From: Lee Jones <lee@kernel.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>, LKML <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related)
Date: Tue, 7 May 2024 09:23:15 +0100 [thread overview]
Message-ID: <20240507082315.GS1227636@google.com> (raw)
In-Reply-To: <8054cc9c-fbfe-a08d-5968-57b90a25af65@candelatech.com>
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 [李琼斯]
next prev parent reply other threads:[~2024-05-07 8:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 16:37 6.9.0-rc2+ kernel hangs on boot Ben Greear
2024-04-02 17:38 ` Ben Greear
2024-04-03 19:35 ` 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related) Ben Greear
2024-04-08 16:35 ` Johannes Berg
2024-04-09 8:47 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-09 8:59 ` Johannes Berg
2024-04-11 7:07 ` Lee Jones
2024-04-15 20:37 ` Ben Greear
2024-04-16 6:17 ` Johannes Berg
2024-04-23 9:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-23 9:06 ` Johannes Berg
2024-04-23 9:29 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-24 17:26 ` Ben Greear
2024-04-24 17:31 ` Johannes Berg
2024-05-02 7:19 ` Lee Jones
2024-05-02 8:30 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-05 5:48 ` Ben Greear
2024-05-05 10:55 ` Tetsuo Handa
2024-05-07 4:21 ` Ben Greear
2024-05-07 8:23 ` Lee Jones [this message]
2024-04-16 12:19 ` Lee Jones
2024-05-06 20:00 ` Heiner Kallweit
2024-05-07 4:20 ` Ben Greear
2024-05-07 6:27 ` Heiner Kallweit
2024-05-07 10:58 ` Heiner Kallweit
2024-05-08 5:51 ` Heiner Kallweit
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=20240507082315.GS1227636@google.com \
--to=lee@kernel.org \
--cc=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=regressions@leemhuis.info \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.