linux-kernel - Re: [REGRESSION][BISECTED] BU40N Blu-Ray drive broken since 7627a0edef54

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] [day] [month] [year] [list]

Message-ID: <f7583d39-890f-4a7f-a5fb-63379e0c9304@heusel.eu>
Date: Tue, 14 Jan 2025 18:51:19 +0100
From: Christian Heusel <christian@...sel.eu>
To: Niklas Cassel <cassel@...nel.org>
Cc: Mario Limonciello <mario.limonciello@....com>, 
	Damien Le Moal <dlemoal@...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 25/01/14 05:40PM, Christian Heusel wrote:
> On 25/01/14 05:05PM, Niklas Cassel wrote:
> > Hello Christian,
> 
> Hello Niklas,

Hello Niklas,

> 
> > Looking at the Arch Linux thread, it seems that the person reporting the
> > problem says that even on a working kernel, you only see the device the
> > user presses the open button on the Blu-Ray player.
> > 
> > This suggests to me that it sends a hotplug/PhyRdy event when the user
> > presses the open button.
> > 
> > In Linux, if we don't detect anything connected to the port during initial
> > boot, and if the port is not marked (by firmware) as either Hotplug Capable,
> > or External, then we mask the PhyRdy interrupt.
> > 
> > We could reconsider this, and leave the PhyRdy interrupt enabled even for a
> > port that is not Hotplug Capable or External, if there is no devices detected
> > on the port.
> > 
> > 
> > However, a device should really show up after a COMRESET... A device that
> > does not do so seems to be non-spec compliant.
> > It would be nice if we could understand why this device does not show up
> > after a COMRESET. (If it did, we most likely would not need the workaround
> > suggested above.)
> > 
> > Could you please run with this debug prints, which might tell us what is
> > going on:
> 
> Thanks for investigating this further, I was typing my previous mail and
> sent it just after yours because I didn't see it x)
> 
> > diff --git a/drivers/ata/libahci.c b/drivers/ata/libahci.c
> > <snip-patch>
> 
> Building a kernel with the patch applied just now! I will get back to
> you once I have heard back from the user.

I have attached the dmesg from the boot with the debug patches.

> On a sidenote it seems like your mail client or something converts the
> tabs to spaces on these inline patches, which makes them quite hard to
> apply for me (I had to manually apply and format-patch).
> Could add them as attachment in the future or reply via git send-mail?
> 
> > Kind regards,
> > Niklas
> 
> Cheers,
> Chris

Cheers,
Chris

View attachment "linux-mainline-6.13-rc7-1.2-dmesg.log" of type "text/plain" (89720 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)