From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: "J.J. Berkhout" <j.j.berkhout@staalenberk.nl>, linux-ide@vger.kernel.org
Subject: Re: Multiple errors with DVD drive
Date: Mon, 26 Sep 2022 07:57:19 +0900 [thread overview]
Message-ID: <efa832ac-2538-7593-f69d-238d18a196f0@opensource.wdc.com> (raw)
In-Reply-To: <223632d5-6d6f-f957-0a27-0b5b5d5ad91a@staalenberk.nl>
On 9/23/22 21:07, J.J. Berkhout wrote:
>
>
> On 23-09-2022 00:08, Damien Le Moal wrote:
>> On 9/21/22 21:38, J.J. Berkhout wrote:
>>> Hello,
>>>
>>>
>>>
>>> On 21-09-2022 13:58, Niklas Cassel wrote:
>>>> 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".
>>>>
>>>
>>> Yes, this worked and did the trick! Reading without any errors. I did
>>> not yet try to write, but will do so today.
>>> When booting with libata.force=nolpm the link_power_management_policy
>>> was still med_power_with_dipm and I got the dmesg:
>>>
>>> [ 0.291452] ata: failed to parse force parameter "nolpm" (unknown value)
>>
>> What kernel version are you running ? This should work with the latest
>> kernels. Your kernel likely pre-dates the addition of all the ata horkage
>> flag as boot parameter options, which I think was with 5.18 kernel.
>
> Yep, I run Ubuntu 5.15.0-48-generic kernel. I circumvented this by
> using sysfsutils with
> class/scsi_host/host0/link_power_management_policy = max_performance
> in the /etc/sysfs.conf file. As long as I don't mess around with my
> hardware, the host number should stay the same.
OK. Then "nolpm" not being a valid parameter is normal then. I wanted to
make sure there is no bug in the parameters handling :)
>
> Kind regards,
>
> Jaap Berkhout
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-09-25 22:57 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 [this message]
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=efa832ac-2538-7593-f69d-238d18a196f0@opensource.wdc.com \
--to=damien.lemoal@opensource.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