archive mirror
 help / color / mirror / Atom feed
From: Matthias Andree <>
To: Linux-Kernel mailing list <>
Subject: 2.6.0-test2: IDE TCQ locks up on Promise chip.
Date: Mon, 28 Jul 2003 09:06:20 +0200	[thread overview]
Message-ID: <> (raw)


I have a board with VIA KT133 and Promise 20265(R) jumpered for UATA/100
(rather than ATA/RAID), an IBM DTLA-307045 drive is attached to the
Promise controller (/dev/hde). On boot-up, the kernel tries to enable
tagged command queueing for that drive, but the completion interrupt
never occurs, so the kernel resets the ATA channel. fdisk -l /dev/hde hangs.

I haven't yet tried the drive with the VIA chip, so I cannot say whether
-test2 TCQ is hosed altogether or just on the Promise chip.

Note: FreeBSD-4 (FreeBSD-5 doesn't support ATA TCQ at the moment) has
blacklisted this Promise chip for ATA TCQ:

Check the function ad_tagsupported(), it blacklists my chip (the third /case/ applies):

    switch (adp->device->channel->chiptype) {
    case 0x4d33105a: /* Promises before TX2 doesn't work with tagged queuing */
    case 0x4d38105a:
    case 0x0d30105a:
    case 0x4d30105a:
        return 0;

lspci excerpts:

00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 10)
00:10.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV4 [Riva TnT] (rev 04)

00:00.0 Class 0600: 1106:0305 (rev 02)
00:01.0 Class 0604: 1106:8305
00:07.0 Class 0601: 1106:0686 (rev 22)
00:07.1 Class 0101: 1106:0571 (rev 10)
00:10.0 Class 0180: 105a:0d30 (rev 02)
01:00.0 Class 0300: 10de:0020 (rev 04)

Matthias Andree

                 reply	other threads:[~2003-07-28  6:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).