Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 10 Jan 2002 22:39:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 10 Jan 2002 22:39:16 -0500 Received: from zero.tech9.net ([209.61.188.187]:30477 "EHLO zero.tech9.net") by vger.kernel.org with ESMTP id ; Thu, 10 Jan 2002 22:39:05 -0500 Subject: Re: [patch] O(1) scheduler, -H4 - 2.4.17 problems From: Robert Love To: Davide Libenzi Cc: Dieter =?ISO-8859-1?Q?N=FCtzel?= , Ed Tomlinson , Ingo Molnar , Linux Kernel List In-Reply-To: In-Reply-To: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.0.99+cvs.2001.12.18.08.57 (Preview Release) Date: 10 Jan 2002 22:41:36 -0500 Message-Id: <1010720496.814.2.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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/