Message-ID: <42285354.5090900@inode.info>
Date: Fri, 04 Mar 2005 13:23:48 +0100
From: Richard Fuchs <richard.fuchs@inode.info>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1
MIME-Version: 1.0
To: Andrew Morton <akpm@osdl.org>
CC: linux-kernel@vger.kernel.org
Subject: Re: slab corruption in skb allocs
References: <42283093.7040405@inode.info> <20050304035309.1da7774e.akpm@osdl.org>
In-Reply-To: <20050304035309.1da7774e.akpm@osdl.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1321
Lines: 33

Andrew Morton wrote:

> I guess it could be hardware.  But given that disabling DMA _causes_ the
> problem, rather than fixes it, it seems unlikely.
> 
> Could you enable CONFIG_DEBUG_PAGEALLOC in .config and see it that triggers
> an oops?

by now, i could reproduce this on two different machines with quite 
different hardware, while a third doesn't seem to show those symptoms. 
on the second machine, i got the corruption errors from the slab 
debugger mostly from the disk access alone, the network traffic was only 
minimal (but still present). i was doing write operations on the hdd in 
this test.

kernel 2.6.7 doesn't show this behavior, while all kernels from 2.6.9 
and up do. (i didn't test 2.6.8.x).

as for DEBUG_PAGEALLOC... when i enable this option, the errors from 
DEBUG_SLAB magically disappear. however, my ssh session got disconnected 
once while doing the disk access with the message:

Received disconnect from 195.58.172.154: 2: Bad packet length 4239103034.

never seen this before and not sure if this has anything to do with it...

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