From: "Andrew Scott" <A.J.Scott@casdn.neu.edu>
To: Pascal Haakmat <a.haakmat@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: Andre Hedrick's IDE patch saved my life
Date: Wed, 16 Jan 2002 15:30:03 -0500 [thread overview]
Message-ID: <3C459C7A.30004.EBDA61@localhost> (raw)
In-Reply-To: <20020112224005.A19577@awacs.dhs.org>
On 12 Jan 2002 at 22:40, Pascal Haakmat wrote:
> Well, that's perhaps not entirely true, but they did solve the mysterious
> and funny, and not so funny, problems that I was having with Oopses and
> filesystem corruption (kernel 2.4.16, 2xPIII/600MHz, PIIX4, XFS).
>
> Is there any reason at all why these patches are not part of the stock
> kernel? I mean the kernel just lost a disk of mine: is there any reason
> worth a disk of lost data?
Well, I've heard good things about the driver, but on one of my machines it
fails to boot _if_ the Maxtor 34098H4 (40 G) drive is connected using an 80
wire cable to an htp366 controller. If I use a 40 wire cable, it runs just
fine.
I have been through six 80 wire cables, just in case they were the problem.
However, the controller, drive and any of the 80 wire cables work just fine
on several other machines!
I do notice that the machine gets further into the boot than it used to.
Previously it would stall when mounting / with a error about 'waiting for
interrupt', I believe. Now mounts / but fails claiming a file that is being
loaded is corrupt. Swap the cables, and it is able to read the previously
'corrupted' file!
I suspect that the issue is that the machine is quite old, an HP dual
Pentium 200 (hp xu5/120, upgraded). It's memory speed is only about 25 MB/s,
which is slower than udma4! :)
_
/ \ / ascott@casdn.neu.edu
/ \ \ /
/ \_/
prev parent reply other threads:[~2002-01-16 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 21:40 Andre Hedrick's IDE patch saved my life Pascal Haakmat
2002-01-16 20:30 ` Andrew Scott [this message]
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=3C459C7A.30004.EBDA61@localhost \
--to=a.j.scott@casdn.neu.edu \
--cc=a.haakmat@chello.nl \
--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