linux-kernel - Re: 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related)

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]

Date: Tue, 7 May 2024 09:23:15 +0100
From: Lee Jones <lee@...nel.org>
To: Ben Greear <greearb@...delatech.com>
Cc: "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info>,
	LKML <linux-kernel@...r.kernel.org>, linux-leds@...r.kernel.org,
	Miri Korenblit <miriam.rachel.korenblit@...el.com>,
	Johannes Berg <johannes@...solutions.net>,
	Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related)

On Sat, 04 May 2024, Ben Greear wrote:

> On 5/2/24 00:19, Lee Jones wrote:
> > On Tue, 23 Apr 2024, Linux regression tracking (Thorsten Leemhuis)
> > wrote:
> > 
> > > On 23.04.24 11:06, Johannes Berg wrote:
> > > > On Tue, 2024-04-23 at 11:00 +0200, Linux regression tracking
> > > > (Thorsten Leemhuis) wrote:
> > > > > On 16.04.24 08:17, Johannes Berg wrote:
> > > > > > On Mon, 2024-04-15 at 13:37 -0700, Ben Greear wrote:
> > > > > > > 
> > > > > > > Johannes, you had another suggestion: changing iwlwifi's
> > > > > > > request_module() to request_module_nowait() in
> > > > > > > iwl_req_fw_callback()
> > > > > > > 
> > > > > > > Is that still best thing to try in your opinion?
> > > > > > 
> > > > > > I guess so, I don't have any better ideas so far anyway ...
> > > > > 
> > > > > [adding the iwlwifi maintainer; thread starts here:
> > > > > https://lore.kernel.org/lkml/30f757e3-73c5-5473-c1f8-328bab98fd7d@candelatech.com/
> > > > > 
> > > > > ]
> > > > > 
> > > > > Johannes, Miri, what's the status wrt to this regression? From
> > > > > here things look somewhat stalled -- but maybe there was
> > > > > progress and I just missed it.
> > > > 
> > > > What do you want? It got bisected to an LED merge, but you ping
> > > > _us_? Way to go ...
> > > 
> > > Sorry, to me it sounded a bit like you had an idea for a fix and
> > > were going to give it a try -- similar to how the maintainers for
> > > a r8169 driver and the igc driver provided fixes for bugs recent
> > > LED changes exposed.
> > > 
> > > But sure, you are right, in the end some LED change seems to have
> > > cause this, so the duty to fix it lies in that field. Therefore:
> > > 
> > > Lee, what's the status here to get this fixed before the final?
> > 
> > No idea.  Did you send a fix?
> 
> I sent what is probably just a work-around.  I also spent time
> bisecting and testing. The problem appears to have come in with the
> LED related merge.  I think it is fair to ask the LED folks to at
> least take a look at the lockdep debugging I posted.

I can't speak for Pavel, but I personally have no way of debugging or
reproducing this.  The only usefulness I can provide is to review and
apply fixes as and when they appear.

> It is not fair to expect anyone that manages to find or track a bug to
> also fix it.

No such expectation has been felt or communicated.

-- 
Lee Jones [李琼斯]