lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60469206-2168-4f53-8882-eddcddc14e80@kernel.org>
Date: Fri, 10 Jan 2025 18:50:10 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Christian Heusel <christian@...sel.eu>
Cc: Mario Limonciello <mario.limonciello@....com>,
 Niklas Cassel <cassel@...nel.org>,
 Mika Westerberg <mika.westerberg@...ux.intel.com>,
 linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
 regressions@...ts.linux.dev
Subject: Re: [REGRESSION][BISECTED] BU40N Blu-Ray drive broken since
 7627a0edef54

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ