With a song in my heart, I set out this afternoon to toss 2.3.50 on my
system and see what happened. The result was a normal-looking boot,
followed by an (evidently) locked system and a great deal of disk
activity. Once I got through the reset-fsck-repeat cycle, I found the
following in my log file:
Mar 10 15:26:06 montalcino kernel: ip_finish_output: bad owned skb = c7505f20:
Mar 10 15:26:06 montalcino kernel: skb: pf=2 (owned) dev=eth0 len=64
Mar 10 15:26:06 montalcino kernel: PROTO=17 38.153.40.12:1024 38.153.40.3:53 L=64 S=0x00 I=0 F=0x4000 T=64
Mar 10 15:26:06 montalcino kernel: ip_local_deliver: bad non-lo skb:
Mar 10 15:26:06 montalcino kernel: skb: pf=2 (unowned) dev=eth0 len=203
Mar 10 15:26:06 montalcino kernel: PROTO=17 38.153.40.3:53 38.153.40.12:1024 L=203 S=0x00 I=59010 F=0x0000 T=64
For what it's worth, .12 is the machine in question; .3 is a system that,
among other things, is our DNS server.
The previous development kernel I ran (2.3.47) worked great for me for a
long time.
Ideas?
Thanks,
jon
Jonathan Corbet, Eklektix, Inc.
corbet@eklektix.com
-
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/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:18 EST