Bug 5133
Summary: | Ondemand governor makes system unstable | ||
---|---|---|---|
Product: | Power Management | Reporter: | Juha Heljoranta (juha) |
Component: | cpufreq | Assignee: | cpufreq (cpufreq) |
Status: | CLOSED CODE_FIX | ||
Severity: | high | CC: | diegocg, kernel |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.13-rc7 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
backtraces from 2.6.12-gentoo-r9
kernel-2.6.12-gentoo-r9 config backtrace from 2.6.13-rc7 backtrace from 2.6.13 |
Description
Juha Heljoranta
2005-08-26 12:50:51 UTC
Created attachment 5774 [details]
backtraces from 2.6.12-gentoo-r9
Created attachment 5775 [details]
kernel-2.6.12-gentoo-r9 config
Created attachment 5776 [details]
backtrace from 2.6.13-rc7
Note that the system didn't start to show symptoms immediatetly after backtraces appeared, but little while after messages (like hour or two). Created attachment 5831 [details]
backtrace from 2.6.13
I enabled cpufreq debug but I haven't noticed anything interesting, except lot
of 'printk: xx messages suppressed' -messages.
Is there anything that I could do to get this bug fixed?
Downstream bug report: http://bugs.gentoo.org/show_bug.cgi?id=103497 What is the state of this bug? no response from reporter, marking as NEEDINFO It seems that the ondemand cpufreq scaling governor has been fixed some where between 2.6.14 and 2.6.17. Ondemand governor has been my default cpu frequency governor at least since 2.6.18. I might have used it with 2.6.17. IIRC I tried to use ondemand with 2.6.14 and 2.6.15 but with same symptoms. Great, thanks for the update. |