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: Re: Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap
Date: Fri, 15 Feb 2002 15:22:21 -0800 [thread overview]
Message-ID: <20020215232221.GB5310@matchmail.com> (raw)
In-Reply-To: <20020215035135.0c26b130.rj@open-net.org> <1013780277.950.663.camel@phantasy> <20020215201810.GA5310@matchmail.com> <1013810411.803.1045.camel@phantasy>
In-Reply-To: <1013810411.803.1045.camel@phantasy>
On Fri, Feb 15, 2002 at 05:00:10PM -0500, Robert Love wrote:
> On Fri, 2002-02-15 at 15:18, Mike Fedyk wrote:
>
> > 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)
>
> The -mjc and similar patches make debugging a bit, uh, hard ;)
>
Yep, I understand. When I was patching in rmap12f I had to manually
merge the little bit into mm/bootmem.c and the offset was several hundred
lines. Then I realized just how much WLI's bootmem patch changes.
> > I'm running 2.4.18-pre9-ac3 now to see if I can reproduce without prempt and
> > O(1).
>
> If you can't reproduce it, I'd like to see if you can reproduce it
> _only_ with preempt. Also, if it happens on stock pre9 (no -ac) would
> be of interest, since that doesn't have Andre's IDE patch.
>
Actually, I'm going to recompile -mjc2 without lock breaking to see if that
helps. Then try without prempt altogether. If either of those two fix the
problem, I'll see if I can reproduce against the latest kernel from marcello
and your latest patch and merge myself. Heh, I want to keep testing -mjc.
There are so many nice things in there. ;)
> > 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.
>
> Now this would be of interest, thanks.
>
I asked him to cc me so that I may be able to help too...
> Robert Love
Mike
next prev parent reply other threads:[~2002-02-15 23:22 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 ` Hard lockup with 2.4.18-pre9 + preempt + lock break + O1k[23] + rmap Mike Fedyk
2002-02-15 22:00 ` Robert Love
2002-02-15 23:22 ` Mike Fedyk [this message]
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=20020215232221.GB5310@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox