From: Chuck Ebbert <cebbert@redhat.com>
To: Zach Carter <linux@zachcarter.com>
Cc: Dave Jones <davej@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: Bad page state errors during kernel make
Date: Mon, 16 Apr 2007 19:36:40 -0400 [thread overview]
Message-ID: <46240888.1040804@redhat.com> (raw)
In-Reply-To: <46230A3A.8060907@zachcarter.com>
Zach Carter wrote:
>
> 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?
memtest86 does not really stress everything a real kernel compile
would.
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert@redhat.com>
To: Zach Carter <linux@zachcarter.com>
Cc: Dave Jones <davej@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: Bad page state errors during kernel make
Date: Mon, 16 Apr 2007 19:36:40 -0400 [thread overview]
Message-ID: <46240888.1040804@redhat.com> (raw)
In-Reply-To: <46230A3A.8060907@zachcarter.com>
Zach Carter wrote:
>
> 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?
memtest86 does not really stress everything a real kernel compile
would.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-16 23:36 UTC|newest]
Thread overview: 12+ 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:30 ` Zach Carter
2007-04-16 3:56 ` Dave Jones
2007-04-16 3:56 ` Dave Jones
2007-04-16 5:31 ` Zach Carter
2007-04-16 5:31 ` Zach Carter
2007-04-16 5:44 ` Dave Jones
2007-04-16 5:44 ` Dave Jones
2007-04-16 23:36 ` Chuck Ebbert [this message]
2007-04-16 23:36 ` Chuck Ebbert
2007-04-17 3:19 ` BUG: Bad page state errors during kernel make (resolved) Zach Carter
2007-04-17 3:19 ` 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=46240888.1040804@redhat.com \
--to=cebbert@redhat.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@zachcarter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.