[Closed] Crash with new Kernel (5.5)

Hooly · 2020-02-05 19:32:42

I don't know where this should go, as I'm not sure what exactly is causing this and I'm new to Arch so I'm posting this here.

Earlier i left my PC to make dinner. When i returned, all the top bars of all the windows were gone (where Minimize, Maximize and Close are located). None of those windows would respond to clicking, discord was reacting to hovering the mouse above it though. Trying to switch to TTY2 did not work.

After roughly a minute the desktop crashed to a black screen, link: https://imgur.com/a/CAQRbsf

Used software during crash: Brave browser, discord.

DE: Gnome (X11), video wallpaper (mp4) using komorebi

CPU: AMD Ryzen 7 3800X
GPU: Gigabyte RX 5700XT
Mainboard: X570 Pro Carbon Wifi

Thanks in advance

Last edited by Hooly (2020-04-27 08:32:06)

loqs · 2020-02-05 20:01:24

Welcome to the arch linux forums Hooly. I would suggest booting live media and run a S.M.A.R.T. self test on the systems storage devices.
Then post the results to a pastebin. (see tip box in link) I would advise against mounting the device again until you have done the above
and have also created duplicates of the devices if you need any files from them.

Hooly · 2020-02-06 17:22:16

I ran the short test on the drive where my Arch install is located, which returned:

SMART overall-health self-assessment test result: PASSED

I accidentally booted into Arch, which worked without issues, though after locking and then unlocking the screen started to flicker with blue-greenish rectangles.

The drive is a Samsung EVO 860 with 512GB btw.

I'm using a dual boot setup with Win10 located on a separate drive, i doubt that this is leading to this issue, though.

loqs · 2020-02-06 19:34:47

SMART overall-health self-assessment test result: PASSED

The self-assessment passes can pass even drives with serious issues. Could you please share the output of

# smartctl -a /dev/<device>

When you booted Arch did fsck detect any issues with the filesystem?

Hooly · 2020-02-06 20:09:00

I didn't see any issues on boot (nosplash).

I will run the extended scan tomorrow, its too late for today.

loqs · 2020-02-06 20:11:01

The short test is fine. When you have time just share the results.

Hooly · 2020-02-07 13:06:32

Pardon, using pastebin didn't work, as i was unable to mount any of my devices with r+w to save the output. (probably Windows' fast reboot or hibernation)

https://imgur.com/a/lWsLH8k

EDIT: I've ran

journalctl -xe | grep fsck

which reported only a minor error on my USB drive (not properly unmounted)

The flickering after locking the screen is gone, too.

Is it safe to assume that this crash is not reproducible?

EDIT2: According to https://wiki.archlinux.org/index.php/Po … nsistently this might be an issue with the kernel and/or the graphics drivers. For now, i've disabled the option to suspend after a certain time of inactivity.

Last edited by Hooly (2020-02-09 12:48:33)

Hooly · 2020-02-09 13:05:45

After applying this workaround I haven't experienced this issue again, so i guess this thread can be closed.

Nevertheless, thank you for your swift reaction and cooperativeness, loqs.

Last edited by Hooly (2020-02-09 13:05:59)

Arch Linux

#1 2020-02-05 19:32:42

[Closed] Crash with new Kernel (5.5)

#2 2020-02-05 20:01:24

Re: [Closed] Crash with new Kernel (5.5)

#3 2020-02-06 17:22:16

Re: [Closed] Crash with new Kernel (5.5)

#4 2020-02-06 19:34:47

Re: [Closed] Crash with new Kernel (5.5)

#5 2020-02-06 20:09:00

Re: [Closed] Crash with new Kernel (5.5)

#6 2020-02-06 20:11:01

Re: [Closed] Crash with new Kernel (5.5)

#7 2020-02-07 13:06:32

Re: [Closed] Crash with new Kernel (5.5)

#8 2020-02-09 13:05:45

Re: [Closed] Crash with new Kernel (5.5)

Board footer