FS#64302 - [linux] 5.3.7-2 kernel hangs during boot on chromebook

Attached to Project: Arch Linux
Opened by Dean Wallace (duffydack) - Monday, 28 October 2019, 20:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 20 November 2019, 00:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description:
After updating the linux pkg to 5.3.7-2 (gcc rebuild), my Toshiba (Baytrail) and Acer (Braswell) chromebooks hang during boot due to kernel panic.
This is due to google modules being added. See https://bugs.archlinux.org/task/55784.
Additional info:
* linux 5.3.7.arch1-2
* CONFIG_GOOGLE_SMI=m

Steps to reproduce:
Update linux pkg and reboot.

The fix to boot successfully:
add module_blacklist=gsmi to bootloader.

Can't find anything upstream about it.
   IMG_20191028_193108.jpg (573.4 KiB)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Wednesday, 20 November 2019, 00:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  gsmi disabled in linux 5.3.9.1-1
Comment by Lauri Gustafsson (gustafla) - Tuesday, 29 October 2019, 09:50 GMT
This happens on my ThinkPad X230 running coreboot (Tianocore payload).

Here's a boot log that shows gsmi acting weirdly.
   gsmi_unknown_error.log (112 KiB)
Comment by Raphael Nestler (rnestler) - Tuesday, 29 October 2019, 15:31 GMT
My Librem 13 Laptop also had a kernel panic during boot after upgrading to linux-5.3.7.arch1-2. After rebooting I got a different panic, see the attached screenshots. Booting with `systemd.unit=emergency.target` let me downgrade the kernel.
   photo_2019-10-29_16-29-30.jpg (216 KiB)
   photo_2019-10-29_16-29-33.jpg (228.6 KiB)
Comment by Dean Wallace (duffydack) - Tuesday, 29 October 2019, 15:48 GMT
Similar to my error messages. Does blacklisting gsmi fix for you? I'm not sure how to fix this properly without blacklisting, other than reverting the modules being enabled in kernel, but that's for the archGodz to decide.
Comment by Raphael Nestler (rnestler) - Tuesday, 29 October 2019, 16:36 GMT
> Does blacklisting gsmi fix for you?

Yes, blacklisting gsmi fixed it for me as well.
Comment by Parker Young (Parker8283) - Wednesday, 30 October 2019, 04:19 GMT
I am also experiencing the same problem. Using coreboot 4.10 from MrChromebox's UEFI on a Lenovo 100S Chromebook. Blacklisting gsmi or downgrading to 5.3.7.arch1-1 fixes the issue. Log file attached.
   2019-10-30-00-00.log (211.8 KiB)
Comment by Tom Hiller (thrilleratplay) - Thursday, 31 October 2019, 12:37 GMT
Blacklisting gsmi also fixed this issue for me on my x230 (coreboot/SeaBios).
Comment by mike (mbalajew) - Thursday, 31 October 2019, 13:01 GMT
Also experienced the same issue (X200, T420 running vanilla coreboot with seabios). Blacklisting gsmi or downgrading to 5.3.7.arch1-1 fixes the issue.
Comment by Stuart P. Bentley (stuart) - Thursday, 31 October 2019, 20:22 GMT
Acer C710-2833 here (coreboot/latest MrChromebox firmware). Per https://bbs.archlinux.org/viewtopic.php?pid=1871255#p1871255, I was still able to boot with gsmi enabled, but with my wifi driver broken. Blacklisting the module fixed that.
Comment by Jan Alexander Steffens (heftig) - Sunday, 03 November 2019, 10:02 GMT
This is something upstream will have to fix. You can blacklist the module until they do.
Comment by Jan Alexander Steffens (heftig) - Sunday, 03 November 2019, 10:42 GMT
Actually, I think the SMI stuff isn't needed for the console access of  FS#55784  so I'll disable SMI next release.
Comment by Wes Fournier (wes.fournier) - Thursday, 07 November 2019, 01:31 GMT
Experienced this issue on a Librem 15 (also uses coreboot). Blacklisting gsmi fixed it for me.
   dmesg-output (61.4 KiB)
Comment by Yves Mermoud (ymermoud) - Thursday, 07 November 2019, 08:35 GMT
Same here on a thinkpad x230 with coreboot, blacklisting gsmi fixes it