mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter J. Stieber" <developer@toyon.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: x86-64 bad pmds in 2.6.11.6 II
Date: Fri, 13 May 2005 14:51:09 -0700	[thread overview]
Message-ID: <01cd01c55805$df437cf0$1600a8c0@toyon.corp> (raw)
In-Reply-To: <20050512212319.GE15965@wotan.suse.de>

CW = Christopher Warner
CW>>>>> 2.6.11.5 kernel,
CW>>>>> Tyan S2882/dual AMD 246 opterons
CW>>>>> sh:18983: mm/memory.c:99: bad pmd
ffff810005974cc8(00007ffffffffe46).
CW>>>>> sh:18983: mm/memory.c:99: bad pmd
ffff810005974cd0(00007ffffffffe47).

DJ = Dave Jones
DJ>>>> That's the 3rd or 4th time I've seen this
DJ>>>> reported on this hardware.
DJ>>>> It's not exclusive to it, but it does seem more
DJ>>>> susceptible for some reason. Spooky.

AK = Andi Kleen wrote:
AK>>> It seems to be clear now that it is hardware
AK>>> independent.
AK>>>
AK>>> I actually got it once now too, but only after
AK>>> 24+h stress test :/
AK>>>
AK>>> I have a better debugging patch now that I will be
AK>>> testing soon, hopefully that turns something up.

DJ = Dave Jones
DJ>> Ok, I'm respinning the Fedora update kernel today
DJ>> for other reasons, if you have that patch in time,
DJ>> I'll toss it in too.
DJ>>
DJ>> Though as yet, no further reports from our users.

AK = Andi Kleen
AK> Here's the new patch. However it costs some memory
AK> bloat because I added a new field to struct page

I posted some information on the fedora-list concerning my experience
with this problem. I am using a Tyan S2885/dual 244 Opterons. For HW and
driver details see:
https://www.redhat.com/archives/fedora-list/2005-May/msg01690.html

I have been using Dave's FC3 test kernel (2.6.11-1.24_FC3smp) for a
little over a day and have been unable to generate the problem with the
computer under a larger than normal load.

Prior to May 12, I had been seeing the problem very regularly. It
started around April 14. I believe this is about the time I first
started using the 2.6.11-1.14_FC3smp kernel. I remember I had to get a
BIOS upgrade from Tyan (http://www.tyan.com/support/html/b_s2885.html
unfortunately a Beta release) to get my network back once I started
using the new kernel. After that the memory.c messages started showing
up. I though it might be BIOS related (see the note on the referenced
Tyan page), but when I saw Christopher's post I thought maybe it was the
kernel because his MOBO doesn't have a Beta BIOS release. I googled and
found this thread, and subscribed to this list.

I have "memory.c:97 bad pmd" entries in my /var/log/messages files going
back to April 14. The only days I don't have them are April 20, 22, 23,
24 and April 29 (22, 23, and 24 are a weekend with less activity). I
have had them every day in May until I installed Dave's test kernel.

I am very computer literate, but not a kernel developer. I hope I didn't
offend you guys by posting here. I would be willing to be your guinea
pig for testing. Currently I am unable to reproduce the problem. If I am
able to reproduce the problem, would you prefer I post here or on the
fedora list?

Thanks for all of your efforts,
Pete



  reply	other threads:[~2005-05-13 21:51 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
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 [this message]
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='01cd01c55805$df437cf0$1600a8c0@toyon.corp' \
    --to=developer@toyon.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®