From: Charlie Wilkinson <cwilkins@boinklabs.com>
To: linux-kernel@vger.kernel.org
Subject: Hard lock-ups on RH7.2 install - Via Chipset?
Date: Tue, 12 Feb 2002 10:56:58 -0500 [thread overview]
Message-ID: <20020212105658.D11655@boink.boinklabs.com> (raw)
Greetings fellow bit jockeys,
This has been driving me nuts for over a week now. All discussion
found and solutions tried so far have proven fruitless. If someone
could point me at a fix or offer any insights, I would be most thrilled.
I've read about some Athlon/Via related problems, so I'm hoping it fits
in with that somehow.
The box is a AMD 1.3GHz Athlon with a "bcm Advanced Research" BC133KT-100
motherboard (Via KT133/VT8363/686B), two Promise Ultra100Tx2 cards, and
an IBM 75gb drive on each IDE channel (four drives in all). The graphics
card is an Nvidia TNT2 AGP, but I'm thinking that doesn't matter too
much as the problem occurs just fine in character mode with no activity
on the screen. I've yanked out network cards, disabled unused ports,
picked conservative BIOS settings, but to no avail.
The problem first occurred when I tried to do a RH7.2 install. I set
each drive up identically, creating a software RAID5 container across all
four drives. The box consistently freezes solid either while creating
the ext3 filesystem on RAID5, or in the early phases of the .rpm march.
(Note that means concurrent load on all four drives...)
Numerous things tried... Finally booted into rescue mode (starting with
the latest RH7.2 updated boot image, FWIW) and tried running concurrent
dd's out to the drives in various combinations, as in:
(dd if=/dev/zero of=/dev/hde2 &) ; (dd if=/dev/zero of=/dev/hdg2 &) ; etc...
What I found was that writing out to any two drives was fine. Writing to
all four will consistently lock up the machine after about 5-10 seconds.
So it seems load related. (No, I didn't try three drives.)
Any clues? Any fixes? Pretty please? :)
-cw-
next reply other threads:[~2002-02-12 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 15:56 Charlie Wilkinson [this message]
[not found] ` <E16agiR-0002Sv-00@the-village.bc.nu>
2002-02-21 15:57 ` Charlie Wilkinson
2002-02-21 16:33 ` Alan Cox
2002-02-21 18:02 ` Charlie Wilkinson
2002-04-18 20:29 ` Charlie Wilkinson
[not found] <20020221110156.B9728@boink.boinklabs.com>
[not found] ` <Pine.LNX.4.33.0202211106340.16271-100000@coffee.psychology.mcmaster.ca>
2002-02-21 17:49 ` Charlie Wilkinson
2002-02-22 20:21 Michael B Allen
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=20020212105658.D11655@boink.boinklabs.com \
--to=cwilkins@boinklabs.com \
--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®