All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: Robert Love <rml@tech9.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: disaster with 2.4.14+preempt
Date: Wed, 07 Nov 2001 13:17:58 -0800	[thread overview]
Message-ID: <3BE9A506.82D64AE4@lexus.com> (raw)
In-Reply-To: <3BE8B460.A23E1A67@pobox.com> <1005109646.884.0.camel@phantasy>

Robert Love wrote:

> So I compiled 2.4.14+preempt, this time using ext2 like you.  I also
> enabled highmem and SMP, although I don't need those.  Again I ran
> multiple dbench runs, went into X, and here I am ... the kernel is
> solid.

OK I have replaced enough of the libs so that
rpm works again, and was able to do a verify
to get the rest of the pieces in order.

> What was the last kernel you had no problems with when used with
> preempt?

I was able to recover some stuff from old
backups, including the kernels I last used
under RH 7.1 -

I see vmlinuz-2.4.12-ac6, and vmlinuz-2.4.13
Both have preempt patches, and highmen
& smp support.

I know they were stable under the test.

I am pounding the old 2.4.13 kernel now
(filesystems mounted as ext2) with dbench
16, 32, 64, and 128 and it is holding up fine.

I will compile 2.4.14 without the preempt
patch and repeat -

Finally, I will repeat the 2.4.14+preempt
test, and I predict the box  will lock hard
a few seconds after typing "dbench 16"

Is there anything in particular you would
like me to try?

cu

jjs


  parent reply	other threads:[~2001-11-07 21:20 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 [this message]
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
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=3BE9A506.82D64AE4@lexus.com \
    --to=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.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.