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#70212 - [linux] random system freezes / graphical glitches
Attached to Project:
Arch Linux
Opened by Ferdinand Bachmann (Ferdi265) - Monday, 29 March 2021, 23:05 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 11 March 2022, 17:02 GMT
Opened by Ferdinand Bachmann (Ferdi265) - Monday, 29 March 2021, 23:05 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 11 March 2022, 17:02 GMT
|
DetailsDescription:
My system seems to fully freeze sometimes with Kernel 5.11.10.arch1-1, not responding to anything except a forced reboot. It also froze once why my tty-based screen locker was up, which let me see some kernel log messages (crash1.jpg). I suspect the fault listed there is either unrelated or triggered by earlier corruption somewhere. While waiting for the system to respond or resort to forcing a reboot, I noticed the tty graphics became glitchy/corrupted (crash2.jpg). Additional info: * package version(s): linux-5.11.10.arch1-1 * config and/or log files: (screen photo, though I suspect the fault is unrelated) * device info: Lenovo V330 Laptop with Intel i3-8130U Steps to reproduce: The system freeze happened twice today during normal use, and once while locked (see photos). I haven't been able to reproduce it on purpose yet. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Friday, 11 March 2022, 17:02 GMT
Reason for closing: Fixed
Friday, 11 March 2022, 17:02 GMT
Reason for closing: Fixed
crash1.jpg
Since I can't seem to be able to reproduce this on purpose (it hasn't happened since the report, though I did not use my system a lot since then) and 5.11.11 is already out, I will update to that and see if it reoccurs.
If nothing happens in the next week I suspect it to have been a random unreproducible bug or fixed in 5.11.11.