[lkml]   [2007]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Kernel panic at boot with ondemand governor as default (2.6.24-rc2)
11/12/2007 10:16 AM, Thomas Renninger wrote/a écrit:
> On Sun, 2007-11-11 at 20:10 +0100, Eric Piel wrote:
>> Hello,
>> I've tried kernel 2.6.24-rc2 and I have a problem with the new option
>> for setting up the cpufreq ondemand governor as default: a kernel panic
>> happens early at boot time. If I boot first with performance governor
>> and later change to ondemand, everything is fine (as usual).
>> This seems related to the delayed_workqueue. The kernel panic message
>> finishes by:
>> EIP: [<c012aa60>] wq_per_cpu+0x0/0x10 SS:ESP 0068:c191be58
>> Kernel panic - not syncing: Attempted to kill init!
>> A picture of the whole message is available here:
>> My computer is a x86 using speedstep-ich, and you can find the full
>> .config leading to the panic attached.
>> Does anyone has any idea was it going wrong?
> Does it work if you compile speedstep-ich as a module?
> If you load it, ondemand governor should still be set up automatically.
> If this works, could it be that the kernel does not like that
> queue_delayed_work_on is called that early?

Yes, it works if I compile speedstep-ich as module. I've put the module
in initramfs and as soon it is loaded, the ondemand governor is selected
and works.

However, do you think it's ok to prevent cpufreq drivers to be built-in
if ondemand governor is selected as default? Another way would be to
reorganise the initialisation code so that workqueue is initialised
before the cpufreq framework is started, do you think it's possible?

See you,

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-11-12 15:31    [W:0.121 / U:3.628 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site