Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757964AbXKLJRI (ORCPT ); Mon, 12 Nov 2007 04:17:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753131AbXKLJQ4 (ORCPT ); Mon, 12 Nov 2007 04:16:56 -0500 Received: from mx2.suse.de ([195.135.220.15]:60044 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753027AbXKLJQz (ORCPT ); Mon, 12 Nov 2007 04:16:55 -0500 Subject: Re: Kernel panic at boot with ondemand governor as default (2.6.24-rc2) From: Thomas Renninger Reply-To: trenn@suse.de To: Eric Piel Cc: linux-kernel@vger.kernel.org, Venkatesh Pallipadi , Dave Jones In-Reply-To: <4737539F.2070401@lifl.fr> References: <4737539F.2070401@lifl.fr> Content-Type: text/plain Organization: Novell/SUSE Date: Mon, 12 Nov 2007 10:16:52 +0100 Message-Id: <1194859012.4590.595.camel@queen.suse.de> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1322 Lines: 33 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: [] 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? 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? Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/