From: john stultz <johnstul@us.ibm.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: davej@codemonkey.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cpufreq@lists.linux.org.uk
Subject: Re: cpufreq longhaul locks up
Date: Fri, 04 May 2007 13:37:32 -0700 [thread overview]
Message-ID: <1178311052.6094.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0705041200370.18504@yvahk01.tjqt.qr>
On Fri, 2007-05-04 at 12:16 +0200, Jan Engelhardt wrote:
> Hi,
>
>
> I found that setting the cpufreq governor to ondemand making the box
> lock up solid in 2.6.20.2 and 2.6.21 after a few seconds. Sysrq
> does not work anymore, and the last messages are:
>
> May 3 19:16:58 cn kernel: longhaul: VIA C3 'Nehemiah C' [C5P] CPU
> detected. Powersaver supported.
> May 3 19:16:58 cn kernel: longhaul: Using northbridge support.
> May 3 19:17:22 cn kernel: Time: acpi_pm clocksource has been installed.
> May 3 19:17:22 cn kernel: Clocksource tsc unstable (delta = -136422685
> ns)
What happens if you boot wihtout the ondemand governor but w/ clocksource=acpi_pm ?
thanks
-john
next prev parent reply other threads:[~2007-05-04 20:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 10:16 Jan Engelhardt
[not found] ` <5699f8f00705040436u63c5ab38g1054001eccc596e7@mail.gmail.com>
2007-05-04 11:51 ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:42 ` Chuck Ebbert
2007-05-04 18:40 ` Rafał Bilski
2007-05-04 18:48 ` Jan Engelhardt
2007-05-04 20:11 ` Rafał Bilski
2007-05-04 21:03 ` Jan Engelhardt
[not found] ` <5699f8f00705041108t67425997w42e6268f9076abc9@mail.gmail.com>
2007-05-04 19:00 ` Rafał Bilski
2007-05-04 20:37 ` john stultz [this message]
2007-05-04 21:02 ` Jan Engelhardt
2007-05-04 22:49 ` john stultz
2007-05-04 23:32 ` Jan Engelhardt
2007-05-05 4:03 ` Rafał Bilski
2007-05-05 8:00 ` Jan Engelhardt
2007-05-05 13:58 ` Rafał Bilski
2007-05-05 18:13 ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson
2007-05-04 23:37 ` Jan Engelhardt
2007-05-05 5:40 ` Rafał Bilski
2007-05-05 9:37 ` Jan Engelhardt
2007-05-05 14:10 ` Rafał Bilski
2007-05-05 17:38 ` Jan Engelhardt
2007-05-05 18:04 ` Rafał Bilski
2007-05-05 18:23 ` Jan Engelhardt
[not found] ` <5699f8f00705050144s5c00a455s8f7dba9258d83986@mail.gmail.com>
2007-05-05 14:02 ` Rafał Bilski
2007-05-05 17:48 ` Rafał Bilski
2007-05-05 18:42 ` Jan Engelhardt
2007-05-05 19:58 ` Rafał Bilski
2007-05-05 20:30 ` Jan Engelhardt
2007-05-05 20:50 ` Jan Engelhardt
2007-05-05 21:32 ` Rafał Bilski
2007-05-06 7:53 ` Jan Engelhardt
2007-05-06 5:12 ` Rafał Bilski
2007-05-06 8:03 ` Jan Engelhardt
2007-05-06 9:23 ` Rafał Bilski
2007-05-06 9:32 ` Jan Engelhardt
2007-05-06 10:25 ` Rafał Bilski
2007-05-06 11:33 ` Jan Engelhardt
2007-05-06 12:20 ` Rafał Bilski
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=1178311052.6094.0.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jengelh@linux01.gwdg.de \
--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