From: Manfred Spraul <manfred@colorfullife.com>
To: caszonyi@rdslink.ro
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slab coruption and oops with 2.6.1-mm4
Date: Sun, 18 Jan 2004 23:03:58 +0100 [thread overview]
Message-ID: <400B02CE.5060907@colorfullife.com> (raw)
Calin wrote:
>Then usual oops but *before that* something which hasn't happened before.
>Slab corruption: start=c57c2000, len=4096
>000: 6e 72 6d 71 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
>
>
Is that reproducable? The selftest code in slab noticed a change in a
buffer that is not in use: All values should be 0x6b, but the first 4
bytes are different.
Could you try to boot with CONFIG_DEBUG_PAGEALLOC enabled? Perhaps that
identifies who corrupts the page. Unfortunately it can't detect DMA writes.
>------------ kernel BUG at include/linux/mm.h:275!
>
put_page_testzero noticed that the page count was already 0. It seems
that someone uses memory that was already freed.
--
Manfred
next reply other threads:[~2004-01-18 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 22:03 Manfred Spraul [this message]
[not found] <20040118220051.3f3d8420.akpm@osdl.org>
2004-01-19 12:15 ` Fw: Slab coruption and oops with 2.6.1-mm4 Gerd Knorr
2004-01-19 16:05 ` Gerd Knorr
2004-01-20 0:27 ` caszonyi
2004-01-20 1:22 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 21:37 caszonyi
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=400B02CE.5060907@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=caszonyi@rdslink.ro \
--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