On Thu, 2002-01-10 at 22:11, Davide Libenzi wrote:
> Move init_idle() before the first call to kernel_thread().
> This should fix it.
On 2.4.17-pre3, UP, with -H5, the following patch failed to fix the
problem -- still hardlock on "Starting kswapd". I still suspect the
problem is with the init_idle changes, though ...
--- linux-2.4.18-pre3-ingo/init/main.c Thu Jan 10 21:13:12 2002
+++ linux/init/main.c Thu Jan 10 22:33:46 2002
@@ -590,14 +590,14 @@
check_bugs();
printk("POSIX conformance testing by UNIFIX\n");
+ smp_init();
+ init_idle();
kernel_thread(init, NULL, CLONE_FS | CLONE_FILES | CLONE_SIGNAL);
/*
* We count on the initial thread going ok
* Like idlers init is an unlocked kernel thread, which will
* make syscalls (and thus be locked).
*/
- smp_init();
- init_idle();
unlock_kernel();
printk("All processors have done init_idle\n");
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:33 EST