sound and TCP checksums in 2.1.126pre2, 2.1.125ac3

Steve VanDevender (stevev@efn.org)
Sat, 17 Oct 1998 16:41:47 -0700 (PDT)

Both 2.1.126pre2 and 2.1.125ac3 seem to fix most of the sound
problems I observed in 2.1.125; most processes no longer hang on
close or exit after writing to an audio device (my GUS classic).
However, I find that XEmacs still blocks in DMAbuf_sync at the
point that it does an ioctl(SNDCTL_DSP_SYNC) after writing to
/dev/dsp.

I'm also seeing quite a few of these messages now, also in both
2.1.126pre2 and 2.1.125ac3:

Oct 17 16:31:01 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=532/532/552
Oct 17 16:31:01 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=532/532/552
Oct 17 16:31:02 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=421/421/441
Oct 17 16:31:02 localhost kernel: TCPv4 bad checksum from 198.68.17.24:006e to 204.214.99.68:0401, len=20/20/40

TCP keeps working, but I've never seen these messages before.
It's possible they may have been happening since I started using
2.1.125 -- I discovered that sysklogd-1.3-27 was losing most of
my syslog information and didn't start seeing these messages
until I went back to plain 1.3.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/