From: Robert Love <rml@tech9.net>
To: Stephen Frost <sfrost@snowman.net>
Cc: Jordan Breeding <ledzep37@home.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Trouble with update Preemptive patch for 2.4.9-ac9
Date: 07 Sep 2001 16:37:50 -0400 [thread overview]
Message-ID: <999895073.2127.5.camel@phantasy> (raw)
In-Reply-To: <20010907072357.A11136@ns>
In-Reply-To: <3B985287.2385275B@home.com> <999839075.865.7.camel@phantasy> <20010907072357.A11136@ns>
On Fri, 2001-09-07 at 07:23, Stephen Frost wrote:
> If you need a guinea pig for testing it on SMP I may be willing
> to do that on one of my SMP machines. :) Let me know, I'll need
> to do some setup work (attaching and setting up a serial
> console, testing the machine without the patch to make sure it's
> mostly happy, etc).
I would certainly take you up on that offer. I honestly don't think the
patch is ready for SMP, yet -- but we have to start somewhere.
apply the patch and set CONFIG_SMP and CONFIG_PREEMPT to 'y' and let it
run. Any errors, OOPS, etc, pass them this way.
Unfortunately, if the patch fails, its going to fall hard. If the
preemption is imperfect during SMP, certainly you will hardlock.
It might help to enable CONFIG_DEBUG_SPINLOCKS and
CONFIG_DEBUG_BUGVERBOSE -- these are present in the -ac tree. The NMI
watchdog might prove useful, too.
But honestly, just telling me it locks on boot is useful, so whatever
you can manage.
I appreciate any help.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
prev parent reply other threads:[~2001-09-07 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 4:52 Trouble with update Preemptive patch for 2.4.9-ac9 Jordan Breeding
2001-09-07 5:04 ` Robert Love
2001-09-07 11:23 ` Stephen Frost
2001-09-07 20:37 ` Robert Love [this message]
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=999895073.2127.5.camel@phantasy \
--to=rml@tech9.net \
--cc=ledzep37@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrost@snowman.net \
/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