From: Lee Jones <lee@kernel.org>
To: Ben Greear <greearb@candelatech.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: 6.9.0-rc2+ kernel hangs on boot (bisected, maybe LED related)
Date: Thu, 11 Apr 2024 08:07:18 +0100 [thread overview]
Message-ID: <20240411070718.GD6194@google.com> (raw)
In-Reply-To: <89a9eec3-337f-3c9f-6bbe-00a26a15287c@candelatech.com>
On Wed, 03 Apr 2024, Ben Greear wrote:
> On 4/2/24 10:38, Ben Greear wrote:
> > On 4/2/24 09:37, Ben Greear wrote:
> > > Hello,
> > >
> > > Sometime between rc1 and today's rc2, my system quit booting.
> > > I'm not seeing any splats, it just stops. Evidently before
> > > sysrq is enabled.
> > >
> > > [ OK ] Started Flush Journal to Persistent Storage.
> > > [ OK ] Started udev Coldplug all Devices.
> > > Starting udev Wait for Complete Device Initialization...
> > > [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
> > > [ OK ] Created slice system-lvm2\x2dpvscan.slice.
> > > Starting LVM2 PV scan on device 8:19...
> > > Starting LVM2 PV scan on device 8:3...
> > > [ OK ] Started Device-mapper event daemon.
> > > iwlwifi 0000:04:00.0: WRT: Invalid buffer destination: 0
> > > sysrq: This sysrq operation is disabled.
> > >
> > > I can start a bisect, but in case anyone knows the answer already, please let me know.
> > >
> > > Thanks,
> > > Ben
> > >
> >
> > So, deadlock I guess....
Does this help you in any way?
https://lore.kernel.org/all/bbcdbc1b-44bc-4cf8-86ef-6e6af2b009c3@gmail.com/
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-04-11 7:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <30f757e3-73c5-5473-c1f8-328bab98fd7d@candelatech.com>
[not found] ` <30819e01-43ce-638f-0cc6-067d6a8d03c7@candelatech.com>
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 [this message]
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
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=20240411070718.GD6194@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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).