Linux-libre > 5.15.12 leads to unbootable system

  • Done
  • quality assurance status badge
Details
3 participants
  • Squirrel
  • Leo Famulari
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
important
Merged with
L
L
Ludovic Courtès wrote on 15 Feb 2022 15:56
(address . bug-guix@gnu.org)(name . Leo Famulari)(address . leo@famulari.name)
8735kk18mc.fsf@inria.fr
2022 has left me without a working Linux-libre kernel.

Breakage occurred sometime between:

• 92faad0adb93b8349bfd7c67911d3d95f0505eb2
(Jan. 3rd; Linux-libre 5.15.12)

• 43dd34c7777a212c99a97da7a2c237158faa9a1b
(Jan. 31st; Linux-libre 5.15.17)

The symptoms are that, on my x86_64 laptop, the kernel boots, I can
enter the passphrase for my root file system (‘cryptsetup’ is invoked
from the initrd), things get printed, the console font changes, and then
things get stuck here. The last messages are from my sound card driver
(Intel HDA). It hangs before syslogd is started, and I think before
shepherd is even started (I can’t be 100% sure because I cannot scroll
back at that point, but I did add print statements in ‘shepherd.conf’
and didn’t see them.)

The same config works in ‘guix system vm’.

I can work around the problem by reconfiguring from current ‘master’ and
doing this:

Toggle snippet (14 lines)
(define inferior-for-kernel
(inferior-for-channels
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(commit
"92faad0adb93b8349bfd7c67911d3d95f0505eb2")))))

(operating-system
;; …
(kernel
(first (lookup-inferior-packages inferior-for-kernel "linux-libre"))))

This suggests a kernel issue.

Ideas and suggestions on how to debug this most welcome!

Ludo’.
L
L
Ludovic Courtès wrote on 15 Feb 2022 15:58
control message for bug #54010
(address . control@debbugs.gnu.org)
87tud0yy56.fsf@gnu.org
severity 54010 important
quit
L
L
Leo Famulari wrote on 15 Feb 2022 19:17
Re: Linux-libre > 5.15.12 leads to unbootable system
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . bug-guix@gnu.org)
YgvuV25kv0sO/C8n@jasmine.lan
On Tue, Feb 15, 2022 at 03:56:27PM +0100, Ludovic Courtès wrote:
Toggle quote (10 lines)
> 2022 has left me without a working Linux-libre kernel.
>
> Breakage occurred sometime between:
>
> • 92faad0adb93b8349bfd7c67911d3d95f0505eb2
> (Jan. 3rd; Linux-libre 5.15.12)
>
> • 43dd34c7777a212c99a97da7a2c237158faa9a1b
> (Jan. 31st; Linux-libre 5.15.17)

Isn't this #53712?

I recommend trying the workaround described there, which is to blacklist
the iwlwifi kernel module, if you are not using it but have iwlwifi
hardware:


That worked for me and is consistent with the upstream discussion of
this bug:

S
S
Squirrel wrote on 15 Feb 2022 17:39
bug#54010: Linux-libre > 5.15.12 leads to unbootable system
(address . bug-guix@gnu.org)
tencent_8C07C8E5FDEE97EDAE35C1F19E44055F8505@qq.com
Have you tried blacklisting the the iwlwifi kernel module on boot by
adding (kernel-arguments '("modprobe.blacklist=iwlwifi")) to
operating-system declaration? The problem may be a bug from upstream
linux. Please see

For your reference, there is a similar thread (bug#53712: Guix System
hangs after boot with linux-libre 5.15.17) in bug-guix at

The patch for it has just been applied in the newest upstream kernel
L
L
Leo Famulari wrote on 15 Feb 2022 22:15
(name . Squirrel via Bug reports for GNU Guix)(address . bug-guix@gnu.org)(address . 54010@debbugs.gnu.org)
YgwYBzHS+CL5AbYE@jasmine.lan
On Wed, Feb 16, 2022 at 12:39:46AM +0800, Squirrel via Bug reports for GNU Guix wrote:
Toggle quote (3 lines)
> The patch for it has just been applied in the newest upstream kernel
> releases. (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.23)

Are you sure the bug is fixed in 5.15.23?

I don't see anything relevant in the changelog and I still have to apply
the workaround in order to boot 5.15.23 on affected hardware.
S
S
Squirrel wrote on 16 Feb 2022 02:40
bug#54010: Linux-libre > 5.15.12 leads to unbootable system
(address . bug-guix@gnu.org)
tencent_3161EFF81206EF3F5480559E8042DEA97E09@qq.com
On Tue, 15 Feb 2022 16:15:51 -0500, Leo Famulari <leo@famulari.name> wrote:
Toggle quote (5 lines)
> Are you sure the bug is fixed in 5.15.23?
>
> I don't see anything relevant in the changelog and I still have to apply
> the workaround in order to boot 5.15.23 on affected hardware.

I'm not sure...I haven't tested. Sorry for that!

The iwlwifi patch is related to use-after-free, but not the one in
5.15.23 changelog. It's this one:
L
L
Ludovic Courtès wrote on 16 Feb 2022 22:17
control message for bug #53712
(address . control@debbugs.gnu.org)
87iltev7e9.fsf@gnu.org
merge 53712 54010
quit
L
L
Ludovic Courtès wrote on 17 Feb 2022 10:12
Re: bug#53712: Guix System hangs after boot with linux-libre 5.15.17
(name . Leo Famulari)(address . leo@famulari.name)
874k4xrh4e.fsf_-_@gnu.org
Hi,

Leo Famulari <leo@famulari.name> skribis:

Toggle quote (13 lines)
> On Tue, Feb 15, 2022 at 03:56:27PM +0100, Ludovic Courtès wrote:
>> 2022 has left me without a working Linux-libre kernel.
>>
>> Breakage occurred sometime between:
>>
>> • 92faad0adb93b8349bfd7c67911d3d95f0505eb2
>> (Jan. 3rd; Linux-libre 5.15.12)
>>
>> • 43dd34c7777a212c99a97da7a2c237158faa9a1b
>> (Jan. 31st; Linux-libre 5.15.17)
>
> Isn't this #53712?

It is!

Toggle quote (6 lines)
> I recommend trying the workaround described there, which is to blacklist
> the iwlwifi kernel module, if you are not using it but have iwlwifi
> hardware:
>
> https://issues.guix.gnu.org/53712#13

I confirm that 5.15.23-gnu works for me with:

(kernel-arguments
"modprobe.blacklist=usbmouse,usbkbd,iwlwifi"
"quiet"))

Thank you!

Ludo’.
?
Your comment

This issue is archived.

To comment on this conversation send an email to 54010@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 54010
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch