From: Christian <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: lockups with 2.4.2x
Date: Sun, 21 Sep 2003 15:26:34 +0200 [thread overview]
Message-ID: <3F6DA70A.6030100@g-house.de> (raw)
In-Reply-To: <20030921053816.GD589@alpha.home.local>
Willy Tarreau wrote:
> Hmmm, there is a lot of hardware in this box. Have you tried disabling IDE ?
> ServeRaid ? SymBIOS ?
hm, yes, i could disable the ServeRaid module. gotta find out how to
disable the builtin IDE / Symbios other than recompile the kernel...
can i do this by giving "ide0=noprobe ide1=noprobe ..." on the
boot-prompt? my rootdisk used to be on hda, will see if i can do something.
> Also, the DMESG shows that you have an AMD bug on your CPUs, and tells you
> that if you have problems, you should restart with 'noapic'. Did you try it ?
Oh, no, I did not. sorry. i'll try it.
> You could also try to boot in 'nosmp' mode, and even with network unplugged.
hm, will try this too.
> I believe it will be relatively quick to find the problem if the system
> usually hangs in no more than 3 minutes.
the worst thing on this machine is the pre-booting process, where all
the controllers are "Initializing..." and "Checking...", and even the
ServRaid controller wants to have 3 minutes sometimes to settle :-)
> You may also have a defect in your RAM.
even it is "ECC" RAM, i'll give it a try.
Thank your for the quick reply, i'll try these things out, will take
some time, so maybe i'm back in the evening.
Christian.
(if I only could use my .sig this time :-))
--
BOFH excuse #301:
appears to be a Slow/Narrow SCSI-0 Interface problem
next prev parent reply other threads:[~2003-09-21 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 2:56 lockups with 2.4.2x evil
2003-09-21 5:37 ` Christian
2003-09-21 5:38 ` Willy Tarreau
2003-09-21 13:26 ` Christian [this message]
2003-09-21 21:49 ` Christian
2003-09-23 0:23 ` Christian Kujau
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=3F6DA70A.6030100@g-house.de \
--to=evil@g-house.de \
--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.