From: Chuck Ebbert <cebbert@redhat.com>
To: Boris Ostrovsky <boris.ostrovsky@amd.com>
Cc: Hans Rosenfeld <hans.rosenfeld@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>
Subject: Re: [PATCH] cpu, AMD: Fix another bug in the new errata checking code
Date: Fri, 13 May 2011 10:59:28 -0400 [thread overview]
Message-ID: <20110513105928.6216ddc8@katamari> (raw)
In-Reply-To: <4DCD2C3F.9070905@amd.com>
On Fri, 13 May 2011 09:03:59 -0400
Boris Ostrovsky <boris.ostrovsky@amd.com> wrote:
> On 05/13/2011 06:21 AM, Hans Rosenfeld wrote:
> > On Thu, May 12, 2011 at 07:59:38PM -0400, Chuck Ebbert wrote:
> > The revision guide states that family 0x10 model 6 stepping 2 has E400.
> > So I would expect that OSVW length is>= 2 and that OSVW status has bit
> > 1 set, or that OSVW length is< 2. This indicates that the workaround is
> > necessary, without any need to check the family-model-stepping ranges.
> >
> > It would also be correct if the BIOS disabled C1E and cleared the
> > corresponding OSVW status bit. Anything else would probably be a very
> > nasty BIOS bug.
> >
> > Could you send me the contents of MSRs 0xc0010140, 0xc0010141 and
> > 0xc0010055?
>
> Knowing whether any C state above C1 is declared could be useful too.
>
rdmsr 0xc0010140 gives 2
rdmsr 0xc0010141 gives 0
rdmsr 0xc0010055 gives 0
And ARAT is definitely set where it wasn't before these updates.
BTW we now have multiple reports of this, one system is a Compaq Presario
CQ61 with an AMD Sempron M120 processor.
I'll check on the C-states next.
next prev parent reply other threads:[~2011-05-13 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 23:59 [PATCH] cpu, AMD: Fix another bug in the new errata checking code Chuck Ebbert
2011-05-13 10:21 ` Hans Rosenfeld
2011-05-13 13:03 ` Boris Ostrovsky
2011-05-13 14:59 ` Chuck Ebbert [this message]
2011-05-13 15:19 ` Hans Rosenfeld
2011-05-16 12:43 ` Chuck Ebbert
2011-05-16 13:38 ` Boris Ostrovsky
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=20110513105928.6216ddc8@katamari \
--to=cebbert@redhat.com \
--cc=Borislav.Petkov@amd.com \
--cc=boris.ostrovsky@amd.com \
--cc=hans.rosenfeld@amd.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