public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@lifl.fr>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Thomas Renninger <trenn@suse.de>,
	linux-kernel@vger.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Dave Jones <davej@redhat.com>
Subject: Re: Kernel panic at boot with ondemand governor as default (2.6.24-rc2)
Date: Mon, 12 Nov 2007 01:38:52 +0100	[thread overview]
Message-ID: <4737A09C.1030200@lifl.fr> (raw)
In-Reply-To: <20071111144523.14164575@laptopd505.fenrus.org>

2007年11月11日 23:45, Arjan van de Ven wrote/a écrit:
> On Sun, 11 Nov 2007 20:10:23 +0100
> Eric Piel <Eric.Piel@lifl.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.

> 
> has ondemand ever worked for you?
Yes, ondemand works perfectly fine on this computer. The panic happens 
only if selecting it as the _default_ governor (which has been 
introduced by commit 1c2562459faedc35927546cfa5273ec6c2884cce).

Eric



  reply	other threads:[~2007-11-12  0:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 19:10 Kernel panic at boot with ondemand governor as default (2.6.24-rc2) Eric Piel
2007-11-11 22:45 ` Arjan van de Ven
2007-11-12  0:38   ` Eric Piel [this message]
2007-11-12  9:16 ` Thomas Renninger
2007-11-12 14:02   ` Eric Piel
2007-11-12 15:23     ` Thomas Renninger
2007-11-12 20:26       ` Dave Jones
2007-11-12 23:09         ` Eric Piel
2007-11-15 23:37       ` Eric Piel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4737A09C.1030200@lifl.fr \
    --to=eric.piel@lifl.fr \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox