public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Christian Heusel <christian@heusel.eu>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Niklas Cassel <cassel@kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	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:50:10 +0900	[thread overview]
Message-ID: <60469206-2168-4f53-8882-eddcddc14e80@kernel.org> (raw)
In-Reply-To: <928aa39d-9c8d-474a-b077-d08e984ad5e9@heusel.eu>

On 2025/01/10 18:42, Christian Heusel wrote:
> On 25/01/10 06:24PM, Damien Le Moal wrote:
>> 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.
> 
> I have attached the dmesg outputs, here is the relevant output:
> 
> [   81.230713] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   81.235708] ata4.00: ATAPI: HL-DT-ST BD-RE BU40N, 1.03, max UDMA/133
> [   81.240789] ata4.00: configured for UDMA/133
> [   81.248585] scsi 3:0:0:0: CD-ROM            HL-DT-ST BD-RE BU40N      1.03 PQ: 0 ANSI: 5
> [   81.302830] scsi 3:0:0:0: Attached scsi generic sg2 type 5
> [   81.382131] sr 3:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray

Is this with the latest kernel 6.13-rc6 ?

> 
> Aswell as the output for "hdparm -i /dev/sr0":
> 
> /dev/sr0:
> 
>  Model=HL-DT-ST BD-RE BU40N, FwRev=1.03, SerialNo=

Odd... The device model string is correct in the patch, so it should work.
May be something is not being done correctly for ATAPI. Let me check.

>  Config={ Fixed Removable DTR<=5Mbs DTR>10Mbs nonMagnetic }
>  RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
>  BuffType=unknown, BuffSize=unknown, MaxMultSect=0
>  CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4 
>  DMA modes:  mdma0 mdma1 mdma2 
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6 
>  AdvancedPM=no
>  Drive conforms to: unknown:  ATA/ATAPI-3,4,5,6,7
> 
>  * signifies the current active mode
> 
> Cheers,
> Chris


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-01-10  9:50 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
2025-01-10  9:42   ` Christian Heusel
2025-01-10  9:50     ` Damien Le Moal [this message]
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=60469206-2168-4f53-8882-eddcddc14e80@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