public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dean Roe <roe@sgi.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG at mm/slab.c:2564 - 2.6.16-rc5-g7b14e3b5
Date: Tue, 7 Mar 2006 09:52:08 +0100	[thread overview]
Message-ID: <20060307095208.6ddc1c4f@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0603061112470.13139@g5.osdl.org>

On Mon, 6 Mar 2006 11:16:13 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:

> On Thu, 2 Mar 2006, Paolo Ornati wrote:
> > 
> > Something is happened again here!
> 
> I think you have bad ram.
> 
> > 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

My suspect was that the failing addr was the same one I had already
seen some time ago with memtest86+ and that was (apparently?) fixed by
disabling "bank interleaving" in the BIOS.

But now that I've rechecked... it was a different address:

76.1 MB -- 04c0 37fc

TEST 6
good	FF FF FF FD
bad	F7 FF FF FD


The one detected with DEBUG_SLAB is at 208.99 MB (so both problems are
in my first 256MB memory module) but I'm unable to reproduce it with
memtest86+...

I wonder if these two are related in some way... or maybe it's just a
weak memory module ;)

-- 
	Paolo Ornati
	Linux 2.6.16-rc5-g501f74f2 on x86_64

      reply	other threads:[~2006-03-07  8:52 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
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 [this message]

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=20060307095208.6ddc1c4f@localhost \
    --to=ornati@fastwebnet.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roe@sgi.com \
    --cc=torvalds@osdl.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