From: Karol Kozimor <sziwan@hell.org.pl>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-mm2] PM timer still has problems
Date: Mon, 5 Jan 2004 23:17:58 +0100 [thread overview]
Message-ID: <20040105221758.GA13727@hell.org.pl> (raw)
In-Reply-To: <1073340716.15645.96.camel@cog.beaverton.ibm.com>
Thus wrote john stultz:
> If the override boot option failed, its most likely your system doesn't
> have an ACPI PM time source. Instead it seems your system is having
Well, I don't have the slightest idea on how to determine this, though I
read somewhere that all ACPI-compliant systems have those.
> trouble using the PIT as a time source (which seems not all that
> uncommon unfortunately).
Perhaps, though bear in mind it behaves so only if clock=pmtmr has been
appended and works fine with clock=pit.
> I guess we can just re-call select_timer() without an override if the
> override fails, that way you'll fall back to the default time source on
> your system. Try the (compile tested) patch below and see if that helps.
That would be PIT again, as TSC is unusable due to CPUFreq.
I'll try it ASAP -- should I test with Dmitry's patch applied?
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next prev parent reply other threads:[~2004-01-05 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 20:48 [2.6.0-mm2] PM timer still has problems Karol Kozimor
2003-12-31 4:02 ` Andrew Morton
2004-01-04 0:44 ` Karol Kozimor
2004-01-05 6:17 ` Dmitry Torokhov
2004-01-05 12:18 ` Karol Kozimor
2004-01-06 8:31 ` john stultz
2004-01-07 6:30 ` Dmitry Torokhov
2004-01-07 17:01 ` john stultz
2004-03-29 15:44 ` Karol Kozimor
2004-01-05 22:11 ` john stultz
2004-01-05 22:17 ` Karol Kozimor [this message]
2004-01-05 22:32 ` john stultz
2004-01-05 22:54 ` Karol Kozimor
2004-01-05 23:18 ` Karol Kozimor
2004-01-05 23:30 ` john stultz
2004-01-06 4:32 ` Dmitry Torokhov
2004-01-17 1:54 ` Karol Kozimor
2004-01-24 0:55 ` Karol Kozimor
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=20040105221758.GA13727@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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