From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Matt Parnell <mparnell@gmail.com>,
linux-kernel@vger.kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 2.6.27-rc0 Power Bugs with HP/Compaq Laptops
Date: Mon, 11 Aug 2008 19:18:49 +0200 [thread overview]
Message-ID: <20080811171849.GN4524@elte.hu> (raw)
In-Reply-To: <200808072300.21771.rjw@sisk.pl>
> > "This is not the right fix. Instead, HPET should be used as a timer
> > source for dynticks. This is not in 2.6.26, but I tried the
> > linux-next tree (google it) and it looked like dynticks worked fine,
> > without disabling C1E. Can't place my finger on the exact commit,
> > but you could check."
Would be nice to figure out which exact change solves the problem, so
that we could fast-route it into v2.6.27. (and for eventual .26 and .25
backporting, if it's simple enough)
first thing would be to check whether tip/master works fine:
http://people.redhat.com/mingo/tip.git/README
if that works fine it would be nice to check whether the pending changes
in tip/timers/hpet solves this particular issue. That can be done by:
git-checkout -b tmp.test tip/timers/hpet
[ once you have set up tip as a remote repository, as described in the
README above. ]
If tip/timers/hpet solves the problem then it's one of these five
commits that solves it:
f92a789: hpet: /dev/hpet - fixes and cleanup, fix
64a76f6: hpet: /dev/hpet - fixes and cleanup
f356181: x86: add PCI ID for 6300ESB force hpet
3243b4e: x86: add another PCI ID for ICH6 force-hpet
70ef6d5: x86: get irq for hpet timer
Ingo
prev parent reply other threads:[~2008-08-11 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <680ad8bc0808070757u49e13b3br1f69fb4881dc44ce@mail.gmail.com>
2008-08-07 21:00 ` 2.6.27-rc0 Power Bugs with HP/Compaq Laptops Rafael J. Wysocki
2008-08-11 17:18 ` Ingo Molnar [this message]
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=20080811171849.GN4524@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mparnell@gmail.com \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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