Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake 10B8B DevExch }

[J.J. Berkhout]

Going from kernel version 5.4.0-99 to 5.4.0-100 my optical drive (Pioneer BD-RW BDR-207M) became unusable. I include a selection of the errors, the dmesg errors immediately after boot without trying to use the drive yet, the system specs from system report, and the output of the inxi -Fdxxx commandin the file attachment.txt.
Up to and including kernel 5.4.0-99 everything worked OK. Kernel 5.13.0-30 also works, from kernel 5.13.0-35 the same problem occurs. Might it be a problem with atalib?
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jaap 1928 F.... pulseaudio
 /dev/snd/controlC1: jaap 1928 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-02-01 (64 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic root=UUID=9d60bcb5-650d-484d-ae74-728526cd6db1 ro ipv6.disable=1 elevator=deadline quiet splash nomodeset
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-100-generic N/A
 linux-backports-modules-5.4.0-100-generic N/A
 linux-firmware 1.187.29
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: yes
Tags: una
Uname: Linux 5.4.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo systemd-timesync vboxusers
_MarkForUpload: True
dmi.bios.date: 12/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X570 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd12/01/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jaap 1928 F.... pulseaudio
 /dev/snd/controlC1: jaap 1928 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-02-01 (64 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic root=UUID=9d60bcb5-650d-484d-ae74-728526cd6db1 ro ipv6.disable=1 elevator=deadline quiet splash nomodeset
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-100-generic N/A
 linux-backports-modules-5.4.0-100-generic N/A
 linux-firmware 1.187.29
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: yes
Tags: una
Uname: Linux 5.4.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo systemd-timesync vboxusers
_MarkForUpload: True
dmi.bios.date: 12/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X570 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd12/01/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1968155

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[J.J. Berkhout (j-j-berkhout)]

apport information

[Seth Goldberg (sethmeisterg)]

I'm seeing the exact same problem -- I've filed bug #1970136, which can be duped to this one.

[J.J. Berkhout (j-j-berkhout)]

The problem was (partly) solved.
After asking for help in the linux kernel development mailing list Niklas Cassel (one of the developers) wrote:

- The commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile") added the - PCI vendor and device id to the list of supported AHCI controllers using the low power board
- version:
 { PCI_VDEVICE(AMD, 0x7901), board_ahci_low_power }, /* AMD Green Sardine */

- Before the commit in question, your AHCI controller relied on this catch-all entry:
 /* Generic, PCI class code for AHCI */
 { PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
   PCI_CLASS_STORAGE_SATA_AHCI, 0xffffff, board_ahci },
- which does not enable/allow any low power mode at all.

- Now, I do think that low power modes *should* work with this AHCI controller. Most likely, it is - simply the optical drive that does not work well when the HBA initiates a low power mode on the
- link.
.
.
.
- A way do disable lpm is to do:

$ ls -al /sys/class/scsi_host/host*

- Find your device in the list. My device is:
/sys/class/scsi_host/host13/

- Print the current lpm policy for your device:
$ cat /sys/class/scsi_host/host13/link_power_management_policy
med_power_with_dipm

- Anything other than "max_performance" means that you have (a varying degree) of low power modes
- enabled.

$ sudo sh -c "echo max_performance > /sys/class/scsi_host/host13/link_power_management_policy"

$ cat /sys/class/scsi_host/host13/link_power_management_policy
max_performance

- Try reading from the optical drive after ensuring that the policy is "max_performance".

This solved the problem.
As the kernel parameter to disable lpm only works from kernel 5.18 onwards, I had to find another way to force this setting, so I did:
$ apt install sysfsutils
and added in /etc/sysfs.conf the line:

class/scsi_host/host0/link_power_management_policy = max_performance

As long as I don't mess around with my hardware, the host number should stay the same.
Of course, if anyone uses this method, he/she should find out his host number for the controller of the optical drive in question and substitute it in the hostnn part.

A definite solution will probably be a future patch in libata.

[Seth Goldberg (sethmeisterg)]

Perfect! Thanks so much for letting me know :).

  Thanks!
   --S

> On Sep 23, 2022, at 8:37 AM, J.J. Berkhout <email address hidden> wrote:
>
> The problem was (partly) solved.
> After asking for help in the linux kernel development mailing list Niklas Cassel (one of the developers) wrote:
>
> - The commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile") added the - PCI vendor and device id to the list of supported AHCI controllers using the low power board
> - version:
> { PCI_VDEVICE(AMD, 0x7901), board_ahci_low_power }, /* AMD Green Sardine */
>
> - Before the commit in question, your AHCI controller relied on this catch-all entry:
> /* Generic, PCI class code for AHCI */
> { PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
> PCI_CLASS_STORAGE_SATA_AHCI, 0xffffff, board_ahci },
> - which does not enable/allow any low power mode at all.
>
> - Now, I do think that low power modes *should* work with this AHCI controller. Most likely, it is - simply the optical drive that does not work well when the HBA initiates a low power mode on the
> - link.
> .
> .
> .
> - A way do disable lpm is to do:
>
> $ ls -al /sys/class/scsi_host/host*
>
> - Find your device in the list. My device is:
> /sys/class/scsi_host/host13/
>
> - Print the current lpm policy for your device:
> $ cat /sys/class/scsi_host/host13/link_power_management_policy
> med_power_with_dipm
>
> - Anything other than "max_performance" means that you have (a varying degree) of low power modes
> - enabled.
>
> $ sudo sh -c "echo max_performance >
> /sys/class/scsi_host/host13/link_power_management_policy"
>
> $ cat /sys/class/scsi_host/host13/link_power_management_policy
> max_performance
>
> - Try reading from the optical drive after ensuring that the policy is
> "max_performance".
>
> This solved the problem.
> As the kernel parameter to disable lpm only works from kernel 5.18 onwards, I had to find another way to force this setting, so I did:
> $ apt install sysfsutils
> and added in /etc/sysfs.conf the line:
>
> class/scsi_host/host0/link_power_management_policy = max_performance
>
> As long as I don't mess around with my hardware, the host number should stay the same.
> Of course, if anyone uses this method, he/she should find out his host number for the controller of the optical drive in question and substitute it in the hostnn part.
>
> A definite solution will probably be a future patch in libata.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1968155
>
> Title:
> Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake
> 10B8B DevExch }
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Going from kernel version 5.4.0-99 to 5.4.0-100 my optical drive (Pioneer BD-RW BDR-207M) became unusable. I include a selection of the errors, the dmesg errors immediately after boot without trying to use the drive yet, the system specs from system report, and the output of the inxi -Fdxxx commandin the file attachment.txt.
> Up to and...

[Mario Limonciello (superm1)]

Here is the fix that has been queued up:

https://<email address hidden>/

[J.J. Berkhout (j-j-berkhout)]

Solved for my devices by backport of libata patch in kernel 5.15.0-57. Thanks everybody for all the help.