From: Robert Love <rml@tech9.net>
To: Steve Bergman <steve@rueb.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fully preemptible kernel
Date: 26 Dec 2001 15:13:50 -0500 [thread overview]
Message-ID: <1009397641.4966.5.camel@phantasy> (raw)
In-Reply-To: <1009396922.1678.9.camel@voyager.rueb.com>
In-Reply-To: <1007930466.11789.2.camel@phantasy> <1009396922.1678.9.camel@voyager.rueb.com>
On Wed, 2001-12-26 at 15:02, Steve Bergman wrote:
> I just compiled 2.4.17 with the patch from your site that looks to be
> for 2.4.17-final. Unfortunately, several modules (e.g. unix.o) fail on
> load with an undefined symbol error (preempt_schedule). FWIW, I also
> have the patch that started the recent "Make highly niced processes run
> only when idle" thread. Which reminds me, I'm anxious to try out your
> "fixed" version of SCHED_IDLE when it's ready. ;-)
If there is no compile error, it is probably mismatched modules, because
preempt_schedule is properly exported.
Make sure your kernel tree is fully patched and CONFIG_PREEMPT is
enabled. Rerun `make dep' and then recompile (including your modules).
Make sure your modules are properly installed.
Either your running kernel doesn't have preemption enabled or your
kernel does but your modules don't (i.e. they are old modules).
Robert Love
next prev parent reply other threads:[~2001-12-26 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 20:41 [PATCH] fully preemptible kernel Robert Love
2001-12-10 10:54 ` vda
2001-12-10 7:03 ` Robert Love
2001-12-10 12:29 ` vda
2001-12-10 16:08 ` vda
2001-12-10 17:25 ` vda
2001-12-10 13:55 ` Wilson
2001-12-26 20:02 ` Steve Bergman
2001-12-26 20:13 ` Robert Love [this message]
2001-12-31 13:29 ` Heinz Diehl
2001-12-31 16:14 ` ncw
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=1009397641.4966.5.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@rueb.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox