Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 103497 - Unstable system because of ondemand cpu scaling governor
Summary: Unstable system because of ondemand cpu scaling governor
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High critical (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
Depends on:
Reported: 2005-08-23 12:17 UTC by Juha Heljoranta
Modified: 2007-04-29 14:52 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Debug infromation from /var/log/kern.log (systemcrashing,5.81 KB, text/plain)
2005-08-23 12:21 UTC, Juha Heljoranta
kernel config file (paska,30.40 KB, text/plain)
2005-08-23 12:22 UTC, Juha Heljoranta
/etc/make.conf (makeconf,678 bytes, text/plain)
2005-08-23 12:23 UTC, Juha Heljoranta
Backtrace from 2.6.13-rc7 (2.6.13-rc7-problem,1.25 KB, text/plain)
2005-08-24 12:54 UTC, Juha Heljoranta

Note You need to log in before you can comment on or make changes to this bug.
Description Juha Heljoranta 2005-08-23 12:17:42 UTC
System becomes unstable when using ondemand cpu scaling governor on kernel. 

Typical scenario: power up, surf the net, read main, emerge stuff and crash.

Typically X crashes without warning or system just reboots. This could happen at
any time: while computer does nothing paticular or middle of, say, emerge
process. Sometimes browser or mail client becomes really sticky and behave oddly
before system hangs it self.

My current kernel is 2.6.12-gentoo-r9 and I enabled ondemand governor by adding
line "echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" to

I've seen exactly the same symptoms on other kernels (roughly 2.6.9 - 2.6.10)
but on that time I just decided to stick with the default governor (performance)
until now.

Reproducible: Always
Steps to Reproduce:
1. power on
2. emerge stuff, surf net, read mail, watch a divx movie, etc.
3. system lockup/crash or processes start to misbehave and eventually system
will die
Comment 1 Juha Heljoranta 2005-08-23 12:21:51 UTC
Created attachment 66677 [details]
Debug infromation from /var/log/kern.log

The only useful error messages that I have managed to catch.
Comment 2 Juha Heljoranta 2005-08-23 12:22:36 UTC
Created attachment 66678 [details]
kernel config file
Comment 3 Juha Heljoranta 2005-08-23 12:23:20 UTC
Created attachment 66679 [details]
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2005-08-23 12:38:09 UTC
So this *only* happens with the ondemand governor, no others? (You didn't
include this in "Steps to reproduce")

Can you reproduce this on the latest development kernel (currently
Comment 5 Juha Heljoranta 2005-08-24 12:51:44 UTC
Yes, this happens only when ondemand cpu scheduler is used.

And yes, I can reproduce this on 2.6.13-rc7 vanilla. I didn't test 2.6.13-rc7
with performance governor to prove that the performance governor works. This
because my regular uptime is +30 days. With ondemand governor the uptime is 1-4
Comment 6 Juha Heljoranta 2005-08-24 12:54:27 UTC
Created attachment 66787 [details]
Backtrace from 2.6.13-rc7
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2005-08-26 02:41:16 UTC
Please file a bug against 2.6.13-rc7 at including the
info that you have posted here. Please post the new bug URL here then I will
keep an eye on it.
Comment 8 Juha Heljoranta 2005-08-28 09:48:23 UTC
Comment 9 Daniel Drake (RETIRED) gentoo-dev 2007-04-29 14:52:27 UTC
fixed with recent kernel releases