Arch Linux

tomcho

Member

Registered: 2020-01-26

Posts: 5

System freezes (apparently) randomly

My laptop (Samsung Notebook 9) has been freezing apparently randomly lately. It used to happen maybe once a month, but it's become more frequently lately (about once or twice a week). I have no idea what's causing. Also I'm not a linux expert, so I'm not sure where to look for possible causes.

Error description:

- system suddenly freezes and reacts to nothing, only hard reset (power off) works
- the display doesn't update at all

Other stuff:

- Laptop is Samsung notebook 9 (np-900)
- processor: intel i5 7th gen
- intel microcode is installed and up to date

Here's a paste bin of `journalctl -b-1` after one of the crashes:

https://paste.ubuntu.com/p/BcNcXS5zVK/

Last edited by tomcho (2020-08-12 17:27:38)

porcelain1

Member

Registered: 2020-01-18

Posts: 97

Re: System freezes (apparently) randomly

I'm also not an expert, but it seems it is Chromium crashing, something related to GPU? I saw this in the end:

[...]
Aug 09 20:33:13 np900 audit[1239]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=1 pid=1239 comm="GpuWatchdog" exe="/usr/lib/chromium/chromium" sig=11 res=1
Aug 09 20:33:13 np900 kernel: GpuWatchdog[1277]: segfault at 0 ip 0000565106122f48 sp 00007f972e5273a0 error 6 in chromium[565101e14000+7866000]
Aug 09 20:33:13 np900 kernel: Code: ce 51 29 ff 48 8b 7d b0 48 8d 45 c0 48 39 c7 74 05 e8 dc f7 b4 fe 41 8b 84 24 e8 00 00 00 89 45 b0 48 8d 7d b0 e8 78 0f eb fb <c7> 04 25 00 00 00 00 37 13 00 00 64 48 8b 04 25 28 00 00 00 48 3b
Aug 09 20:33:13 np900 kernel: audit: type=1701 audit(1597030393.106:189): auid=1000 uid=1000 gid=985 ses=1 pid=1239 comm="GpuWatchdog" exe="/usr/lib/chromium/chromium" sig=11 res=1
Aug 09 20:33:13 np900 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Aug 09 20:33:13 np900 audit: BPF prog-id=16 op=LOAD
Aug 09 20:33:13 np900 kernel: audit: type=1334 audit(1597030393.130:190): prog-id=16 op=LOAD
Aug 09 20:33:13 np900 kernel: audit: type=1334 audit(1597030393.130:191): prog-id=17 op=LOAD
Aug 09 20:33:13 np900 audit: BPF prog-id=17 op=LOAD
Aug 09 20:33:13 np900 systemd[1]: Started Process Core Dump (PID 15812/UID 0).
Aug 09 20:33:13 np900 kernel: audit: type=1130 audit(1597030393.130:192): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-15812-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 09 20:33:13 np900 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-15812-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 09 20:33:14 np900 systemd-coredump[15813]: Process 1239 (chromium) of user 1000 dumped core.
                                               
                                               Stack trace of thread 1277:
                                               #0  0x0000565106122f48 n/a (chromium + 0x5de2f48)
                                               #1  0x0000565104bff6d6 n/a (chromium + 0x48bf6d6)
                                               #2  0x0000565104c1132d n/a (chromium + 0x48d132d)
                                               #3  0x0000565104c110c4 n/a (chromium + 0x48d10c4)
                                               #4  0x0000565104bc4a6c n/a (chromium + 0x4884a6c)
                                               #5  0x0000565104c11a0c n/a (chromium + 0x48d1a0c)
                                               #6  0x0000565104be903a n/a (chromium + 0x48a903a)
                                               #7  0x0000565104c2a415 n/a (chromium + 0x48ea415)
                                               #8  0x0000565104c6a63a n/a (chromium + 0x492a63a)
                                               #9  0x00007f973915e422 start_thread (libpthread.so.0 + 0x9422)
                                               #10 0x00007f9734fbfbf3 __clone (libc.so.6 + 0xffbf3)

[... other stack traces]

Were you using Chromium when your system freezed? Maybe you could try to disable hardware acceleration on it and then let's see if it happens less frequently. After it crashes, can you switch to a virtual console pressing CTRL+ALT+F2? There we could try to reboot more cleanly or kill Chromium if it is still alive (with killall maybe or using top or htop).
I'd recommend the magic REISUB shortcut to reset your computer instead of powering off. I couldn't get it to work when I needed but maybe you can. Just note that the REISUB trick is a last resort, don't rely on it on daily use lol

https://wiki.archlinux.org/index.php/Ke … #Rebooting

Maybe it is your GPU driver. Have you updated it recently? Which is it? Also I dunno if it related, but are you using X or Wayland?

https://wiki.archlinux.org/index.php/Xo … stallation

Last edited by porcelain1 (2020-08-12 18:31:09)

---

Behemoth, wake up!