lists.openwall.net   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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 11 Nov 2007 14:45:23 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Eric Piel <Eric.Piel@...l.fr>
Cc:	Thomas Renninger <trenn@...e.de>, linux-kernel@...r.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Dave Jones <davej@...hat.com>
Subject: Re: Kernel panic at boot with ondemand governor as default
 (2.6.24-rc2)

On Sun, 11 Nov 2007 20:10:23 +0100
Eric Piel <Eric.Piel@...l.fr> 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:
> http://pieleric.free.fr/unorder/1162-ondemand-panic.jpg
> 
> 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?
> Thanks,
> Eric
> 
> PS: I haven't tried 2.6.24-rc1.
> 

has ondemand ever worked for you?


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ