From: Zach Carter <linux@zachcarter.com>
To: Dave Jones <davej@redhat.com>, Zach Carter <linux@zachcarter.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: Bad page state errors during kernel make
Date: Sun, 15 Apr 2007 22:31:38 -0700 [thread overview]
Message-ID: <46230A3A.8060907@zachcarter.com> (raw)
In-Reply-To: <20070416035603.GD21217@redhat.com>
Dave Jones wrote:
> On Sun, Apr 15, 2007 at 08:30:27PM -0700, Zach Carter wrote:
> > list_del corruption. prev->next should be c21a4628, but was e21a4628
>
> 'c' became 'e' in that last address. A single bit flipped.
> Given you've had this for some time, this smells like a hardware problem.
> memtest86+ will probably show up something.
Hum. I forgot to mention in my report that I had already run thru 10 clean passes with memtest86+
Do you think there might be other bad hw, or another explanation?
-Zach
next prev parent reply other threads:[~2007-04-16 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 3:30 BUG: Bad page state errors during kernel make Zach Carter
2007-04-16 3:56 ` Dave Jones
2007-04-16 5:31 ` Zach Carter [this message]
2007-04-16 5:44 ` Dave Jones
2007-04-16 23:36 ` Chuck Ebbert
2007-04-17 3:19 ` BUG: Bad page state errors during kernel make (resolved) Zach Carter
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=46230A3A.8060907@zachcarter.com \
--to=linux@zachcarter.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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