Linux 2.4.21-rc<x>-ac<y> network errors (machine lockup)
From: Richard A Nelson (cowboy@vnet.ibm.com)
Date: Mon May 26 2003 - 20:07:16 EST
Every so often, my home box does this:
back40 kernel: ip_dev_loopback_xmit: bad owned skb = cbf61b40: PRE_ROUTING FORWARD POST_ROUTING
back40 kernel: skb: pf=2 (unowned) dev=eth0 len=77
back40 kernel: PROTO=17 192.168.0.1:32772 239.255.255.253:427 L=77 S=0x00 I=0 F=0x4000 T=7
back40 kernel: ip_dev_loopback_xmit: bad owned skb = d9731c80: PRE_ROUTING FORWARD POST_ROUTING
back40 kernel: skb: pf=2 (unowned) dev=eth0 len=77
back40 kernel: PROTO=17 192.168.0.1:32782 239.255.255.253:427 L=77 S=0x00 I=0 F=0x4000 T=7
back40 kernel: LIST_DELETE: ip_conntrack_core.c:300
`&ct->tuplehash[IP_CT_DIR_REPLY]'(c0920ea4) not in &ip_conntrack_hash
[hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
back40 kernel: ip_dev_loopback_xmit: bad owned skb = ce073900: PRE_ROUTING FORWARD POST_ROUTING
back40 kernel: skb: pf=2 (unowned) dev=eth0 len=77
May 26 18:52:04 back40 kernel: PROTO=17 192.168.0.1:32785
239.255.255.253:427 L=77 S=0x00 I=0 F=0x4000 T=7
The machine will run a few minutes longer and the freeze hard (CAS B or
reset switch is the only thing accepted).
This has happened with all -pre and -rc patches I can remember
$lspci
00:00.0 Host bridge: ALi Corporation M1541 (rev 04)
00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04)
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:03.0 Bridge: ALi Corporation M7101 PMU
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV] (rev c3)
00:09.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
00:0a.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
00:0c.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10] (rev 08)
00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c1)
--
Rick Nelson
Life'll kill ya -- Warren Zevon
Then you'll be dead -- Life'll kill ya
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/