All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
	"Ed Tomlinson" <tomlins@cam.org>, "Ingo Molnar" <mingo@elte.hu>,
	"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] O(1) scheduler, -H4 - 2.4.17 problems
Date: 10 Jan 2002 22:41:36 -0500	[thread overview]
Message-ID: <1010720496.814.2.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.40.0201101910260.1493-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0201101910260.1493-100000@blue1.dev.mcafeelabs.com>

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


  reply	other threads:[~2002-01-11  3:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11  2:10 [patch] O(1) scheduler, -H4 - 2.4.17 problems Dieter Nützel
2002-01-11  2:42 ` Davide Libenzi
2002-01-11  3:00   ` Robert Love
2002-01-11  3:11     ` Davide Libenzi
2002-01-11  3:41       ` Robert Love [this message]
2002-01-11 16:27   ` Ingo Molnar
2002-01-11 14:47     ` Taco IJsselmuiden
     [not found] <Pine.LNX.4.33.0201111852340.5922-100000@localhost.localdomain>
2002-01-11 17:33 ` Taco IJsselmuiden
2002-01-12  4:49   ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2002-01-11  8:46 Alex Davis
2002-01-11  0:43 Ed Tomlinson
2002-01-11  0:52 ` khromy
2002-01-11  2:27 ` Robert Love

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=1010720496.814.2.camel@phantasy \
    --to=rml@tech9.net \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tomlins@cam.org \
    /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.