From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Lost interrupt with HPT370
Date: Sun, 12 Aug 2001 22:08:12 -0700 [thread overview]
Message-ID: <028101c123b5$f3d50040$6baaa8c0@kevin> (raw)
In-Reply-To: <E15Vvjz-0005k2-00@the-village.bc.nu>
I have just tried an HPT-366 card with IC35L040VER07 drives (latest DeskStar
41G ATA-100, although the card is only ATA-66) and could not get them to
even let me create a filesystem without hard locking the machine. This was
using 2.4.8-ac1 and 2.4.7-ac11. I wrote this off to motherboard/IDE card
compatibility (or lack thereof), but could it still be an IDE driver issue?
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Adam Huffman" <bloch@verdurin.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, August 12, 2001 6:57 AM
Subject: Re: Lost interrupt with HPT370
> > I get hde/hdg: lost interrupt messages when booting with 2.4.7/8.
> >
> > There are two IBM DTLA-307030 drives on the HPT370 interface (m/b is
> > Abit KA7-100).
> >
> > 2.4.6-ac5 (which I had been using for quite a while) does not have this
> > problem.
>
> The fixes you need to run certain HPT cards with certain drives (HPT370
> included) are not in the Linus tree. Its waiting Andre to submit the
> relevant stuff on to Linus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2001-08-13 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 12:49 Lost interrupt with HPT370 Adam Huffman
2001-08-12 13:57 ` Alan Cox
2001-08-13 5:08 ` Kevin P. Fleming [this message]
[not found] <no.id>
2001-08-13 11:37 ` Alan Cox
2001-08-13 17:23 ` Kevin P. Fleming
2001-08-14 7:49 ` Wojtek Pilorz
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='028101c123b5$f3d50040$6baaa8c0@kevin' \
--to=kevin@labsysgrp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).