From: Seth Forshee <seth.forshee@canonical.com>
To: Burt Triplett <burt@pbjtriplett.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>,
Venkatesh Pallipadi <venki@google.com>,
Len Brown <lenb@kernel.org>
Subject: Re: Performance/resume issues on Toshiba NB305
Date: Sat, 26 Feb 2011 09:00:32 -0600 [thread overview]
Message-ID: <20110226150032.GA2053@thinkpad-t410> (raw)
In-Reply-To: <4D689681.1030301@pbjtriplett.org>
On Fri, Feb 25, 2011 at 09:58:25PM -0800, Burt Triplett wrote:
> Looks like the Toshiba NB305 has an Intel Atom processor in it.
> bits-327, released today, now detects Intel Atom processors, and no
> longer shows them as unknown. We don't have any processor-specific
> tests for Atom yet, though we may add some in the future. All of
> the general tests should work, however.
The new release detects the Atom processor okay, but in bits-327 the
system resets during the SMI frequency/latency test, whereas it didn't
with bits-316.
> Can you provide more details on which MSRs show up as inconsistent
> on your system? They might represent actual bugs in your BIOS, but
> we might just need to add a few more entries to the Atom
> CPU-specific MSR blacklist as expected inconsistencies.
Here's what it says:
(MSR 0x39 consistent): FAIL
(MSR 0x199 consistent): FAIL
(MSR 0x1a0 consistent): FAIL
Summary: 7917 passed, 3 failed
I have 3 systems with this same processor, and they all report the same
thing here.
Seth
next prev parent reply other threads:[~2011-02-26 15:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 16:42 Performance/resume issues on Toshiba NB305 Seth Forshee
2011-02-25 20:17 ` Steven Rostedt
2011-02-25 20:27 ` Seth Forshee
2011-02-25 22:11 ` Thomas Gleixner
2011-02-25 22:33 ` Seth Forshee
2011-02-25 20:37 ` Thomas Gleixner
2011-02-25 21:21 ` Seth Forshee
2011-02-25 21:47 ` Thomas Gleixner
2011-02-25 22:29 ` Seth Forshee
2011-02-25 22:40 ` Thomas Gleixner
2011-02-26 5:58 ` Burt Triplett
2011-02-26 15:00 ` Seth Forshee [this message]
2011-02-27 20:17 ` Burt Triplett
2011-02-28 15:10 ` Seth Forshee
2011-03-05 5:55 ` Burt Triplett
2011-02-26 8:49 ` [tip:timers/urgent] clockevents: Prevent oneshot mode when broadcast device is periodic tip-bot for Thomas Gleixner
2011-03-01 20:04 ` Performance/resume issues on Toshiba NB305 Seth Forshee
2011-03-01 20:22 ` Thomas Gleixner
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=20110226150032.GA2053@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arjan@infradead.org \
--cc=burt@pbjtriplett.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
/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