From: Eric Piel <Eric.Piel@lifl.fr>
To: trenn@suse.de
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: Fri, 16 Nov 2007 00:37:28 +0100 [thread overview]
Message-ID: <473CD838.8060300@lifl.fr> (raw)
In-Reply-To: <1194880989.5474.12.camel@queen.suse.de>
2007年11月12日 16:23, Thomas Renninger wrote/a écrit:
> On Mon, 2007-11-12 at 15:02 +0100, Eric Piel wrote:
:
>> 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...
Hi, I've just checked and it seems a bit weird, at least not as I
expected: the workqueue is already initialized _before_ cpufreq! At
least, from what I read in init/main.c, in do_basic_setup(), first there
is a call to init_workqueues(), then there is a call to do_initcalls()
(which indirectly calls cpufreq_core_init()). So maybe workqueues need
something more than being initialized to work? What could it be? (My
kernel is compiled for monoprocessor, I can't see what goes wrong in
wq_per_cpu()).
See you,
Eric
prev parent reply other threads:[~2007-11-15 23:37 UTC|newest]
Thread overview: 10+ 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
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 [this message]
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=473CD838.8060300@lifl.fr \
--to=eric.piel@lifl.fr \
--cc=cpufreq@lists.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.