From: Charlie Wilkinson <cwilkins@boinklabs.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Hard lock-ups on RH7.2 install - Via Chipset?
Date: Thu, 21 Feb 2002 12:49:59 -0500 [thread overview]
Message-ID: <20020221124959.A12456@boink.boinklabs.com> (raw)
In-Reply-To: <20020221110156.B9728@boink.boinklabs.com> <Pine.LNX.4.33.0202211106340.16271-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0202211106340.16271-100000@coffee.psychology.mcmaster.ca>; from hahn@physics.mcmaster.ca on Thu, Feb 21, 2002 at 11:07:11AM -0500
On Thu, Feb 21, 2002 at 11:07:11AM -0500, Mark Hahn waxed eloquent:
[...]
> > Hi Mark,
> > Yeah, Alan suggested his latest pre 2.4.18 kernel *might* work. Tried it,
> > still no joy. :/
>
> but HOW?
How did I try it, or how no joy? ;)
On the former, I didn't run any really exhaustive tests, and Alan
didn't suggest using or avoiding certain options. I built a relatively
conservative kernel and then beat on all four drives with concurrent dd's.
I also did an hdparm -tT. hdparm killed the box in a matter of a second
or two. dd took about 30 seconds. It seems safe to assume that hdparm
is able to create a higher load.
On the latter, the box just freezes up solid. No magic SysRq, no nothing.
A very frustrating state to try and troubleshoot. Any suggestions?
-cw-
next parent reply other threads:[~2002-02-21 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2002-02-22 20:21 Michael B Allen
-- strict thread matches above, loose matches on Subject: below --
2002-02-12 15:56 Charlie Wilkinson
[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
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=20020221124959.A12456@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®