From: Jurriaan <thunder7@xs4all.nl>
To: Svetoslav Slavtchev <galia@st-peter.stw.uni-erlangen.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6 test3-bk7 & -mm3 : HPT374 - cable missdetection, lock-ups
Date: Wed, 20 Aug 2003 21:35:18 +0200 [thread overview]
Message-ID: <20030820193518.GA1547@middle.of.nowhere> (raw)
In-Reply-To: <1061384019.3f436f531a333@secure.st-peter.stw.uni-erlangen.de>
From: Svetoslav Slavtchev <galia@st-peter.stw.uni-erlangen.de>
Date: Wed, Aug 20, 2003 at 02:53:39PM +0200
> Hi
>
> first test run of 2.6 on Epox 8k9a3+ VIA KT400 VT8235,
> HPT374 and 4 IBM Deskstar GXP120 80Gb on each chanel as master
> Mandrake-cooker gcc-3.3.1
>
> the 3rd and the 4th chanel of the HPT374 are saying that the used cable
> is 40 wires, so it forces the drives in UDMA33 which i think causes the lock-
> ups several seconds after booting in runlevel 1
>
As far as I know, I have no problems with my 3rd channel on my Epox
8K9A3+ motherboard. I've got a WD 80 Gb disk (8 Mb cache model) on it.
However, I've noticed something else.
As soon as I type
cat /proc/ide/hpt366
I get hit by the dreaded 'status=0x58 .... hdi interrupt lost' thing.
It tries to reset ide4, but keeps telling 'interrupt lost' and finally I
have to use the reset button. If I never cat /proc/ide/hpt366 I can run
the system for a week at a time, where hdi is part of a raid-0 partition
that contains both /home and my newsspool - so it's used frequently.
Kind regards,
Jurriaan
--
Carson heaved a sigh. "Easley tried to kill you. You retaliate by calling
yourself Jim Harrison. It seems a subtle revenge. Perhaps I'm stupid..."
Jack Vance - The Deadly Isles
Debian (Unstable) GNU/Linux 2.6.0-test3-mm3 4259 bogomips 1.04 0.41
next prev parent reply other threads:[~2003-08-20 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 12:53 2.6 test3-bk7 & -mm3 : HPT374 - cable missdetection, lock-ups Svetoslav Slavtchev
2003-08-20 19:35 ` Jurriaan [this message]
2003-08-20 20:47 ` Svetoslav Slavtchev
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 23:09 Duncan Laurie
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=20030820193518.GA1547@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=galia@st-peter.stw.uni-erlangen.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.