From: Mark Rutherford <mark@justirc.net>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ide harddisk freeze WDC WD1800JB vs VIA VT8235
Date: Wed, 01 Jan 2003 10:59:58 -0500 [thread overview]
Message-ID: <3E13107E.3D579F3@justirc.net> (raw)
In-Reply-To: 1041435181.983.76.camel@sun
Q: are you using cables with a slave connector, but its not in use?
I had this problem, with this chipset and it turned out that it didnt like
having
a long 80 wire cable with a loose connector
I got a round cable with just 2 connectors, 1 for the board and 1 for the
drive....
never locked again.
I thought it to be strange as well.
but with my setup it happened more frequently, say once every 2-3 hours.
hope this is of any help.
Soeren Sonnenburg wrote:
> Hi.
>
> I still get harddisk freezes on 2 WD1800JB drives (asus A7V8X mobo),
> i.e., I have to powercycle the system to get the harddisk back working.
> A cold reset is not enough.
>
> The harddisks are connected to the primary and secondary via vt8235
> controller (both disks are master).
>
> When a harddisk 'freezes' the ide-light is continuosly on. When that
> happens the machine is still ping-able but since these two disk form a
> software raid0 the machine hangs on disk access.
>
> This problem happens like once in a week....and very seldom within 3
> days.
>
> The system is athlon xp 2.4G+ a7v8x mainboard 1.5g ddr333 memory kernel
> 2.4.21-pre2 (did not work with 2.4.20 that is why I went to the pre
> version)
>
> So far I have ruled out the following:
> - it is not a cable problem (tested several cables)
> - the memory of the machine seems to be ok (memtest ran for 2 days
> without reporting an error)
> - it is not a problem of the power supply (tested another powersupply)
> - the harddisk are ok ( I ran the vendors check program )
>
> Now it could be that the via vt8235 chipset has a bug, the linux ide
> handling code is buggy or the firmware of the drive is not ok.
>
> It is probably a vt8235 problem or linux driver problem since a I know
> of 8 wdc1800jb disks with that firmware version running since >1month in
> a hardware raid setup without problems.
>
> I attached the kernel config, dmesg, and hdparm -I of one of the drives.
>
> If you have any ideas/ need further infos don't hesitate to contact me.
>
> Thanks in advance,
> Soeren.
>
> ------------------------------------------------------------------------
> Name: config
> config Type: Plain Text (text/plain)
> Encoding: 7bit
>
> Name: dmesg
> dmesg Type: Plain Text (text/plain)
> Encoding: 7bit
>
> Name: hdparm
> hdparm Type: unspecified type (application/octet-stream)
> Encoding: quoted-printable
--
Regards,
Mark Rutherford
mark@justirc.net
next prev parent reply other threads:[~2003-01-01 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 15:33 ide harddisk freeze WDC WD1800JB vs VIA VT8235 Soeren Sonnenburg
2003-01-01 15:59 ` Mark Rutherford [this message]
2003-01-01 16:17 ` Soeren Sonnenburg
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 7:48 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=3E13107E.3D579F3@justirc.net \
--to=mark@justirc.net \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.