From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Christopher Warner <chris@servertogo.com>,
Hugh Dickins <hugh@veritas.com>,
cwarner@kernelcode.com, Chris Wright <chrisw@osdl.org>,
"Sergey S. Kostyliov" <rathamahata@ehouse.ru>,
Clem Taylor <clem.taylor@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86-64 bad pmds in 2.6.11.6 II
Date: Tue, 10 May 2005 12:59:38 -0400 [thread overview]
Message-ID: <20050510165938.GA11835@redhat.com> (raw)
In-Reply-To: <20050510164649.GL25612@wotan.suse.de>
On Tue, May 10, 2005 at 06:46:49PM +0200, Andi Kleen wrote:
> On Tue, May 10, 2005 at 12:38:51PM -0400, Dave Jones wrote:
> > On Tue, May 10, 2005 at 05:36:54AM -0400, Christopher Warner wrote:
> > > 2.6.11.5 kernel,
> > > Tyan S2882/dual AMD 246 opterons
> > > sh:18983: mm/memory.c:99: bad pmd ffff810005974cc8(00007ffffffffe46).
> > > sh:18983: mm/memory.c:99: bad pmd ffff810005974cd0(00007ffffffffe47).
> >
> > That's the 3rd or 4th time I've seen this reported on this hardware.
> > It's not exclusive to it, but it does seem more susceptible
> > for some reason. Spooky.
>
> It seems to be clear now that it is hardware independent.
>
> I actually got it once now too, but only after 24+h stress test :/
>
> I have a better debugging patch now that I will be testing soon,
> hopefully that turns something up.
Ok, I'm respinning the Fedora update kernel today for other
reasons, if you have that patch in time, I'll toss it in too.
Though as yet, no further reports from our users.
Dave
next prev parent reply other threads:[~2005-05-10 17:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 21:44 x86-64 bad pmds in 2.6.11.6 Dave Jones
2005-03-31 10:41 ` Andi Kleen
2005-03-31 21:52 ` Dave Jones
2005-04-01 11:52 ` Sergey S. Kostyliov
2005-04-07 2:49 ` Dave Jones
2005-04-07 6:29 ` Andi Kleen
2005-04-14 13:54 ` Hugh Dickins
2005-04-14 17:01 ` Andi Kleen
2005-04-14 17:34 ` Hugh Dickins
2005-04-14 18:10 ` Andi Kleen
2005-04-14 18:11 ` x86-64 bad pmds in 2.6.11.6 II Andi Kleen
2005-04-14 18:27 ` Chris Wright
2005-04-15 17:24 ` Andi Kleen
2005-04-15 17:28 ` Chris Wright
2005-04-15 17:58 ` Hugh Dickins
2005-04-15 18:07 ` Dave Jones
2005-04-22 17:37 ` Debugging patch was " Andi Kleen
2005-04-27 14:23 ` New debugging " Andi Kleen
2005-04-27 17:37 ` Dave Jones
2005-04-29 11:07 ` Hans Kristian Rosbach
2005-04-19 13:35 ` Andi Kleen
2005-04-19 15:52 ` Hugh Dickins
2005-04-29 11:12 ` Christopher Warner
2005-04-29 16:13 ` Chris Wright
2005-04-29 17:32 ` Dave Jones
2005-05-02 17:00 ` Andi Kleen
2005-05-02 15:28 ` Christopher Warner
2005-05-02 20:33 ` Chris Wright
2005-05-02 21:08 ` Dave Jones
2005-05-03 14:28 ` Andi Kleen
2005-05-03 15:15 ` Dave Jones
2005-05-10 9:36 ` Christopher Warner
2005-05-10 16:26 ` Chris Wright
2005-05-10 12:03 ` Christopher Warner
2005-05-10 16:38 ` Dave Jones
2005-05-10 16:46 ` Andi Kleen
2005-05-10 16:59 ` Dave Jones [this message]
2005-05-10 20:32 ` Andi Kleen
2005-05-10 20:43 ` Chris Wright
2005-05-12 21:23 ` Andi Kleen
2005-05-13 21:51 ` Peter J. Stieber
2005-05-14 17:29 ` Peter J. Stieber
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=20050510165938.GA11835@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=chris@servertogo.com \
--cc=chrisw@osdl.org \
--cc=clem.taylor@gmail.com \
--cc=cwarner@kernelcode.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@ehouse.ru \
/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