From: Rolf Fokkens <FokkensR@vertis.nl>
To: linux-kernel@vger.kernel.org
Subject: [BUG] Total freeze of 2.4 kernel
Date: Thu, 9 Aug 2001 12:48:30 +0200 [thread overview]
Message-ID: <200108091048.MAA04335@linux06.vertis.nl> (raw)
This is not a detailed bug report, but it may nevertheless be interesting
for others that have the same problem. I have the impression that my first
report got lost somewhere, so this is the second attempt to post it.
We installed a 2.4.7 kernel on a Compaq Proliant server and it makes the
machine freeze totally at various moments. We've been running 2.4 on several
other non-server machines for a while without any problem at all, so we
tried to figure out what may be causing the problem. Here is a list of what
we know so far:
INITIAL SYMPTOMS
At totally unpredictable moments the sever hangs. Nothing on the display, no
keyboard led response, no disk activity, no ping response on the net.
2.2.19 KERNEL
The machine ran a 2.2.19 kernel prior to the 2.4.7 kernel without any
problems at all. Only kernel upgrades forced us to do reboots.
CPQHEALTH
There were Compaq cpqhealth modules in the kernel. Those are binary modules
from Compaq that help to gather health information about the machine. The
modules didn't load in a 2.4.7 kernel (cpqhealth 2.1 even created kernel
stack dumps when loaded in a 2.4.7 kernel on another machine) so we removed
the cpqhealth software. It didn't help.
CPQARRAY
This is the first machine with a Compaq SMART 3200 raid controller we tried
with 2.4.7. I don't believe this is causing the problem, but it's worth
mentioning I think.
MONITOR/MOUSE/KEYBOARD SWITCH
This also is the first machine with an electronic MONITOR/MOUSE/KEYBOARD
SWITCH. Last weekend the machine ran w/o any problems at all, but today
(monday) it had a hangup. We can be sure that nobody touched the switch
during the weekend and today at was used most certainly, so there may be a
relation between the switch and the hanging.
Of course we'll go on investigating this, but because the machine has a
semi-production status we have to do this with care. However suggestions are
wellcome.
Rolf
next reply other threads:[~2001-08-09 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 10:48 Rolf Fokkens [this message]
2001-08-10 1:30 ` [BUG] Total freeze of 2.4 kernel Keith Owens
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=200108091048.MAA04335@linux06.vertis.nl \
--to=fokkensr@vertis.nl \
--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