From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "David Flynn" <Dave@keston.u-net.com>,
"linux kernel mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: Via KT133 and 2.4.8 and a hard disk problem ?
Date: Sun, 28 Oct 2001 13:34:07 +0100 [thread overview]
Message-ID: <00b201c15fac$d633fef0$0201a8c0@HOMER> (raw)
In-Reply-To: <045301c15fa7$c2809b70$1901a8c0@node0.idium.eu.org>
I often get these kinds of problems with semi-old HD's (UDMA33) when I run
*anything* else than DMA enabled (like when I run stuff like
hdparm -c1 -m16 -u1). It could also be a hard drive reporting the wrong
capabilities to the IDE controller.
A "hdparm /dev/hdX" and "hdparm -I /dev/hdX" would be most helpful to
diagnose your problem.
/Martin (fresh & new to l-k)
----- Original Message -----
From: "David Flynn" <Dave@keston.u-net.com>
To: "linux kernel mailinglist" <linux-kernel@vger.kernel.org>
Sent: Sunday, October 28, 2001 12:57 PM
Subject: Via KT133 and 2.4.8 and a hard disk problem ?
> All;
>
> What is the status of the problems with the old KT133 and kernel 2.4.8 ?
>
> I have a system here which looks to me as if its beginning to suffer from
> HDD failure, just do anything with the disk for a while and you get disk {
> busy } errors (and there is an 0x0d error code there somewhere) ... (oh,
and
> the HDD light reports no activity) normally, i would view this as a good
> time to pull all the data off the drive and replace it.
>
> However, i have noticed that the chipset used is the Via KT133, and am now
> wondering if this is actually a HDD problem (i still am siding with this)
or
> a chipset problem.
<snip>
next prev parent reply other threads:[~2001-10-28 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 11:57 Via KT133 and 2.4.8 and a hard disk problem ? David Flynn
2001-10-28 12:34 ` Martin Eriksson [this message]
2001-10-28 20:46 ` David Grant
2001-10-28 22:03 ` Martin Eriksson
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='00b201c15fac$d633fef0$0201a8c0@HOMER' \
--to=nitrax@giron.wox.org \
--cc=Dave@keston.u-net.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