Closed jacobgkau closed 3 years ago
I don't see any output when pressing
ESC
at the stuck splash screen
Are all the command line options that hide logs removed, like quiet
? And try without splash
as well.
Are all the command line options that hide logs removed, like
quiet
? And try withoutsplash
as well.
Ok, after removing all of the log-suppressing options, I'm seeing a kernel panic, but it's scrolling very quickly. I'll need to take a video and go frame-by-frame to see what it says. There are a couple of psmouse serio2: synaptics:
lines about the touchpad after the kernel panic.
Photo of where it ends up:
Screen grab of the beginning of the panic:
Video with a few more frames in between: https://user-images.githubusercontent.com/7199422/139335556-a3b7981a-229c-455a-aa81-767a606d536c.mp4
Does this help?
It looks like a number of items can't be removed:
kernfs: can not remove 'uevent', no directory
...
kernfs: can not remove 'waiting_for_supplier', no directory
...
kernfs: can not remove 'online', no directory
...
kernfs: can not remove 'name', no directory
...
kernfs: can not remove 'phys', no directory
...
kernfs: can not remove 'uniq', no directory
...
kernfs: can not remove 'nodalias', no directory
...
kernfs: can not remove 'inhibited', no directory
I can force it to happen.
Distribution (run
cat /etc/os-release
): Pop!_OS 21.04, Pop!_OS 20.04 LTS, Ubuntu 20.04 LTSRelated Application and/or Package Version (run
apt policy $PACKAGE NAME
): system76-acpi-dkms version c169971892d4bd0fa8524a86b2da36d990fc1d7b and b82bcba7d90abc99f76f7072e8e31d7b9de64e18Issue/Bug Description: The system hangs at the firmware splash screen and does not display the cryptsetup screen.
Steps to reproduce (if you know):
Expected behavior: System should boot
Other Notes: Only affects darp6/galp4 running proprietary EC, does not affect systems transitioned to Open EC (only darp6 has Open EC officially released.)
Checked out c169971892d4bd0fa8524a86b2da36d990fc1d7b, built & installed, still had the issue; checked out 0bc966cf8ec11a173e0bdffb9d5df8d99bea2617, built & installed, and did not have the issue. Based on this, it appears the issue is in c169971892d4bd0fa8524a86b2da36d990fc1d7b and not necessarily b82bcba7d90abc99f76f7072e8e31d7b9de64e18.
I don't see any output when pressing
ESC
at the stuck splash screen, and nothing is being logged to journalctl on affected boots.