public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Eric Piel <Eric.Piel@lifl.fr>
Cc: linux-kernel@vger.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Dave Jones <davej@redhat.com>,
	cpufreq <cpufreq@lists.linux.org.uk>
Subject: Re: Kernel panic at boot with ondemand governor as default	(2.6.24-rc2)
Date: Mon, 12 Nov 2007 16:23:09 +0100	[thread overview]
Message-ID: <1194880989.5474.12.camel@queen.suse.de> (raw)
In-Reply-To: <47385D05.20705@lifl.fr>

On Mon, 2007-11-12 at 15:02 +0100, Eric Piel wrote:
> 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:
> >> 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?
> 
> 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?
Making all this work with low-level drivers built in would be perfect of
course...
If nobody answers the next days, could you open a bug at
bugzilla.kernel.org, so that this does not get lost, pls.
Add myself and Venkatesh to CC...
I try to have a look at it ASAP.
If someone already finds out more, this would be great.

Thanks,

   Thomas


  reply	other threads:[~2007-11-12 15:23 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
2007-11-12  9:16 ` Thomas Renninger
2007-11-12 14:02   ` Eric Piel
2007-11-12 15:23     ` Thomas Renninger [this message]
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=1194880989.5474.12.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=Eric.Piel@lifl.fr \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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