| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <473CD838.8060300@lifl.fr> Date: Fri, 16 Nov 2007 00:37:28 +0100 From: Eric Piel <Eric.Piel@...l.fr> To: trenn@...e.de CC: linux-kernel@...r.kernel.org, Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>, Dave Jones <davej@...hat.com>, cpufreq <cpufreq@...ts.linux.org.uk> Subject: Re: Kernel panic at boot with ondemand governor as default (2.6.24-rc2) 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists