From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: "J.J. Berkhout" <j.j.berkhout@staalenberk.nl>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Multiple errors with DVD drive
Date: Tue, 20 Sep 2022 13:35:31 +0000 [thread overview]
Message-ID: <YynBohKGFDRIPdRg@x1-carbon> (raw)
In-Reply-To: <c7e0c932-2e20-18b5-fe9f-36572807f59b@staalenberk.nl>
On Thu, May 26, 2022 at 02:38:53PM +0200, J.J. Berkhout wrote:
> Firstly, if this is not the right place for this message, I apologize.
> In this case, disregard.
>
> I have a problem which I suspect is a bug in libata, but of course I
> could be wrong.
>
> The problem is:
> After going from Linux Mint 19.3 Cinnamon kernel 5.4.0-97 to Linux Mint
> 20.3 Cinnamon kernel 5.4.0-107 I discovered that I could not (reliably)
> access my optical drive anymore.
> It produces errors like:
> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe frozen
> ata1: SError: { PHYRdyChg CommWake 10B8B DevExch }
> ata1.00: cmd a0/00:00:00:00:fc/00:00:00:00:00/a0 tag 0 pio 131072 in
> Read(10) 28 00 00 00 05 61 00 00 40 00res
> 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
> blk_update_request: I/O error, dev sr0, sector 5508 op 0x0:(READ) flags
> 0x80700 phys_seg 19 prio class 0
> ata1.00: failed to set xfermode (err_mask=0x1)
>
FWIW, there seems to be a bunch of quirks for Pioneer optical drives
related to set xfermode:
/*
* Devices which choke on SETXFER. Applies only if both the
* device and controller are SATA.
*/
{ "PIONEER DVD-RW DVRTD08", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVRTD08A", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVR-215", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVR-212D", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVR-216D", NULL, ATA_HORKAGE_NOSETXFER },
Perhaps you could try the following patch:
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 826d41f341e4..263f6a59b2cf 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -3987,6 +3987,7 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
{ "PIONEER DVD-RW DVR-215", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVR-212D", NULL, ATA_HORKAGE_NOSETXFER },
{ "PIONEER DVD-RW DVR-216D", NULL, ATA_HORKAGE_NOSETXFER },
+ { "PIONEER BD-RW BDR-207M", NULL, ATA_HORKAGE_NOSETXFER },
/* Crucial BX100 SSD 500GB has broken LPM support */
{ "CT500BX100SSD1", NULL, ATA_HORKAGE_NOLPM },
Kind regards,
Niklas
prev parent reply other threads:[~2022-09-20 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 12:38 Multiple errors with DVD drive J.J. Berkhout
2022-05-26 23:36 ` Damien Le Moal
2022-05-27 8:50 ` J.J. Berkhout
2022-05-27 10:32 ` J.J. Berkhout
2022-08-05 9:17 ` J.J. Berkhout
2022-09-20 10:05 ` J.J. Berkhout
2022-09-20 13:06 ` Niklas Cassel
[not found] ` <9756ac37-6790-7b83-5840-abe04f8ab838@staalenberk.nl>
2022-09-20 21:08 ` Niklas Cassel
2022-09-21 10:28 ` J.J. Berkhout
2022-09-21 11:58 ` Niklas Cassel
2022-09-21 12:38 ` J.J. Berkhout
2022-09-21 14:54 ` J.J. Berkhout
2022-09-21 18:32 ` Niklas Cassel
2022-09-26 12:59 ` J.J. Berkhout
2022-09-26 14:39 ` Niklas Cassel
2022-09-26 14:50 ` J.J. Berkhout
2022-09-22 22:08 ` Damien Le Moal
2022-09-23 12:07 ` J.J. Berkhout
2022-09-25 22:57 ` Damien Le Moal
2022-09-20 13:35 ` 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=YynBohKGFDRIPdRg@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=j.j.berkhout@staalenberk.nl \
--cc=linux-ide@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