From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Len Brown <lenb@kernel.org>,
akpm@osdl.org, mm-commits@vger.kernel.org, ak@muc.de,
johnstul@us.ibm.com, zippel@linux-m68k.org,
linux-acpi@vger.kernel.org, asit.k.mallick@intel.com,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: + acpi-keep-track-of-timer-broadcasting-fix.patch added to -mm tree
Date: Tue, 30 Jan 2007 21:31:18 +0100 [thread overview]
Message-ID: <20070130203118.GC1246@elte.hu> (raw)
In-Reply-To: <1170115975.29240.111.camel@localhost.localdomain>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 2007-01-29 at 18:55 -0500, Len Brown wrote:
> > My understanding is that
> > 1. All existing and future Intel systems have a FUNCTIONAL LAPIC timer in C2.
> > 2. All existing Intel systems have a BROKEN LAPIC timer in C3.
> >
> > If you've found a system that defies these rules, then I'm extremely
> > interested to know about it.
>
> Ask akpm. His vaio has this problem since ages. As well as other Intel
> based boxen. Yes, they have broken BIOSes ....
my HP nx9030 is one such box too. [ I sent the BIOS info - Len, did you
get those? ]
Ingo
next prev parent reply other threads:[~2007-01-30 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701282247.l0SMl3rG005194@shell0.pdx.osdl.net>
[not found] ` <200701282153.29132.lenb@kernel.org>
[not found] ` <20070129065540.GB23785@elte.hu>
2007-01-29 23:55 ` + acpi-keep-track-of-timer-broadcasting-fix.patch added to -mm tree Len Brown
2007-01-30 0:12 ` Thomas Gleixner
2007-01-30 20:31 ` Ingo Molnar [this message]
2007-01-30 20:34 ` Ingo Molnar
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=20070130203118.GC1246@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=asit.k.mallick@intel.com \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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