From: Willy Tarreau <willy@w.ods.org>
To: evil <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lockups with 2.4.2x
Date: Sun, 21 Sep 2003 07:38:16 +0200 [thread overview]
Message-ID: <20030921053816.GD589@alpha.home.local> (raw)
In-Reply-To: <3F6D134E.2080505@g-house.de>
On Sun, Sep 21, 2003 at 04:56:14AM +0200, evil wrote:
> the machine:
> Dual Athlon, 1GB RAM (HighMem enabled), gcc 3.3.1, libc 2.3.2,
> (Debian/Testing) some more infos are on:
>
> http://nerdbynature.de/bits/freeze/config|cpuinfo|dmesg|lspci
Hmmm, there is a lot of hardware in this box. Have you tried disabling IDE ?
ServeRaid ? SymBIOS ? Your hangs may be related to an updatedb or slocate
indexing all your filesystems, and triggering a bug in one of those drivers.
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 ?
You could also try to boot in 'nosmp' mode, and even with network unplugged.
I believe it will be relatively quick to find the problem if the system
usually hangs in no more than 3 minutes.
You may also have a defect in your RAM. Someone else here had problems since
2.4.20, and only when saving disks to tape. It was finally tracked down to
a RAM problem which only showed up on SMP with newer kernels which seem to
torture the hardware a bit more. So if your GB ram is 4*256, you can try to
remove 2 sticks and see what happens.
Hope this helps,
Willy
next prev parent reply other threads:[~2003-09-21 5:38 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 [this message]
2003-09-21 13:26 ` Christian
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=20030921053816.GD589@alpha.home.local \
--to=willy@w.ods.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox