From: Jens Axboe <axboe@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: J Sloan <jjs@pobox.com>, J Sloan <jjs@lexus.com>,
Robert Love <rml@tech9.net>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: preempt-patch cleared of blame
Date: Thu, 8 Nov 2001 12:38:08 +0100 [thread overview]
Message-ID: <20011108123808.I27652@suse.de> (raw)
In-Reply-To: <20011108113615.F27652@suse.de> <Pine.LNX.4.33.0111081322570.8555-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0111081322570.8555-100000@localhost.localdomain>
On Thu, Nov 08 2001, Ingo Molnar wrote:
>
> On Thu, 8 Nov 2001, Jens Axboe wrote:
>
> > On Wed, Nov 07 2001, J Sloan wrote:
> > > I think there may be a problem with the
> > > compaq smart/2p raid drivers, since
> > > the "do_ida_intr" code keeps showing
> > > up in the oops, and I have not seen a
> > > problem with 2.4.14 on any other system.
> >
> > Does this fix it?
>
> it did the trick on my system, which used to oops in/around do_ida_intr as
> well.
Good, so it was a dequeue race. Thanks Ingo.
--
Jens Axboe
next prev parent reply other threads:[~2001-11-08 11:38 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
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 [this message]
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=20011108123808.I27652@suse.de \
--to=axboe@suse.de \
--cc=jjs@lexus.com \
--cc=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.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