From: Jeff Lessem <Jeff.Lessem@Colorado.EDU>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.3 Crash - (Kernel BUG at highmem.c:155)
Date: Tue, 10 Apr 2001 13:49:32 -0600 [thread overview]
Message-ID: <200104101949.NAA208788@ibg.colorado.edu> (raw)
In-Reply-To: <0104101811150C.25951@webman>
I also have seen the Kernel BUG at highmem.c:155 problem on a machine
I am testing. It is a Dell 8 processor P-III 700Mhz with 8GB of
memory and Linux 2.4.3 + a knfsd and quota patch for reiserfs. When
doing 5 simultaneous kernel compiles from another machine mounting the
8 processor one over nfs the 8 processor machine hung with an error
message somewhat like
nfsd: terminating on signal 2
kernel BUG at highmem.c: 155!
invalid operand: 0000
CPU: 6
I apologize for the nearly useless error information, but I am 5000
miles and 7 time zones away from this machine, so I have to depend on
others for getting me on console information until I can get it moved
over to a serial console.
>Occassional lockups lasting 5-20 seconds were experienced when working on the
>box under 2.4.2 but seem to be much better in 2.4.3.
The machine is also having these odd lockup problems under intense
disk IO, but I will detail that in another message (look for "kswapd,
kupdated, and bdflush at 99%").
Any advice to alleviate this problem would be appreciated, and I will
provide any more information I can upon request.
--
Thanks,
Jeff Lessem.
prev parent reply other threads:[~2001-04-10 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 16:11 Marcin Kowalski
2001-04-10 19:49 ` Jeff Lessem [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=200104101949.NAA208788@ibg.colorado.edu \
--to=jeff.lessem@colorado.edu \
--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
all inboxes | Powered by JetHome®