Re: Kernel panic at boot with ondemand governor as default (2.6.24-rc2)

Eric Piel
2007-11-12T23:10:30Z

2007年11月12日 21:26, Dave Jones wrote/a écrit:
> On Mon, Nov 12, 2007 at 04:23:09PM +0100, Thomas Renninger wrote:
> > On Mon, 2007-11-12 at 15:02 +0100, Eric Piel wrote:
:
> > > 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.
>
> I'm actually surprised that speedstep-ich works with a low enough
> latency for ondemand. On the kernel that works, can you boot
> with cpufreq.debug=7 and send the cpufreq messages from dmesg?
I'm not surprised, contrarly to speedstep-smi, speedstep-ich has been
working with ondemand for quite a long time, since commit
1a10760c91c394dfe4adfefeeaf85cd8098c4894 precisely :-) As stated in the
commit message, the latency transition is about 200µs, much smaller than
the 10ms required by ondemand. Actually, on my laptop the transition
time is set to even higher due to problems of measurement, but it's
still fine for ondemand. I get this at boot:
speedstep: frequency transition measured seems out of range (4800 nSec),
falling back to a safe one of 500000 nSec.

See you,
Eric