LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Joachim Deguara" <joachim.deguara@amd.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Cal Peake" <cp@absolutedigital.net>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Chuck Ebbert" <cebbert@redhat.com>,
"Gabriel C" <nix.or.die@googlemail.com>,
"Frank Hale" <frankhale@gmail.com>,
"Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Kernel ACPI Mailing List" <linux-acpi@vger.kernel.org>,
len.brown@intel.com, "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: ACPI on Averatec 2370
Date: Wed, 8 Aug 2007 16:41:59 +0200 [thread overview]
Message-ID: <200708081642.00581.joachim.deguara@amd.com> (raw)
In-Reply-To: <20070808000631.GB7353@one.firstfloor.org>
On Wednesday 08 August 2007 02:06:31 Andi Kleen wrote:
> On Tue, Aug 07, 2007 at 06:15:37PM -0400, Cal Peake wrote:
> > On Fri, 3 Aug 2007, Linus Torvalds wrote:
> > > > MSR_K8_ENABLE_C1E lo == 0x04c14015
> > > > MSR_K8_ENABLE_C1E hi == 0x00000000
> > > > lo & ENABLE_C1E_MASK == 0
> > >
> > > And yeah, that claims that C1E is not on, but:
> > > > amd_apic_timer_broken: forcing return value of 1
> >
> > So it seems my initial debugging report was, err, incomplete. I failed to
> > notice that the amd_apic_timer_broken function was getting called twice,
> > once for each core.
> >
> > The second call shows this:
> >
> > MSR_K8_ENABLE_C1E == 0x14c14015
>
> Ah interesting. Ok finally that all starts making sense.
>
> Not sure why the MSR varies between cores though.
This is a BIOS bug as the BIOS should have programmed the MSR the same for
both cores. See section 10.2.4 of the Rev F BKDG [1] (10.2.4.1 talks about
the SMI case but a newer version of the doc not yet release has similar
wording about both cores needing to have the bit set for the chipset case).
-Joachim
[1]
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32559.pdf
next prev parent reply other threads:[~2007-08-08 14:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 18:05 Frank Hale
2007-07-29 18:13 ` Gabriel C
2007-07-29 18:45 ` Cal Peake
2007-07-29 18:58 ` Frank Hale
2007-07-29 19:58 ` Frank Hale
2007-07-30 15:20 ` Cal Peake
2007-08-02 17:50 ` Cal Peake
2007-08-02 19:09 ` Chuck Ebbert
2007-08-02 19:42 ` Cal Peake
2007-08-02 20:26 ` Chuck Ebbert
2007-08-02 20:30 ` Cal Peake
2007-08-02 20:51 ` Frank Hale
2007-08-02 21:07 ` Linus Torvalds
2007-08-02 21:53 ` Cal Peake
2007-08-03 21:56 ` Linus Torvalds
2007-08-04 9:30 ` Andi Kleen
2007-08-04 13:50 ` Frank Hale
2007-08-05 14:26 ` Thomas Renninger
2007-08-07 22:15 ` Cal Peake
2007-08-08 0:06 ` Andi Kleen
2007-08-08 0:53 ` [PATCH] drop unneeded variable in amd_apic_timer_broken Cal Peake
2007-08-08 14:36 ` Andi Kleen
2007-08-08 16:00 ` Cal Peake
2007-08-08 18:25 ` Tim Gardner
2007-08-08 14:41 ` Joachim Deguara [this message]
2007-08-08 23:52 ` ACPI on Averatec 2370 Frank Hale
2007-08-09 9:45 ` Joachim Deguara
2007-08-03 15:52 ` Ben Collins
2007-08-03 18:19 ` Chuck Ebbert
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=200708081642.00581.joachim.deguara@amd.com \
--to=joachim.deguara@amd.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cebbert@redhat.com \
--cc=cp@absolutedigital.net \
--cc=frankhale@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nix.or.die@googlemail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--subject='Re: ACPI on Averatec 2370' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).