From: john stultz <johnstul@us.ibm.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Len Brown <len.brown@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: Fw: [BUG 2.6.21-rc7] acpi_pm clocksource loses time on x86-64
Date: Thu, 03 May 2007 19:38:50 -0700 [thread overview]
Message-ID: <1178246331.7460.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1178129409.6183.12.camel@localhost.localdomain>
On Wed, 2007-05-02 at 11:10 -0700, john stultz wrote:
> On Sun, 2007-04-29 at 17:24 +0200, Mikael Pettersson wrote:
> > On Thu, 26 Apr 2007 15:42:44 -0700, john stultz wrote:
> > >Another shot in the dark:
> > >
> > >I wonder if the ACPI PM counter is halting in idle. Does booting w/
> > >idle=poll change the behavior? (Please do this while your laptop is
> > >plugged in, as it will run the cpu at full speed all the time).
> >
> > Bingo!
>
> Awesome! Finally, some progress! Thanks again for putting up w/ all my
> testing requests.
>
> > I booted the x86-64 2.6.21 final kernel with idle=poll and let the
> > laptop idle for an hour. The ondemand cpufreq governor did reduce
> > the CPU's clock frequency, but that shouldn't have affected the
> > chipset or the ACPI PM counter.
> >
> > Anyway, after 60 minutes `date' and `hwclock' were still in perfect
> > sync and matched actual time.
> >
> > Any ideas why this halting in idle doesn't happen with the 32-bit kernel?
>
> No clue. Time to ask Len. :)
>
> Hey Len,
> So that slow acpi_pm on x86_64 seems to be connected w/ the idle loop.
> I'm guessing the chipset halts the ACPI PM in lower C states. Do you
> have any guesses as to what might differ between x86_64 and i386 ACPI
> idle loops? Or might this be something different in what the BIOS
> exports in x86_64 mode or i386 mode?
Mikael,
Just trying to dig a bit more through the acpi_processor_idle code.
Could you run "cat /proc/acpi/processor/CPU1/power" and reply w/ the
output?
thanks
-john
next prev parent reply other threads:[~2007-05-04 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704291524.l3TFOL9j013216@harpo.it.uu.se>
2007-05-02 18:10 ` Fw: [BUG 2.6.21-rc7] acpi_pm clocksource loses time on x86-64 john stultz
2007-05-04 2:38 ` john stultz [this message]
2007-05-13 21:30 Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 9:11 Mikael Pettersson
2007-05-10 18:52 ` john stultz
2007-05-04 7:42 Mikael Pettersson
2007-05-08 19:14 ` Len Brown
[not found] <20070417100942.c990604b.akpm@linux-foundation.org>
2007-04-17 20:12 ` john stultz
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=1178246331.7460.27.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=ak@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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