From: Niklas Cassel <cassel@kernel.org>
To: Philip Pemberton <lists@philpem.me.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Zip 100 ATAPI not working, "qc timeout" and "failed to clear UNIT ATTENTION"
Date: Wed, 8 Jan 2025 15:05:39 +0100 [thread overview]
Message-ID: <Z36GMwr49ihd2nAG@ryzen> (raw)
In-Reply-To: <c6722ee8-5e21-4169-af59-cbbae9edc02f@philpem.me.uk>
On Wed, Jan 08, 2025 at 12:52:50PM +0000, Philip Pemberton wrote:
> I'm trying to connect an old Iomega Zip 100 ATAPI to a B550-chipset Ryzen
> system, to exchange files with an even older system. The Gigabyte B550 AORUS
> ELITE AX V2 rev1.3 motherboard doesn't have any PATA ports, so I'm using a
> SATA to PATA adapter.
>
> Sadly it will not work in the B550 system (Kernel 6.8.0-51-generic x86_64,
> Linux Mint 21.3 based on Ubuntu 22.04). When I have the Zip drive connected,
> I get the following in dmesg and the sd device never appears:
>
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: ATAPI: IOMEGA ZIP 100 ATAPI, 12.A, max PIO3, CDB intr,
> DMADIR
> ata3.00: applying bridge limits
> ata3.00: configured for PIO0
> ata3.00: qc timeout after 5000 msecs (cmd 0xa0)
> ata3.00: failed to clear UNIT ATTENTION (err_mask=0x5)
Since we see that the drive name is printed, the ATAPI IDENTIFY command
succeded (ATA_CMD_ID_ATAPI (0xA1)).
The command that timed out is ATA_CMD_PACKET 0xA0, so a regular ATAPI command.
The UNIT ATTENTION print is just from atapi_eh_clear_ua(), which seems to be
called by ata_eh_recover() unconditionally for ATAPI devices, because they
always need to clear UNIT ATTENTION after a reset:
https://github.com/torvalds/linux/blob/v6.8/drivers/ata/libata-eh.c#L3232-L3234
But the reset is of course only triggered because a command has timed out.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-01-08 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 12:52 Zip 100 ATAPI not working, "qc timeout" and "failed to clear UNIT ATTENTION" Philip Pemberton
2025-01-08 13:42 ` Niklas Cassel
2025-01-08 13:45 ` Niklas Cassel
2025-01-09 11:36 ` Philip Pemberton
2025-01-08 14:05 ` Niklas Cassel [this message]
2025-01-09 7:17 ` Hannes Reinecke
2025-01-09 11:33 ` Philip Pemberton
2025-01-09 13:22 ` Niklas Cassel
2025-01-09 15:06 ` Philip Pemberton
2025-01-09 11:35 ` Philip Pemberton
[not found] ` <e1985151-c206-4be1-91c1-92eac16f6236@philpem.me.uk>
2025-01-09 12:22 ` Niklas Cassel
2025-01-09 15:31 ` Philip Pemberton
2025-01-17 13:37 ` Niklas Cassel
2025-01-23 13:19 ` Philip Pemberton
2025-01-23 16:19 ` Philip Pemberton
2025-01-24 10:03 ` Niklas Cassel
2025-02-18 3:05 ` Philip Pemberton
2025-02-19 15:48 ` Niklas Cassel
2025-02-19 16:02 ` Niklas Cassel
2025-02-19 20:04 ` Philip Pemberton
2025-02-21 1:57 ` Niklas Cassel
2025-02-21 17:08 ` Philip Pemberton
2025-02-21 17:24 ` Niklas Cassel
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=Z36GMwr49ihd2nAG@ryzen \
--to=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=lists@philpem.me.uk \
/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.