public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 21 Sep 2022 11:58:34 +0000	[thread overview]
Message-ID: <Yyr8aV5CEOuChpre@x1-carbon> (raw)
In-Reply-To: <f3111c18-704b-1845-1d39-e220642eec34@staalenberk.nl>

On Wed, Sep 21, 2022 at 12:28:34PM +0200, J.J. Berkhout wrote:
> On 20-09-2022 23:08, Niklas Cassel wrote:
> >
> > You should be able to test this theory by adding libata.force=nolpm
> > on the kernel command line on a recent (non-working) kernel, low power
> > modes should then be disabled, and the drive should work again.
> > (You can press 'e' in grub to temporarily add something to the kernel
> > command line, and then ctrl+x to boot.)
> >
> > But the proper fix is probably to add a quirk for you device, either:
> > +       { "PIONEER BD-RW   BDR-207M",   NULL,   ATA_HORKAGE_NOSETXFER },
> > or
> > +       { "PIONEER BD-RW   BDR-207M",   NULL,   ATA_HORKAGE_NOLPM },
>
> I just tested the libata.force=nolpm kernel parameter on my system
> running kernel 5.15.0-48-generic x86_64 (linux mint 20.3, base Ubuntu
> 20.04 focal).  I am sorry to say, this parameter did not solve the problem.

Another 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".

However, disabling all low power modes on the kernel command line
should basically be the same.


Perhaps you could verify that your policy is "max_performance" out of the box
when booting the non-working kernel with libata.force=nolpm.

Booting the non-working without libata.force=nolpm should result in
"med_power_with_dipm"
(as that is the ubuntu default).

Booting the old kernel should result in "max_performance", since lpm
wasn't available/allowed for your AHCI controller in your old kernel.


>
> As for your patch concerning NOSETXFER, I will try to test this shortly,
> but it could take one or two days (medical stuff for me and my wife).

There is absolutely no need to rush.


Kind regards,
Niklas

  reply	other threads:[~2022-09-21 11:58 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 [this message]
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

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=Yyr8aV5CEOuChpre@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