From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ide harddisk freeze WDC WD1800JB vs VIA VT8235
Date: 02 Jan 2003 08:48:19 +0100 [thread overview]
Message-ID: <1041493699.958.0.camel@sun> (raw)
On Wed, 2003-01-01 at 18:37, Mark Hahn wrote:
> ide cables are <= 18", PERIOD. if only one connnector is used,
> it must be the end one. this is all quite clear in the ATA spec.
the flat cables I tried were all ~24cm < 18" (tried two different
sets)... I have not measured the length of the round cables...
> the original poster should consider simplifying his system first:
> for instance, don't load all the random IO devices, especially not
> the NVidia module, consider testing with ext2/3, etc.
I don't see the point with this. This system (with a K7- and older via
chipset) was working reliably. All that changed is 180G harddisks +
mainboard + processor.
Anyway the kernel is not crashing and it is very unlikely that a bug in
whatever io device will cause this specific problem reproducably with
different kernel versions isn't it ?
Especially changing the file system type will not gain anything....
However it *might* be that this is some 48bit ide-access problem as both
disks are 180G in size.
Unfortunately I failed to trigger the problem, i.e. I could run
badblocks -p 0 /dev/hda and at the same time for /dev/hdc for more then
a day (>16 passes) without any trouble.
So it sounds as if the problem to occur is very very unlikely... IMHO
this is some 'failure of transfer' between disk and controller... and
this error condition is not properly handled...
Not the slightest idea what that could be....
Soeren.
next reply other threads:[~2003-01-02 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 7:48 Soeren Sonnenburg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 15:33 ide harddisk freeze WDC WD1800JB vs VIA VT8235 Soeren Sonnenburg
2003-01-01 15:59 ` Mark Rutherford
2003-01-01 16:17 ` Soeren Sonnenburg
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=1041493699.958.0.camel@sun \
--to=kernel@nn7.de \
--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