I've had a box being tortured with random junk packets (created with isic)
for a few days, and it spat this out last night..
Feb 1 04:28:09 trogdor kernel: Slab corruption: (Not tainted) start=cefc8a9c,
len=244
Feb 1 04:28:09 trogdor kernel: Redzone: 0x5a2cf071/0x5a2cf071.
Feb 1 04:28:09 trogdor kernel: Last user: [<c02a3d22>](dst_destroy+0x7f/0xab)
Feb 1 04:28:09 trogdor kernel: [<c015f88f>] check_poison_obj+0x73/0x16a
[<c015f9a8>] cache_alloc_debugcheck_after+0x22/0xf9
Feb 1 04:28:09 trogdor kernel: [<c015fafc>] kmem_cache_alloc+0x7d/0x86
[<c02a3ed5>] dst_alloc+0x27/0x7b
Feb 1 04:28:09 trogdor kernel: [<c02a3ed5>] dst_alloc+0x27/0x7b
[<c02b724d>] __ip_route_output_key+0x5a2/0x843
Feb 1 04:28:09 trogdor kernel: [<e08d34bb>] issue_and_wait+0x28/0x93 [3c59x]
[<e08d6c64>] boomerang_start_xmit+0x31c/0x335 [3c59x]
Feb 1 04:28:09 trogdor kernel: [<c02a26ca>] dev_queue_xmit+0x208/0x20f
[<c02b7501>] ip_route_output_flow+0x13/0x57
Feb 1 04:28:09 trogdor kernel: [<c02b754e>] ip_route_output_key+0x9/0xb
[<c02d81cc>] icmp_send+0x282/0x397
Feb 1 04:28:09 trogdor kernel: [<c02b758b>] ip_route_input+0x3b/0xc6a
[<c02f61af>] _spin_lock_irqsave+0x9/0xd
Feb 1 04:28:09 trogdor kernel: [<c02bbb4f>] ip_options_compile+0x3da/0x3f3
[<c02ba1a0>] ip_rcv+0x322/0x478
Feb 1 04:28:09 trogdor kernel: [<c02a0d70>] netif_receive_skb+0x211/0x259
[<c02a2283>] process_backlog+0x7a/0x100
Feb 1 04:28:09 trogdor kernel: [<c02a23a2>] net_rx_action+0x99/0x170
[<c0127ac8>] __do_softirq+0x58/0xc2
Feb 1 04:28:09 trogdor kernel: [<c0105f03>] do_softirq+0x46/0x4e <0>
=======================
Feb 1 04:28:09 trogdor kernel: [<c0105eb4>] do_IRQ+0x72/0x7b
Feb 1 04:28:09 trogdor kernel: [<c0104766>] common_interrupt+0x1a/0x20
[<c0102db1>] default_idle+0x0/0x55
Feb 1 04:28:09 trogdor kernel: [<c0102ddd>] default_idle+0x2c/0x55
[<c0102e95>] cpu_idle+0x8f/0xa8
Feb 1 04:28:09 trogdor kernel: [<c03ce684>] start_kernel+0x301/0x307
<3>000: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Feb 1 04:28:09 trogdor kernel: Prev obj: start=cefc899c, len=244
Feb 1 04:28:09 trogdor kernel: Redzone: 0x5a2cf071/0x5a2cf071.
Feb 1 04:28:09 trogdor kernel: Last user: [<c02a3d22>](dst_destroy+0x7f/0xab)
Feb 1 04:28:09 trogdor kernel: 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
6b 6b
Feb 1 04:28:09 trogdor kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
6b 6b
Feb 1 04:28:09 trogdor kernel: Next obj: start=cefc8b9c, len=244
Feb 1 04:28:09 trogdor kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Feb 1 04:28:09 trogdor kernel: Last user: [<c02a3ed5>](dst_alloc+0x27/0x7b)
Feb 1 04:28:09 trogdor kernel: 000: 7c dd 63 cf 01 00 00 00 a6 a2 00 00 00 00
00 00
Feb 1 04:28:09 trogdor kernel: 010: 00 b7 37 c0 00 00 02 00 01 00 00 00 56 a9
1b 02
Note the first slab corruption line..
000: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
has a single bit error, which _could_ be bad ram, as this box is an ancient
4-way pentium pro, so it's days may be numbered. I'll give it a spin with
memtest86 next time I'm at the office, but I wanted to report this just
in case, as the last few days I've been seeing a number of slab corruption
issues on different boxes, some of which I know are definitly ok wrt hardware
problems.
Dave
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
