public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.11 BUG vs 2.4.10-ac
Date: Wed, 10 Oct 2001 13:08:42 -0700	[thread overview]
Message-ID: <3BC4AACA.F7380F94@lexus.com> (raw)

Greetings -

I have had but little time to pursue the problems I reported
earlier, but I can provide some additional data points in the
hope that they may be of use here -

To recap, the system is a Compaq 6500 with 4 CPUs and 1.2
GB RAM.

Previously I reported that 2.4.11-pre kernels can all be reliably
made to lock hard within seconds, just by starting a dbench run.

I also reported that redhat roswell and rawhide kernels are solid
in this test, as is 2.4.10-ac6.

I have tested 2.4.11 final on this system, and sadly I must report
that it locks up hard within seconds of starting "dbench 16", and
although I booted Linux with verbose debugging and nmi_watchdog,
the oops scrolled by too quickly to catch, and as the system then
played possum, the PGUP, PGDN keys could not be used to scroll back
and inspect the oops, and the Magic SysRq keys also had no effect,
so I had to power cycle the box to revive it.

Just to confirm a hunch, I recompiled 2.4.11 with highmem support
disabled (So, it sees just under 1 GB RAM, no major loss), and
reran the dbench tests, with complete success - even with the load
up over 80 for an extended period of time, it would not fall over.

In short, it looks like a highmem bug, which is NOT in -ac.

cu,

jjs



                 reply	other threads:[~2001-10-10 20:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BC4AACA.F7380F94@lexus.com \
    --to=jjs@lexus.com \
    --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