From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>
Cc: Robert Jameson <rj@open-net.org>, linux-kernel@vger.kernel.org
Subject: Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap
Date: Fri, 15 Feb 2002 12:18:10 -0800 [thread overview]
Message-ID: <20020215201810.GA5310@matchmail.com> (raw)
In-Reply-To: <20020215035135.0c26b130.rj@open-net.org> <1013780277.950.663.camel@phantasy>
In-Reply-To: <1013780277.950.663.camel@phantasy>
On Fri, Feb 15, 2002 at 08:37:52AM -0500, Robert Love wrote:
> On Fri, 2002-02-15 at 03:51, Robert Jameson wrote:
> > I have been seeing this oops from 2.4.16 -> 2.4.18-pre9, so here we go!
>
> Do you see this on device close? It looks like there may be a race
> between device closer -> usb release.
>
I don't use USB, and I have had several machines lock up hard while doing
medium to heavy IO. I've had this happen with pre9-mjc2 and another patch
that just contained pre9-preempt-schedo1
(nyu.dyn.dhs.org:8080/patches/2.4.18-pre9-to-rmap12e-schedO1-rml.patch.bz2)
I'm running 2.4.18-pre9-ac3 now to see if I can reproduce without prempt and
O(1).
I have someone else from IRC that has the same issue with prempt+O(1)
against vanilla 2.4.17. He should be sending you a bug report soon.
BTW, all machines ran the same kernel compiled for SMP, but some machines
were UP.
Has anyone else seen this?
Mike
next prev parent reply other threads:[~2002-02-15 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 8:51 oops with 2.4.18-pre9-mjc2 Robert Jameson
2002-02-15 8:55 ` William Lee Irwin III
2002-02-15 13:29 ` Michael Cohen
2002-02-15 13:37 ` Robert Love
2002-02-15 15:20 ` Robert Jameson
2002-02-15 15:30 ` Arjan van de Ven
2002-02-15 17:48 ` Alan Cox
2002-02-15 19:15 ` Robert Love
2002-02-15 20:18 ` Mike Fedyk [this message]
2002-02-15 22:00 ` Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap Robert Love
2002-02-15 23:22 ` Mike Fedyk
2002-02-15 23:30 ` William Lee Irwin III
2002-02-15 23:42 ` Mike Fedyk
2002-02-16 9:29 ` Zwane Mwaikambo
2002-02-15 14:26 ` oops with 2.4.18-pre9-mjc2 Alan Cox
2002-02-15 16:07 ` Greg KH
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=20020215201810.GA5310@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rj@open-net.org \
--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 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.