From: "Karol Kozimor" <sziwan@hell.org.pl>
To: <Administrator@osdl.org>
Cc: "Andrew Morton" <akpm@osdl.org>, <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjanv@redhat.com>,
"jw schultz" <jw@pegasys.ws>
Subject: Re: [2.6.0-mm2] PM timer still has problems
Date: Mon, 29 Mar 2004 16:44:21 +0100 [thread overview]
Message-ID: <030601c415a4$b46f0110$d100000a@sbs2003.local> (raw)
In-Reply-To: <200401050117.06681.dtor_core@ameritech.net>
Thus wrote Dmitry Torokhov:
> I threw a monkey wrench in timer code and came up with the patch below...
> It is not intended for inclusion as is, just some work in progress.
>
> I decided to go hpet way and use tsc in ACPI PM timer to do delay stuff
> and monotonic clock. Plus there some code rearrangements, and stuff I grabbed
> from the CPUFREQ list (Dominics + Li Shahoua P4 variable tsc info ), etc...
> If there is an interest I can split the code into smaller chinks. For what
> it worth I am running with ACPI PM timer, CPUFREQ (dynamically switching
> frequency based on load) and Synaptics and everything is calm. Ntpd has also
> stopped complaining about loosing sync...
Well, no luck here. When clock=pmtmr is appended, the system hangs just
after printing:
#v+
Warning: clock= override failed. Defaulting to PIT
Using pit for high-res timesource
Detected 1700.598 MHz processor.
Console: colour VGA+ 80x25
#v-
The system boots fine without the clock= parameter, though.
[it's an ASUS L3800C laptop with a P4-M and 2.6.1-rc1-mm1 with your patch
on top]
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next prev parent reply other threads:[~2004-03-29 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 20:48 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 [this message]
2004-01-05 22:11 ` john stultz
2004-01-05 22:17 ` Karol Kozimor
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='030601c415a4$b46f0110$d100000a@sbs2003.local' \
--to=sziwan@hell.org.pl \
--cc=Administrator@osdl.org \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=jw@pegasys.ws \
--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
Powered by JetHome