All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Johnson <dj@david-web.co.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: cpufreq longhaul locks up
Date: Fri, 4 May 2007 23:20:40 +0100	[thread overview]
Message-ID: <200705042320.41278.dj@david-web.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0705041200370.18504@yvahk01.tjqt.qr>

On Friday 04 May 2007 11:16, you wrote:
>
> 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:
>

I've been seeing a similar issue, but with a few differences.
I'm running 2.6.21.1 on the same CPU as yourself:

longhaul: VIA C3 'Nehemiah C' [C5P] CPU detected.  Powersaver supported.
longhaul: Using ACPI support.

It seems that longhaul on my system is 'using ACPI support' whereas on yours 
it is 'using northbridge support'. I'm getting lockups after approx. 2-3 
hours using the ondemand governor. It has no problem changing the clock 
speed, and runs at the minimum speed most of the time.

I seem to recall that I get an oops when my system locks-up (the system runs 
headless normally, so it isn't easy to check). I'll investigate.

Regards,
David.

-- 
David Johnson
www.david-web.co.uk

WARNING: multiple messages have this Message-ID (diff)
From: David Johnson <dj@david-web.co.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq longhaul locks up
Date: Fri, 4 May 2007 23:20:40 +0100	[thread overview]
Message-ID: <200705042320.41278.dj@david-web.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0705041200370.18504@yvahk01.tjqt.qr>

On Friday 04 May 2007 11:16, you wrote:
>
> 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:
>

I've been seeing a similar issue, but with a few differences.
I'm running 2.6.21.1 on the same CPU as yourself:

longhaul: VIA C3 'Nehemiah C' [C5P] CPU detected.  Powersaver supported.
longhaul: Using ACPI support.

It seems that longhaul on my system is 'using ACPI support' whereas on yours 
it is 'using northbridge support'. I'm getting lockups after approx. 2-3 
hours using the ondemand governor. It has no problem changing the clock 
speed, and runs at the minimum speed most of the time.

I seem to recall that I get an oops when my system locks-up (the system runs 
headless normally, so it isn't easy to check). I'll investigate.

Regards,
David.

-- 
David Johnson
www.david-web.co.uk

  parent reply	other threads:[~2007-05-04 22:20 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 10:16 cpufreq longhaul locks up Jan Engelhardt
2007-05-04 11:36 ` Wander Winkelhorst
2007-05-04 11:51   ` Jan Engelhardt
2007-05-04 11:51     ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:08   ` Rafał Bilski
2007-05-04 17:42   ` Chuck Ebbert
2007-05-04 17:42     ` Chuck Ebbert
2007-05-04 18:40     ` Rafał Bilski
2007-05-04 18:08   ` Wander Winkelhorst
2007-05-04 19:00     ` Rafał Bilski
2007-05-04 19:00       ` Rafał Bilski
2007-05-04 18:48   ` Jan Engelhardt
2007-05-04 18:48     ` Jan Engelhardt
2007-05-04 20:11     ` Rafał Bilski
2007-05-04 20:11       ` Rafał Bilski
2007-05-04 21:03       ` Jan Engelhardt
2007-05-04 21:03         ` Jan Engelhardt
2007-05-04 20:37 ` john stultz
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  8:00             ` Jan Engelhardt
2007-05-05 13:58             ` Rafał Bilski
2007-05-05 13:58               ` Rafał Bilski
2007-05-05 18:13               ` Jan Engelhardt
2007-05-05 18:13                 ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson [this message]
2007-05-04 22:20   ` David Johnson
2007-05-04 23:37   ` Jan Engelhardt
2007-05-04 23:37     ` Jan Engelhardt
2007-05-05  5:40     ` Rafał Bilski
2007-05-05  5:40       ` Rafał Bilski
2007-05-05  8:44       ` Wander Winkelhorst
2007-05-05 14:02         ` Rafał Bilski
2007-05-05 14:02           ` Rafał Bilski
2007-05-05 17:48         ` Rafał Bilski
2007-05-05 17:48           ` Rafał Bilski
2007-05-05 18:42           ` Jan Engelhardt
2007-05-05 18:42             ` Jan Engelhardt
2007-05-05 19:58             ` Rafał Bilski
2007-05-05 19:58               ` Rafał Bilski
2007-05-05 20:30               ` Jan Engelhardt
2007-05-05 20:30                 ` Jan Engelhardt
2007-05-05 20:50               ` 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  7:53                     ` Jan Engelhardt
2007-05-06  5:12                 ` Rafał Bilski
2007-05-06  5:12                   ` Rafał Bilski
2007-05-06  8:03                   ` Jan Engelhardt
2007-05-06  8:03                     ` Jan Engelhardt
2007-05-06  9:23                     ` Rafał Bilski
2007-05-06  9:23                       ` Rafał Bilski
2007-05-06  9:32                       ` Jan Engelhardt
2007-05-06 10:25                         ` Rafał Bilski
2007-05-06 10:25                           ` Rafał Bilski
2007-05-06 11:33                           ` Jan Engelhardt
2007-05-06 12:20                             ` Rafał Bilski
2007-05-05  9:37       ` Jan Engelhardt
2007-05-05  9:37         ` Jan Engelhardt
2007-05-05 14:10         ` Rafał Bilski
2007-05-05 14:10           ` Rafał Bilski
2007-05-05 17:38           ` Jan Engelhardt
2007-05-05 17:38             ` Jan Engelhardt
2007-05-05 18:04             ` Rafał Bilski
2007-05-05 18:04               ` Rafał Bilski
2007-05-05 18:23               ` Jan Engelhardt
2007-05-05 18:23                 ` Jan Engelhardt

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=200705042320.41278.dj@david-web.co.uk \
    --to=dj@david-web.co.uk \
    --cc=cpufreq@lists.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.