You are not logged in.
In the past two days I've been experiencing random crashes. Nothing shows up in any logs, journalctl only has this from before the last two today:
Jul 14 16:27:32 yumiko dhcpcd[680]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 16:27:32 yumiko dhcpcd[680]: wlp2s0: refresh in 86400 seconds
Jul 14 16:29:32 yumiko dhcpcd[680]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 16:29:32 yumiko dhcpcd[680]: wlp2s0: refresh in 86400 seconds
Jul 14 16:32:02 yumiko dhcpcd[680]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 16:32:02 yumiko dhcpcd[680]: wlp2s0: refresh in 86400 seconds
Jul 14 16:33:14 yumiko clamd[672]: Wed Jul 14 16:33:14 2021 -> SelfCheck: Database status OK.
Jul 14 16:33:48 yumiko dhcpcd[680]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 16:33:48 yumiko dhcpcd[680]: wlp2s0: refresh in 86400 seconds
Jul 14 16:35:54 yumiko dhcpcd[680]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 16:35:54 yumiko dhcpcd[680]: wlp2s0: refresh in 86400 seconds
-- Boot 3e9d2840771544a89a8c60422aed431e --
Jul 14 21:45:25 yumiko dhcpcd[675]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 21:45:25 yumiko dhcpcd[675]: wlp2s0: refresh in 86400 seconds
Jul 14 21:47:12 yumiko dhcpcd[675]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 21:47:12 yumiko dhcpcd[675]: wlp2s0: refresh in 86400 seconds
Jul 14 21:48:35 yumiko kglobalaccel5[968]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
[...]
Jul 14 21:48:42 yumiko kglobalaccel5[968]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
Jul 14 21:49:49 yumiko dhcpcd[675]: wlp2s0: REPLY6 received from fe80::362c:c4ff:fe69:7b5d
Jul 14 21:49:49 yumiko dhcpcd[675]: wlp2s0: refresh in 86400 seconds
Jul 14 21:49:59 yumiko kglobalaccel5[968]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
[...]
Jul 14 21:50:21 yumiko kglobalaccel5[968]: kf.windowsystem.keyserver.x11: Your keyboard setup doesn't provide a key to use for meta. See 'xmodmap -pm' or 'xkbcomp $DISPLAY'
-- Boot c6d394fb93804ad3a424cc0be3bf87b4 --
I omitted some from the second because that kglobalaccel5[968] line is there dozens of times.
Now, I hope it's just a coincidence but I replaced my external monitor when this started, the earlier broke. Its resolution is higher, 2560x1440 from the earlier 1920x1080, but that shouldn't cause something like that, right? I can't really go back on it if that's the issue. My laptop only has an MX150. I'm wondering if one of the GPUs causes the crash anyway. I also seen some weird behavior, when it boots up the resolution after mode switching is 4K, then it falls down to a low resolution with a weird aspect ratio in SDDM and the login screen looks broken on the internal monitor when the external's plugged in. I can't tie it to anything I do, either, sometimes I'm watching a YouTube video, sometimes I'm working, sometimes I'm playing Minecraft.
Laptop: Asus VivoBook S530UN
CPU: Intel Core i5-8250U
Linux version: 5.12.15.arch1-1 (also tried the current LTS 5.10.49-1, same result)
Nvidia version: 465.31-14
DE: KDE
I set the dGPU as primary based on this guide but it was working fine so far.
Any ideas?
Offline
How bad is the crash? Can you still ping the system (or ssh into it)?
=> https://bbs.archlinux.org/viewtopic.php?id=267824 but that's "only" Xorg
Otherwise: Is the monitor attached via HDMI or Displayport?
For DP 465xx has a known issue w/ at least some outputs, https://bbs.archlinux.org/viewtopic.php?id=265563
For HDMI it might be just the cable - you could try to drive the output at FullHD and see whether you still encounter crashes.
Offline
How bad is the crash? Can you still ping the system (or ssh into it)?
=> https://bbs.archlinux.org/viewtopic.php?id=267824 but that's "only" Xorg
Otherwise: Is the monitor attached via HDMI or Displayport?
For DP 465xx has a known issue w/ at least some outputs, https://bbs.archlinux.org/viewtopic.php?id=265563
For HDMI it might be just the cable - you could try to drive the output at FullHD and see whether you still encounter crashes.
Total crash, nothing responds and the screen is just frozen in place with seemingly every second line being either green or purple. HDMI cable, came with the monitor. I do have another one somewhere, I'll try that first.
Offline
A bad cable would not harm the rest of the system (you just can't see anything anymore, but eg. the network stack would not be affected and you could still ping the system)
Sounds more like the GPU crashes and takes the kernel with it, so either a HW issue or we're in the realm of the rather weird 465xx bug (you could either downgrade to some 460xx or try the 470xx beta driver from the AUR)
Offline
Doesn't sound great, I hope it's not my GPU dying, that would be inconvenient to deal with. So far I replaced the HDMI cable and got a crash while I was typing this. This time it actually rebooted in a few seconds. I'll try the beta driver for now.
Also, not sure if it's relevant but this is how the SDDM login looks like. It always turns on the internal display, that's nothing new, but there's something glitchy here, the resolution is low and stretched out on the external display and there's some weird thing going on on the internal, only a smaller square of the screen is the actual screen and the rest is... not sure what that is:
Offline
You can either make sddm use xrandr to configure the outputs in /usr/share/sddm/scripts/Xsetup
Or you configure them https://wiki.archlinux.org/title/Multih … _xorg.conf
You might already be doing the latter w/ an nvidia-settings generated /etc/X11/xorg.conf - which is aligned to the previous external output w/ lower resolution?
Offline
The beta driver didn't help, for now I restored the current one and reverted the changes for using only the dGPU. Maybe the iGPU won't cause issues, using it like that for some time now and it's holding. SDDM is also different, for some reason it defaults to 4K now. I may force 1440p on it.
Offline
or some reason it defaults to 4K now
The output names change w/ the gpu/driver, so whatever configured it to a different resolution now runs into unavailable outputs (see my previous post)
I assume the external output is wired to the dGPU anyway?
Feel free to post your current xorg log.
Offline
Tried without setting the dGPU as primary but didn't help. Not sure how much it's used now, the primary is definitely the Intel chip, but it just froze again. This time no artifacts on the screen, just a clean freeze.
Xorg.0.log.old at https://0x0.st/-OhR.old
Offline
The HDMI output seems wire to the intel chip, nvidia might be a 3D accelerator "only",
lspci
?
[ 21.853] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[ 21.853] (--) intel(0): Output HDMI1 using initial mode 3840x2160 on pipe
Step one: remove xf86-video-intel to use the modesetting driver.
Still a problem?
Offline
Removed it, SDDM didn't change resolution to 4K now, that's one better. We'll see the freeze by tomorrow.
Current Xorg.0.log at https://0x0.st/-VrV.log
And lspci out at https://0x0.st/-VrW.txt
Offline
Same cause: changing the driver changes the output names - so the likely present (now mis-)configuration does't work and you end up w/ the defaults.
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
The nvidia chip is currently not involved in any of this (unless you prime-run stuff)
Offline
So, in the past few days I was running Lubuntu from a USB hard drive to see if it crashes, that would suggest some hardware issue but nothing, no crash at all. Not a 100% but hopefully there's nothing wrong with my laptop hardware-wise.
I switched to LXQt in Arch, long shot that there's something in KDE/Plasma but I'll test everything I can come up with. Worst case scenario I do a clean reinstall.
Last edited by KorvinSilver (2021-07-23 10:15:00)
Offline
Still no idea what the issue is, and I've given up. I reinstall Arch when I can.
Offline