From: Damien Le Moal <dlemoal@kernel.org>
To: Christian Heusel <christian@heusel.eu>,
Mario Limonciello <mario.limonciello@amd.com>,
Niklas Cassel <cassel@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION][BISECTED] BU40N Blu-Ray drive broken since 7627a0edef54
Date: Fri, 10 Jan 2025 18:24:42 +0900 [thread overview]
Message-ID: <d1b79f57-9e77-4b2a-9dfb-f86cdcffcb0d@kernel.org> (raw)
In-Reply-To: <e2be6f70-dff6-4b79-bd49-70ec7e27fc1c@heusel.eu>
On 2025/01/10 18:04, Christian Heusel wrote:
> Hello everyone,
>
> we have recently received a report by a user in the Arch Linux Forums
> user that their Blue Ray player, a HL-DT-ST BD-RE BU40N stopped working
> somewhere since kernel version v6.8.0. We have then bisected the issue
> together with them within the mainline kernel sources to the following
> commit that changes the default power policy:
>
> 7627a0edef54 ("ata: ahci: Drop low power policy board type")
>
> The user reports that adding "ahci.mobile_lpm_policy=1" as a kernel
> parameter fixes the issue for them.
>
> Additionally fellow forum user @loqs came up with a quirk patch, that
> sadly was reported to not work:
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index c085dd8..ef01ccd 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4118,6 +4118,9 @@ static const struct ata_dev_quirks_entry __ata_dev_quirks[] = {
> { "SAMSUNG MZ7TD256HAFV-000L9", NULL, ATA_QUIRK_NOLPM },
> { "SAMSUNG MZ7TE512HMHP-000L1", "EXT06L0Q", ATA_QUIRK_NOLPM },
>
> + /* Hitachi-LG Data Storage models with LPM issues */
> + { "HL-DT-ST BD-RE BU40N", NULL, ATA_QUIRK_NOLPM },
Looks like "BU40N" may be the FW rev ? If we can get a dmesg ourput of the
failing case, we should be able to sort out this. Likely it is a bad string
reference here.
> +
> /* devices that don't properly handle queued TRIM commands */
> { "Micron_M500IT_*", "MU01", ATA_QUIRK_NO_NCQ_TRIM |
> ATA_QUIRK_ZERO_AFTER_TRIM },
>
> So if anyone has feedback on why the patch does not work or any
> alternative ideas for a solution that would be highly appreciated!
>
> Cheers,
> gromit
>
> [0]: https://bbs.archlinux.org/viewtopic.php?id=302334
>
> ---
>
> #regzbot introduced: 7627a0edef54
> #regzbot link: https://bbs.archlinux.org/viewtopic.php?id=302334
> #regzbot title: ata: ahci: Blue Ray player broken since power policy change
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-01-10 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 9:04 [REGRESSION][BISECTED] BU40N Blu-Ray drive broken since 7627a0edef54 Christian Heusel
2025-01-10 9:24 ` Damien Le Moal [this message]
2025-01-10 9:42 ` Christian Heusel
2025-01-10 9:50 ` Damien Le Moal
2025-01-10 11:24 ` Niklas Cassel
2025-01-10 16:21 ` Christian Heusel
2025-01-11 16:41 ` Christian Heusel
2025-01-13 16:26 ` Niklas Cassel
2025-01-14 16:05 ` Niklas Cassel
2025-01-14 16:40 ` Christian Heusel
2025-01-14 17:51 ` Christian Heusel
2025-01-15 18:35 ` Niklas Cassel
2025-01-14 16:06 ` Christian Heusel
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=d1b79f57-9e77-4b2a-9dfb-f86cdcffcb0d@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=christian@heusel.eu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=regressions@lists.linux.dev \
/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