From: Richard Fuchs <richard.fuchs@inode.info>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: slab corruption in skb allocs
Date: Fri, 04 Mar 2005 13:23:48 +0100 [thread overview]
Message-ID: <42285354.5090900@inode.info> (raw)
In-Reply-To: <20050304035309.1da7774e.akpm@osdl.org>
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
next prev parent reply other threads:[~2005-03-04 12:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 9:55 slab corruption in skb allocs Richard Fuchs
2005-03-04 11:53 ` Andrew Morton
2005-03-04 12:23 ` Richard Fuchs [this message]
2005-03-04 20:11 ` Matt Mackall
2005-03-04 21:19 ` Richard Fuchs
2005-03-04 21:27 ` Matt Mackall
2005-03-04 21:52 ` Richard Fuchs
2005-03-04 22:05 ` Matt Mackall
2005-03-04 22:51 ` Richard Fuchs
2005-03-05 18:25 ` Scott Feldman
2005-03-05 19:10 ` Richard Fuchs
2005-03-06 17:44 ` Scott Feldman
2005-03-06 18:40 ` Richard Fuchs
2005-03-07 5:07 ` Scott Feldman
2005-03-07 8:30 ` Richard Fuchs
2005-03-04 18:10 ` Dave Jones
2005-03-04 18:32 ` Richard Fuchs
2005-03-04 19:29 ` Richard Fuchs
2005-03-21 22:36 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42285354.5090900@inode.info \
--to=richard.fuchs@inode.info \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox