From: Brad Laue <brad@brad-x.com>
To: Brian Dushaw <dushaw@apl.washington.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Albatron KM18G PRO/RedHat 9.0 - disk errors and system seizures...
Date: Sun, 04 May 2003 21:55:55 -0400 [thread overview]
Message-ID: <3EB5C4AB.8000208@brad-x.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305041543440.8546-100000@munk.apl.washington.edu>
Brian Dushaw wrote:
> I've installed RedHat 9.0 three times now - going on the fourth. Most
> recently I upgraded the kernel with the RedHat update, to similar effect. The
> problem seems to be two fold: system lockups and disk errors.
The RedHat kernel is massively modified, especially in version 9.0 of
the distribution. Try a vanilla kernel and see if the system continues
to misbehave.
Brad
--
// -- http://www.BRAD-X.com/ -- //
next prev parent reply other threads:[~2003-05-05 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 23:10 Albatron KM18G PRO/RedHat 9.0 - disk errors and system seizures Brian Dushaw
2003-05-05 1:55 ` Brad Laue [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 3:19 Brian Dushaw
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=3EB5C4AB.8000208@brad-x.com \
--to=brad@brad-x.com \
--cc=dushaw@apl.washington.edu \
--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