From: Alois Treindl <alois@astro.ch>
To: linux-kernel@vger.kernel.org
Subject: Oops with kernel 2.4.5 on heavy disk traffic - reproduce
Date: Sun, 10 Jun 2001 13:52:54 +0200 [thread overview]
Message-ID: <3B235F96.E161B138@astro.ch> (raw)
I have reported before a kernel oops.
I now oberserved the same oops, with the same stack trace,
and a Dell Poweredge 1550 with dual CPU, 1 gb RAM, only
one disk and with little disk usage (most file activity via
NFS, where this system is a client).
The kernel is identical to the one reported before,
and the stack trace is identical too.
The oops occurred with the process 'top'
I have not yet found a way to reproduce the crash in a systematic
way, I am running the kernel now on 4 different machines
under heavy load, and will try to reproduce.
reply other threads:[~2001-06-10 11:53 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=3B235F96.E161B138@astro.ch \
--to=alois@astro.ch \
--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 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.