Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69161 - [linux] full system freezes during boot / login
Attached to Project:
Arch Linux
Opened by Ferdinand Bachmann (Ferdi265) - Friday, 01 January 2021, 01:28 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 11:14 GMT
Opened by Ferdinand Bachmann (Ferdi265) - Friday, 01 January 2021, 01:28 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 11:14 GMT
|
DetailsDescription:
After updating to Linux 5.10.4, my system freezes unrecoverably during boot, and sometimes as late as starting sway (I login on the tty, no display manager). The system also appears to run a little slower than normal before freezing. (subjective experience, not measured) Hardware: Lenovo V330 Laptop, Intel Graphics, i3-8130U processor Freezes encountered: - boot works, tty login works, full system freeze as I start sway (login tty still visible, but full freeze) - boot works, tty login works, full system freeze as I try to switch back to tty1 from tty3 after running some commands there - boot freezes after initrd systemd switched to host systemd, but before tty login visible |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 21 April 2021, 11:14 GMT
Reason for closing: Fixed
Additional comments about closing: not reproducible after 5.10.4.arch2-1
Wednesday, 21 April 2021, 11:14 GMT
Reason for closing: Fixed
Additional comments about closing: not reproducible after 5.10.4.arch2-1
Comment by Ferdinand Bachmann (Ferdi265) -
Friday, 01 January 2021, 23:37 GMT
Seems to be fixed by 5.10.4.arch2-1.