linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Lee Jones <lee@kernel.org>
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: Mon, 15 Apr 2024 13:37:54 -0700	[thread overview]
Message-ID: <de43c7e1-7e8c-bdbe-f59e-7632c21da24a@candelatech.com> (raw)
In-Reply-To: <20240411070718.GD6194@google.com>

On 4/11/24 00:07, Lee Jones wrote:
> 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/
> 
Hello Lee,

I cannot see how that patch above would fix my issues since I am not using that driver,
but possibly some similar change needs to be made to iwlwifi.

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?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



  reply	other threads:[~2024-04-15 20:37 UTC|newest]

Thread overview: 19+ 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 [this message]
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-04-16 12:19         ` Lee Jones

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=de43c7e1-7e8c-bdbe-f59e-7632c21da24a@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=lee@kernel.org \
    --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).