From: Dave Jones <[EMAIL PROTECTED]>
Date: Sat, 4 Feb 2006 12:14:11 -0500
> I've hit it three times now, and every time it seems to have happened
> whilst it was under attack from junk icmp, which hopefully narrows
> it down a little to a specific set of isic parameters.
I've sent the following
On Fri, Feb 03, 2006 at 08:27:02PM -0800, Stephen Hemminger wrote:
> It takes about 15 minutes of over a gigabit link for me to trigger
> on a dual Opteron with 2G of mem. Maybe Dave's niagra's would be
> faster.
>
> Although it might be depend on what level of debugging is turned on.
> Wha
On Sat, 04 Feb 2006 13:50:44 +1100
Herbert Xu <[EMAIL PROTECTED]> wrote:
> Dave Jones <[EMAIL PROTECTED]> wrote:
> > 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 anci
Dave Jones <[EMAIL PROTECTED]> wrote:
> 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
Actually, this is exactly what would've happened if someone did a
dst_release on
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 trogd
