From: Robert Love <rml@tech9.net>
To: Steven Cole <elenstev@mesatop.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.37 lockup with dbench 36 and make -j3 bzImage and PREEMPT=y.
Date: 23 Sep 2002 14:32:29 -0400 [thread overview]
Message-ID: <1032805949.25745.21.camel@phantasy> (raw)
In-Reply-To: <1032797370.28405.5.camel@spc9.esa.lanl.gov>
On Mon, 2002-09-23 at 12:09, Steven Cole wrote:
> Further testing with 2.5.37 over the weekend showed that the lockup also
> occurred without preempt here too.
>
> This seems to have been fixed in 2.5.38-mm2. I've run up to dbench 128
> while doing several kernel compiles with make -j3 with PREEMPT enabled,
> and have not observed any lockups at all.
Excellent. Thanks a lot for this update.
I appreciate your testing, Steven. Any future preempt-related lock ups
please let me know.
Robert Love
prev parent reply other threads:[~2002-09-23 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 21:05 2.5.37 lockup with dbench 36 and make -j3 bzImage and PREEMPT=y Steven Cole
2002-09-21 10:05 ` Helge Hafting
2002-09-23 16:09 ` Steven Cole
2002-09-23 18:32 ` 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=1032805949.25745.21.camel@phantasy \
--to=rml@tech9.net \
--cc=elenstev@mesatop.com \
--cc=helgehaf@aitel.hist.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox