Received-SPF: pass (google.com: domain of linux-kernel+bounces-136513-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <157c703381624d331c7de4aeb2b2802789239456.camel@sipsolutions.net>
Subject: Re: 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related)
From: Johannes Berg <johannes@sipsolutions.net>
To: Linux regressions mailing list <regressions@lists.linux.dev>, Ben Greear
	 <greearb@candelatech.com>, LKML <linux-kernel@vger.kernel.org>, 
	linux-leds@vger.kernel.org
Date: Tue, 09 Apr 2024 10:59:42 +0200
In-Reply-To: <93494f0b-ad05-4566-b454-fa36a7dac248@leemhuis.info>
References: <30f757e3-73c5-5473-c1f8-328bab98fd7d@candelatech.com>
	 <30819e01-43ce-638f-0cc6-067d6a8d03c7@candelatech.com>
	 <89a9eec3-337f-3c9f-6bbe-00a26a15287c@candelatech.com>
	 <05545ecdd2b05223b9204131b0ce9ba33460f44c.camel@sipsolutions.net>
	 <93494f0b-ad05-4566-b454-fa36a7dac248@leemhuis.info>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

On Tue, 2024-04-09 at 10:47 +0200, Linux regression tracking (Thorsten
Leemhuis) wrote:
> On 08.04.24 18:35, Johannes Berg wrote:
> > On Wed, 2024-04-03 at 12:35 -0700, Ben Greear wrote:
> > > >=20
> > > > So, deadlock I guess....
> > > >=20
> > > >  =C2=A0INFO: task kworker/5:13:648 blocked for more than 180 second=
s.
> > > >  =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Not tainted 6.9.0-rc2+ #23
> > > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this me=
ssage.
> > > > task:kworker/5:13=C2=A0=C2=A0=C2=A0 state:D stack:0=C2=A0=C2=A0=C2=
=A0=C2=A0 pid:648=C2=A0=C2=A0 tgid:648=C2=A0=C2=A0 ppid:2=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 flags:0x00004000
> > > > Workqueue: events deferred_probe_timeout_work_func
> > > > Call Trace:
> > > >  =C2=A0<TASK>
> > > >  =C2=A0__schedule+0x43d/0xe20
> > > >  =C2=A0schedule+0x31/0x130
> > > >  =C2=A0schedule_timeout+0x1b9/0x1d0
> > > >  =C2=A0? mark_held_locks+0x49/0x70
> > > >  =C2=A0? lockdep_hardirqs_on_prepare+0xd6/0x170
> > > >  =C2=A0__wait_for_common+0xb9/0x1d0
> > > >  =C2=A0? usleep_range_state+0xb0/0xb0
> > > >  =C2=A0? __flush_work+0x1ff/0x460
> > > >  =C2=A0__flush_work+0x287/0x460
> > > >  =C2=A0? flush_workqueue_prep_pwqs+0x120/0x120
> > > >  =C2=A0deferred_probe_timeout_work_func+0x2b/0xa0
> >=20
> > This seems ... complex.
> >=20
> > Does changing iwlwifi's request_module() to request_module_nowait() in
> > iwl_req_fw_callback() (only) fix it? I think we can do that, we don't
> > really care at that point, and the issue here seems to be waiting for i=
t
> > while also other modules are loading and due to the hashing in
> > idempotent() (kernel/module/main.c) it can't make progress.
>=20
> Not my area of expertise, so listening to me my send you off-track.
>=20
> Might this be related to the issue discussed here:
> https://lore.kernel.org/all/ZhRD3cOtz5i-61PB@mail-itl/
>=20
> See also:
> https://lore.kernel.org/all/2695e9db-a5a0-4564-9812-a50b91fb1b46@gmail.co=
m/

Don't think so, that was related to devm and module unload, neither
seems to be the case here.

johannes