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: Fri, 21 Feb 2025 18:24:15 +0100 [thread overview]
Message-ID: <Z7i2v8Nyetfx29zx@ryzen> (raw)
In-Reply-To: <62cd0608-8089-4c1e-b44d-699f1409dccb@philpem.me.uk>
On Fri, Feb 21, 2025 at 05:08:21PM +0000, Philip Pemberton wrote:
> On 21/02/2025 01:57, Niklas Cassel wrote:
> > Please try this patch:
> > https://lore.kernel.org/linux-ide/20250221015422.20687-2-cassel@kernel.org/T/#u
> >
> > and see if it fixes your problem.
> >
> > Please also make sure to check that you can still write and read back what
> > you wrote to the device (with the read data matching the written data).
>
> I can confirm the patch works!
Thanks for testing, and thanks for actually taking the time to debug this!
> Dump the original contents of the disk:
> # ddrescue /dev/sdb zip_orig
> GNU ddrescue 1.27
> Press Ctrl-C to interrupt
> ipos: 100597 kB, non-trimmed: 0 B, current rate: 589 kB/s
> opos: 100597 kB, non-scraped: 0 B, average rate: 792 kB/s
> non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
> rescued: 100663 kB, bad areas: 0, run time: 2m 6s
> pct rescued: 100.00%, read errors: 0, remaining time: n/a
> time since last successful read: n/a
> Copying non-tried blocks... Pass 1 (forwards)
> Finished
>
> Create 100MB of randomness, write it to the disk:
> # dd if=/dev/urandom of=ziptest bs=512 count=196608
> 196608+0 records in
> 196608+0 records out
> 100663296 bytes (101 MB, 96 MiB) copied, 2.74086 s, 36.7 MB/s
> # dd if=ziptest of=/dev/sdb bs=512
> 196608+0 records in
> 196608+0 records out
> 100663296 bytes (101 MB, 96 MiB) copied, 226.022 s, 445 kB/s
>
> Read it back:
> # ddrescue /dev/sdb ziptest_read
> GNU ddrescue 1.27
> Press Ctrl-C to interrupt
> ipos: 100597 kB, non-trimmed: 0 B, current rate: 196 kB/s
> opos: 100597 kB, non-scraped: 0 B, average rate: 1059 kB/s
> non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
> rescued: 100663 kB, bad areas: 0, run time: 1m 34s
> pct rescued: 100.00%, read errors: 0, remaining time: n/a
> time since last successful read: n/a
> Copying non-tried blocks... Pass 1 (forwards)
> Finished
>
> Compare:
> # md5sum ziptest*
> f132f7ad38beef40d45ce9f96a6e9f92 ziptest
> f132f7ad38beef40d45ce9f96a6e9f92 ziptest_read
Certainly good enough for me, I will add your Tested-by tag!
Considering that this has been broken for 19 years, a few more weeks
will be quick in comparison. I will queue it for 6.15 just to get some
extra testing.
Kind regards,
Niklas
prev parent reply other threads:[~2025-02-21 17:24 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
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 [this message]
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=Z7i2v8Nyetfx29zx@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 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).