lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 12 Nov 2007 10:16:52 +0100
From:	Thomas Renninger <>
To:	Eric Piel <>
	Venkatesh Pallipadi <>,
	Dave Jones <>
Subject: Re: Kernel panic at boot with ondemand governor as default

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?


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

Powered by blists - more mailing lists