From: Paolo Ornati <ornati@fastwebnet.it>
To: Dean Roe <roe@sgi.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG at mm/slab.c:2564 - 2.6.16-rc5-g7b14e3b5
Date: Thu, 2 Mar 2006 09:07:28 +0100 [thread overview]
Message-ID: <20060302090728.2fee8f3c@localhost> (raw)
In-Reply-To: <20060301173636.GA20861@sgi.com>
On Wed, 1 Mar 2006 11:36:36 -0600
Dean Roe <roe@sgi.com> wrote:
> I might have hit something similar about a month ago running 2.6.16-rc1.
> At the time I had written this off as a hardware problem since I was using
> a questionable system, but maybe there is a hard-to-hit bug in the anon_vma
> or slab code?
Something is happened again here!
Slab corruption: start=ffff81000d0ffb30, len=104
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39)
000: 6b 6b 6b 2b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Prev obj: start=ffff81000d0ffab0, len=104
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<ffffffff80141b05>](mempool_alloc+0x44/0xdf)
000: 3e db d8 05 00 00 00 00 00 00 00 00 00 00 00 00
010: 58 a6 f1 1f 00 81 ff ff 09 00 00 00 00 00 00 00
Next obj: start=ffff81000d0ffbb0, len=104
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Slab corruption: start=ffff81000d0ffb30, len=104
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39)
000: 6b 6b 6b 2b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Prev obj: start=ffff81000d0ffab0, len=104
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=ffff81000d0ffbb0, len=104
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<ffffffff8015caac>](end_bio_bh_io_sync+0x35/0x39)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Mmmm... I'm going to disable CPU freq scaling, it's the only thing I've
recently enabled, maybe it's causing some kind of instability ?!
--
Paolo Ornati
Linux 2.6.16-rc5-g800d1142 on x86_64
next prev parent reply other threads:[~2006-03-02 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 15:06 Kernel BUG at mm/slab.c:2564 - 2.6.16-rc5-g7b14e3b5 Paolo Ornati
2006-03-01 16:07 ` Paolo Ornati
2006-03-02 8:53 ` Paolo Ornati
2006-03-01 17:36 ` Dean Roe
2006-03-02 8:07 ` Paolo Ornati [this message]
2006-03-04 9:07 ` Kernel BUG at mm/slab.c:2564 - problem vanished Paolo Ornati
2006-03-06 19:16 ` Kernel BUG at mm/slab.c:2564 - 2.6.16-rc5-g7b14e3b5 Linus Torvalds
2006-03-07 8:52 ` Paolo Ornati
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=20060302090728.2fee8f3c@localhost \
--to=ornati@fastwebnet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=roe@sgi.com \
/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