From: Robert Love <rml@tech9.net>
To: J Sloan <jjs@lexus.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: disaster with 2.4.14+preempt
Date: 07 Nov 2001 17:30:36 -0500 [thread overview]
Message-ID: <1005172239.939.2.camel@phantasy> (raw)
In-Reply-To: <3BE9A506.82D64AE4@lexus.com>
In-Reply-To: <3BE8B460.A23E1A67@pobox.com> <1005109646.884.0.camel@phantasy> <3BE9A506.82D64AE4@lexus.com>
On Wed, 2001-11-07 at 16:17, J Sloan wrote:
> Is there anything in particular you would
> like me to try?
Confirm 2.4.13+preempt doesn't cause the problem.
If it doesn't, can you try recompiling with the newest 2.4.13
preempt-kernel patch. I forget from which version we removed the atomic
operators, but I want to confirm this is not the problem.
Confirm 2.4.14 doesn't cause the problem.
(if possible) confirm 2.4.14+preempt does indeed cause the problem.
Let me just spit out my thinking here:
Is it preempt?
Is it something in 2.4.14 annoying preempt?
Is it the non-atomicity recently introduced?
Robert Love
next prev parent reply other threads:[~2001-11-07 22:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 4:11 disaster with 2.4.14+preempt J Sloan
2001-11-07 5:07 ` Robert Love
2001-11-07 6:52 ` J Sloan
2001-11-07 21:17 ` J Sloan
2001-11-07 22:30 ` Robert Love [this message]
2001-11-08 3:48 ` preempt-patch cleared of blame J Sloan
2001-11-08 10:36 ` Jens Axboe
2001-11-08 12:23 ` Ingo Molnar
2001-11-08 11:38 ` Jens Axboe
2001-11-08 11:41 ` [patch] cciss dequeue race fix (was Re: preempt-patch cleared of blame) Jens Axboe
2001-11-08 12:05 ` AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go Cyrus
2001-11-08 17:14 ` Robert Love
2001-11-09 0:45 ` David S. Miller
2001-11-08 22:04 ` Jussi Laako
2001-11-08 23:28 ` Alan Cox
2001-11-09 21:04 ` Jussi Laako
2001-11-15 23:25 ` Stephen C. Tweedie
2001-11-11 7:59 ` AMD761Agpgart+Radeon64DDR+kernel+2.4.15-pre2...still testing Cyrus
2001-11-09 1:35 ` Success with 2.4.14 on Compaq 6500 J Sloan
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=1005172239.939.2.camel@phantasy \
--to=rml@tech9.net \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.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.