From: Dave Jones <davej@redhat.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Charles McCreary <mccreary@crmeng.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86-64 bad pmds in 2.6.11.6
Date: Tue, 20 Sep 2005 19:23:18 -0400 [thread overview]
Message-ID: <20050920232318.GC1040@redhat.com> (raw)
In-Reply-To: <20050920194446.GA15606@taniwha.stupidest.org>
On Tue, Sep 20, 2005 at 12:44:46PM -0700, Chris Wedgwood wrote:
> On Tue, Sep 20, 2005 at 10:30:48AM -0700, Linus Torvalds wrote:
>
> > This is quite possibly the result of an Opteron errata (tlb flush
> > filtering is broken on SMP) that we worked around as of 2.6.14-rc4.
>
> It would be really interesting to know if this does help. I was told
> em64t also have the 'bad pmd' problem but I can't make it happen here
> on opteron on em64t.
In the dozens of reports of bad pmd that Fedora users filed, there
wasn't a single EM64T user. In fact, most of the hits were from
very similar product lines, from a handful of vendors (Tyan's seemed
especially susceptable). It may be that other vendors updated their
BIOS's to include this workaround already, and Tyan and a few others
lagged behind.
Dave
next prev parent reply other threads:[~2005-09-20 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 17:12 x86-64 bad pmds in 2.6.11.6 Charles McCreary
2005-09-20 17:30 ` Linus Torvalds
2005-09-20 19:44 ` Chris Wedgwood
2005-09-20 23:23 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 16:55 Andy Davidson
2005-04-08 16:33 Clem Taylor
2005-03-30 21:44 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
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=20050920232318.GC1040@redhat.com \
--to=davej@redhat.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mccreary@crmeng.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