You are not logged in.
- Topics: Active | Unanswered
#1 2021-01-22 07:40:47
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Need advice on investigating system hangs
Since an update several weeks ago, maybe a month or so, my laptop has these random hangs.
I think it is usually or even only during full screen video playing in browsers (never had it while watching video's on mpv).
The sound will continue, but the image and the mouse will freeze. Using CTRL-ALT-Fx to switch TTY doesn't work.
My fan will strart spinning hard.
If I then press the POWER button (which normally shuts down the computer gracefully), the sound will also stop, but the system will not shut down properly.
I need to hard reset the laptop and every time (even if I waited long), the disk needs error fixing at boot.
I've endured it for a while, hoping that an update would fix it, but it's really becoming a hassle.
I remember the update containing a new driver for nvidia gpu, a new kernel, something with vulkan on the intel gpu, but then also a lot of other things.
I've had several updates on those things I just mentioned since and they didn't solve it.
Where do I start to investigate this?
Offline
#2 2021-01-22 08:07:39
- VoDo
- Member
- From: Europe
- Registered: 2020-06-04
- Posts: 122
Re: Need advice on investigating system hangs
I use this wiki page when looking for problem solution
https://wiki.archlinux.org/index.php/System_maintenance
Archi3
Offline
#3 2021-01-23 15:43:06
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Ok, the journalctl shows the crash:
Jan 23 16:39:46 bto3-arch autossh[444]: ssh exited prematurely with status 255; autossh exiting
Jan 23 16:39:47 bto3-arch kernel:
Jan 23 16:39:47 bto3-arch connman-vpnd[668]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Jan 23 16:39:47 bto3-arch kernel: irq 10: nobody cared (try booting with the "irqpoll" option)
Jan 23 16:39:47 bto3-arch kernel: handlers:
Jan 23 16:39:47 bto3-arch kernel: [<0000000034088b06>] tis_int_handler [tpm_tis_core]
Jan 23 16:39:47 bto3-arch kernel: Disabling IRQ #10
Jan 23 16:39:47 bto3-arch kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Jan 23 16:39:47 bto3-arch kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Jan 23 16:39:47 bto3-arch kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Jan 23 16:39:47 bto3-arch wpa_supplicant[669]: nl80211: kernel reports: Attribute failed policy validation
Jan 23 16:39:47 bto3-arch wpa_supplicant[669]: Failed to create interface p2p-dev-wlp116s0: -22 (Invalid argument)
Jan 23 16:39:47 bto3-arch wpa_supplicant[669]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp116s0
Jan 23 16:39:48 bto3-arch kernel: tpm tpm0: tpm_try_transmit: send(): error -62
Jan 23 16:39:48 bto3-arch kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
Jan 23 16:39:50 bto3-arch systemd-coredump[852]: Process 567 (Xorg) of user 0 dumped core.
Stack trace of thread 567:
#0 0x00007f75daab6615 raise (libc.so.6 + 0x3d615)
#1 0x00007f75daa9f862 abort (libc.so.6 + 0x26862)
#2 0x0000560205fd46ea OsAbort (Xorg + 0x14a6ea)
#3 0x0000560205fd61b1 FatalError (Xorg + 0x14c1b1)
#4 0x0000560205fdbe09 n/a (Xorg + 0x151e09)
#5 0x00007f75daab66a0 __restore_rt (libc.so.6 + 0x3d6a0)
#6 0x0000560205f3d3d9 RRTellChanged (Xorg + 0xb33d9)
#7 0x00005602060459d4 n/a (Xorg + 0x1bb9d4)
#8 0x0000560206045b0a n/a (Xorg + 0x1bbb0a)
#9 0x0000560205fd4331 n/a (Xorg + 0x14a331)
#10 0x0000560205fcfc00 WaitForSomething (Xorg + 0x145c00)
#11 0x0000560205ec3914 n/a (Xorg + 0x39914)
#12 0x00007f75daaa1152 __libc_start_main (libc.so.6 + 0x28152)
#13 0x0000560205ec45de _start (Xorg + 0x3a5de)
Stack trace of thread 807:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 820:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d187063c n/a (i965_dri.so + 0x55763c)
#2 0x00007f75d186feb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 821:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d187063c n/a (i965_dri.so + 0x55763c)
#2 0x00007f75d186feb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 811:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 819:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d187063c n/a (i965_dri.so + 0x55763c)
#2 0x00007f75d186feb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 812:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 808:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 818:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d187063c n/a (i965_dri.so + 0x55763c)
#2 0x00007f75d186feb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 806:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 810:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 809:
#0 0x00007f75da96e6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f75d9d1fb90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f75da9683e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f75dab79293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 567 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Process 567 (Xorg) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Jan 23 16:39:57 bto3-arch lightdm[1011]: gkr-pam: unable to locate daemon control fileI have this when watching video's on youtube and when playing one specific game (Kingdom Two Crowns)...
Everything hangs and I can only force reset the laptop.
Anyone knows what I can do about this?
Offline
#4 2021-01-23 16:09:05
- twelveeighty
- Member
- Registered: 2011-09-04
- Posts: 1,456
Re: Need advice on investigating system hangs
In the span of just those 4 seconds of your journal you posted, there are what appears to be no less than 4 distinct problems, which makes me think they're all connected somehow: 1) your autossh crashes 2) your wireguard seems misconfigured or out of date 3) your TPM driver crashes and 4) your nvidia gpu/driver dumps.
Are you running any TPM stuff on this machine? What is happening with your network config?
Offline
#5 2021-01-23 16:58:21
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
I didn't even know what Wireguard and TPM were... No I don't think I use them.
My network config... I don't know... I use connman for my wireless network connection and that seems to work fine.
Autossh is for a tunnel I like to always have at hand, it is initiated in a self-written systemd service.
Should I simply remove Wireguard and TPM (and how)? I've looked with pacman, I don't see any wireguard package on my system, and also nothing for tpm as far as I know.
Should I switch to NetworkManager? I like connman because then the wifi is also available when not logged into an X session.
Last edited by scippie (2021-01-23 17:08:58)
Offline
#6 2021-01-23 17:59:53
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,025
Re: Need advice on investigating system hangs
Is the system fully up to date? `pacman -Syu`
What modules are loaded? Blacklisting the relevant module is any easy way to try and stop the TPM from being used. `lsmod`
I would leave connman alone if you like it, although I would note NetworkManager does not require X.
Offline
#7 2021-01-23 18:45:10
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Is the system fully up to date? `pacman -Syu`
Yes, it is fully up to date.
What modules are loaded? Blacklisting the relevant module is any easy way to try and stop the TPM from being used. `lsmod`
I've blacklisted tpm, tpm_crb, tpm_tis and tpm_tis_core. I'll be rebooting after this message, I hope everything still works...
Done... everything still works, tpm is disabled. I'll wait a while to see if I have any more system hangs.
I would leave connman alone if you like it, although I would note NetworkManager does not require X.
Oh, I was under the impression that you need the tray icon to use it. I'll look into that, because I've had some issues with Connman (2.4Ghz wifi on channel 6 for example) that I didn't have with NetworkManager, and NM has a plugin for Fortinet VPN's which is useful for me.
Thanks!
Last edited by scippie (2021-01-23 19:32:04)
Offline
#8 2021-01-23 19:46:25
- twelveeighty
- Member
- Registered: 2011-09-04
- Posts: 1,456
Re: Need advice on investigating system hangs
Oh, I was under the impression that you need the tray icon to use it.
No, NetworkManager runs fine on headless machines and you can manage it without the tray app using the CLI tool 'nmcli'.
But, I agree with loqs: it's not likely this has anything to do with connman, I wouldn't replace it if it's not broken.
Offline
#9 2021-01-25 17:13:41
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Ok, I had hoped to be able to mark this thread as solved, but I just had the hang again while watching a youtube video:
Jan 25 18:10:34 bto3-arch autossh[459]: ssh exited prematurely with status 255; autossh exiting
Jan 25 18:10:35 bto3-arch kernel:
Jan 25 18:10:35 bto3-arch connman-vpnd[627]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Jan 25 18:10:35 bto3-arch kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Jan 25 18:10:35 bto3-arch kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Jan 25 18:10:35 bto3-arch kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Jan 25 18:10:35 bto3-arch wpa_supplicant[628]: nl80211: kernel reports: Attribute failed policy validation
Jan 25 18:10:35 bto3-arch wpa_supplicant[628]: Failed to create interface p2p-dev-wlp116s0: -22 (Invalid argument)
Jan 25 18:10:35 bto3-arch wpa_supplicant[628]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp116s0
Jan 25 18:10:38 bto3-arch systemd-coredump[881]: Process 551 (Xorg) of user 0 dumped core.
Stack trace of thread 551:
#0 0x00007f6a1a1ac615 raise (libc.so.6 + 0x3d615)
#1 0x00007f6a1a195862 abort (libc.so.6 + 0x26862)
#2 0x000056081de0e6ea OsAbort (Xorg + 0x14a6ea)
#3 0x000056081de101b1 FatalError (Xorg + 0x14c1b1)
#4 0x000056081de15e09 n/a (Xorg + 0x151e09)
#5 0x00007f6a1a1ac6a0 __restore_rt (libc.so.6 + 0x3d6a0)
#6 0x000056081dd773d9 RRTellChanged (Xorg + 0xb33d9)
#7 0x000056081de7f9d4 n/a (Xorg + 0x1bb9d4)
#8 0x000056081de7fb0a n/a (Xorg + 0x1bbb0a)
#9 0x000056081de0e331 n/a (Xorg + 0x14a331)
#10 0x000056081de09c00 WaitForSomething (Xorg + 0x145c00)
#11 0x000056081dcfd914 n/a (Xorg + 0x39914)
#12 0x00007f6a1a197152 __libc_start_main (libc.so.6 + 0x28152)
#13 0x000056081dcfe5de _start (Xorg + 0x3a5de)
Stack trace of thread 795:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 804:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a10f6663c n/a (i965_dri.so + 0x55763c)
#2 0x00007f6a10f65eb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 803:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a10f6663c n/a (i965_dri.so + 0x55763c)
#2 0x00007f6a10f65eb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 802:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a10f6663c n/a (i965_dri.so + 0x55763c)
#2 0x00007f6a10f65eb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 793:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 805:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a10f6663c n/a (i965_dri.so + 0x55763c)
#2 0x00007f6a10f65eb8 n/a (i965_dri.so + 0x556eb8)
#3 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 796:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 791:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 794:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 792:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 790:
#0 0x00007f6a1a0646a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007f6a19415b90 n/a (intel_drv.so + 0xb0b90)
#2 0x00007f6a1a05e3e9 start_thread (libpthread.so.0 + 0x93e9)
#3 0x00007f6a1a26f293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 551 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ Documentation: man:core(5)
░░
░░ Process 551 (Xorg) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Jan 25 18:10:43 bto3-arch lightdm[1038]: gkr-pam: unable to locate daemon control fileAgain, it started with autossh... and again with the wireguard vpn which I don't use (I think)... that's so weird.
More advice?
Offline
#10 2021-01-27 17:15:36
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
I've tried replacing connman with networkmanager. Didn't help, although the Xorg crash seemed to be gone and the wireguard notification was gone too.
The nvidia-gpu timeout error remains.
Still, it always starts with autossh (which I use all the time on other pc's too, but not as a service), so I removed my hand made systemd service that runs this ssh tunnel and made it an autostart in my i3 session. Let's see what that does.
Last edited by scippie (2021-01-27 17:15:58)
Offline
#11 2021-01-27 20:15:34
- twelveeighty
- Member
- Registered: 2011-09-04
- Posts: 1,456
Re: Need advice on investigating system hangs
It's an easy thing to check if you remove your custom autossh service, so I would recommend giving that a try regardless.
But I think this is something to do with your GPU / Graphics driver: nvidia-gpu and ucsi_ccg are both graphics related. It could very well be that fails first and then your kernel craters, which in turn drops your network stack. I don't think it's the other way around, where your network drivers are causing a GPU failure.
Offline
#12 2021-01-27 20:34:18
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Sidenote: this time the hang didn't occur during a youtube video, but on my own game I'm developing (opengl).
I was testing it on my Intel GPU at the moment of the hang. Same with video playing by the way, that's also Intel GPU.
I use nvidia-prime for heavier games.
I'm just telling because I'm not really using the nvidia at those moments, although I don't know what evil stuff prime does when simply using the Intel GPU of course.
Offline
#13 2021-02-01 21:59:43
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
So like I said, I stopped using my self-created systemd service for the ssh-tunnel and just started autossh from the i3config file. I was almost ready to tell that the problem was gone, but it just happened again during a dosbox session.
Feb 01 22:51:49 bto3-arch kernel:
Feb 01 22:51:49 bto3-arch wpa_supplicant[593]: nl80211: kernel reports: Attribute failed policy validation
Feb 01 22:51:49 bto3-arch wpa_supplicant[593]: Failed to create interface p2p-dev-wlp116s0: -22 (Invalid argument)
Feb 01 22:51:49 bto3-arch wpa_supplicant[593]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp116s0
Feb 01 22:51:49 bto3-arch kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Feb 01 22:51:49 bto3-arch kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Feb 01 22:51:49 bto3-arch kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Feb 01 22:51:55 bto3-arch lightdm[792]: gkr-pam: unable to locate daemon control file
Feb 01 22:51:56 bto3-arch autossh[929]: ssh exited prematurely with status 255; autossh exitingThis time autossh is there again, but now at the end, which might even be when I pressed the power button. You can see that everything hung at 22:51:49. The music from YouTube was still playing in the background. After a few seconds, I pressed the power button shortly. That's when the music stopped and the fan started spinning. I had to hard reset again.
So I guess autossh isn't related (as expected), although it looks again like something went wrong with the network. I'm now using NetworkManager instead of connman.
But at the same time, something happened with the nvidia (which I wasn't using, because I didn't start dosbox with nvidia-prime so it runs on the intel gpu).
I'm at a loss here, but I guess you guys can't figure it out either.
Is there some place I can send these things to, so that maybe if there really is a bug which I'm encountering, I can help them fix it?
Offline
#14 2021-02-01 22:05:36
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,351
Re: Need advice on investigating system hangs
That particular nvidia-gpu error is a non issue (it's from a kernel polling driver that is irrelevant when nouveau isn't the driving force). The xorg dump points at intel traces. Are you using xf86-video-intel? Can you reproduce without it? How up to date are you? Afaik there were a few intel crash fixes in 5.10.11
Offline
#15 2021-02-02 07:27:49
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Hm, the last hang dump doesn't even show Xorg crashing, and shows nothing about Intel. So I am not certain that the hang is related to it. It may of course not have been saved.
I'm quite up to date, but it may have been a week now, so I'm updating now.
Xf86-video-intel is installed so I guess I use it. I don't know why though, and I see in the wiki that it may not be necessary for me.
I'll uninstall it.
Offline
#16 2021-02-05 12:53:21
- tmlrbgfz
- Member
- Registered: 2021-02-05
- Posts: 2
Re: Need advice on investigating system hangs
I'm having exactly the same problem as described in the top post.
The problems seem to start like this:
Feb 05 13:19:21 catalyst kernel: GpuWatchdog[6538]: segfault at 0 ip 000055d659aec519 sp 00007f91dc2044e0 error 6 in Discord[55d6561a1000+5cbb000]The segfault happens in Discord which is not even the program that started the video. I'm using firefox to view youtube videos fullscreen.
Anyways, this causes Discord to coredump:
Feb 05 13:19:22 catalyst systemd-coredump[104542]: Process 6525 (Discord) of user 1000 dumped core.Directly after the core dump I see a message that concerns me:
Feb 05 13:19:22 catalyst kernel: INFO: task kworker/2:2H:56134 blocked for more than 122 seconds.
Feb 05 13:19:22 catalyst kernel: Not tainted 5.10.10-arch1-1 #1
Feb 05 13:19:22 catalyst kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 05 13:19:22 catalyst kernel: task:kworker/2:2H state:D stack: 0 pid:56134 ppid: 2 flags:0x00004080
Feb 05 13:19:22 catalyst kernel: Workqueue: events_highpri intel_atomic_cleanup_work [i915]
Feb 05 13:19:22 catalyst kernel: Call Trace:
Feb 05 13:19:22 catalyst kernel: __schedule+0x295/0x810
Feb 05 13:19:22 catalyst kernel: schedule+0x5b/0xc0
Feb 05 13:19:22 catalyst kernel: schedule_preempt_disabled+0x11/0x20
Feb 05 13:19:22 catalyst kernel: __ww_mutex_lock.constprop.0+0x4bd/0x810
Feb 05 13:19:22 catalyst kernel: ? dequeue_entity+0xc6/0x460
Feb 05 13:19:22 catalyst kernel: intel_unpin_fb_vma+0x25/0xa0 [i915]
Feb 05 13:19:22 catalyst kernel: drm_atomic_helper_cleanup_planes+0x52/0x70 [drm_kms_helper]
Feb 05 13:19:22 catalyst kernel: intel_atomic_cleanup_work+0x67/0x110 [i915]
Feb 05 13:19:22 catalyst kernel: process_one_work+0x1d6/0x3a0
Feb 05 13:19:22 catalyst kernel: worker_thread+0x4d/0x3d0
Feb 05 13:19:22 catalyst kernel: ? rescuer_thread+0x410/0x410
Feb 05 13:19:22 catalyst kernel: kthread+0x133/0x150
Feb 05 13:19:22 catalyst kernel: ? __kthread_bind_mask+0x60/0x60
Feb 05 13:19:22 catalyst kernel: ret_from_fork+0x22/0x30The scheduler seems to block. And some intel (i915) and drm (drm_kms_helper) stuff is in the call trace.
This message is repeated a few times with increasing time values:
Feb 05 13:25:31 catalyst kernel: INFO: task kworker/2:2H:56134 blocked for more than 491 seconds.Do you have any similar messages?
Edit: Come to think of it, the discord stuff happens when the kernel helper is already hanging for 2 Minutes. Maybe the discord crash is just a symptom.
Last edited by tmlrbgfz (2021-02-05 12:54:37)
Offline
#17 2021-02-05 12:57:02
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Do you have any similar messages?
The messages I get are in the above posts and I don't know if they are similar...
I had the crash again yesterday, during a Dosbox session.
I've never had any problems with Discord though and it has never been mentioned in the crash log (unless there's another log I should look at, this is the journalctl log).
If you have suggestions on how to investigate further on my machine, please give them!
Offline
#18 2021-02-05 13:02:38
- tmlrbgfz
- Member
- Registered: 2021-02-05
- Posts: 2
Re: Need advice on investigating system hangs
The other thread I found for my problem also suggests uninstalling xf86-video-intel so if our problems are related, that should fix yours as well.
Edit: The thread I'm talking about: https://bbs.archlinux.org/viewtopic.php?id=262456
Last edited by tmlrbgfz (2021-02-05 13:03:04)
Offline
#19 2021-02-05 13:11:32
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
The other thread I found for my problem also suggests uninstalling xf86-video-intel so if our problems are related, that should fix yours as well.
It was suggested here as well and I uninstalled it, but it still happens.
Offline
#20 2021-02-06 16:53:04
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Just had the hang again, with all the uninstalls it has gotten down to:
Feb 06 17:48:34 bto3-arch kernel:
Feb 06 17:48:34 bto3-arch kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Feb 06 17:48:34 bto3-arch kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Feb 06 17:48:34 bto3-arch kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Feb 06 17:48:34 bto3-arch wpa_supplicant[629]: nl80211: kernel reports: Attribute failed policy validation
Feb 06 17:48:34 bto3-arch wpa_supplicant[629]: Failed to create interface p2p-dev-wlp116s0: -22 (Invalid argument)
Feb 06 17:48:34 bto3-arch wpa_supplicant[629]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp116s0
Feb 06 17:48:42 bto3-arch lightdm[784]: gkr-pam: unable to locate daemon control file
Feb 06 17:48:43 bto3-arch autossh[985]: ssh exited prematurely with status 255; autossh exitingI don't think autossh is related as :43 is about the time I press the power button on my laptop after which the fan starts spinning and everything goes completely hang.
I also don't think the lightdm error at :42 is anything, because that may also be power button related.
It always starts with the nvidia i2c timeout and a networking issue together, so I really think the problem lies there. But how, what... how to solve it...
It doesn't seem to be Xorg related as we first thought, because these last crashes never showed anything about Xorg anymore.
Last edited by scippie (2021-02-06 16:53:41)
Offline
#21 2021-02-06 17:00:50
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,351
Re: Need advice on investigating system hangs
These logs normally happen early during boot and should not have much relevance on a freeze happening later in the running session.
Which commands are you using to produce these? After rebooting from a crash post a complete unfiltered
sudo journalctl -b-1Last edited by V1del (2021-02-06 17:01:57)
Offline
#22 2021-02-06 17:10:03
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Which commands are you using to produce these?
journalctl -p 3 -xbThat's the one I did, I took it from the https://wiki.archlinux.org/index.php/System_maintenance page.
Next time, I'll do your command.
Offline
#23 2021-02-06 17:12:32
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,351
Re: Need advice on investigating system hangs
Yes that will only give the log of the current, not yet frozen boot, so it's not really useful for identifying freezes that you had to reboot from.
Offline
#24 2021-02-06 17:13:35
- scippie
- Member
- Registered: 2019-06-07
- Posts: 168
Re: Need advice on investigating system hangs
Seems it's still available: sudo journalctl -b-1
Feb 06 17:37:35 bto3-arch kernel: ------------[ cut here ]------------
Feb 06 17:37:35 bto3-arch kernel: Trying to vfree() nonexistent vm area (000000000667fdfa)
Feb 06 17:37:35 bto3-arch kernel: WARNING: CPU: 2 PID: 8983 at mm/vmalloc.c:2251 __vunmap+0x6f/0x270
Feb 06 17:37:35 bto3-arch kernel: Modules linked in: snd_seq snd_seq_device ccm rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink xt_addrtype br_netfilter bridge stp llc overlay nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iptable_security nfnetlink ip6table_filter ip6_tables cmac algif_hash algif_skcipher intel_rapl_msr af_alg intel_rapl_common iptable_filter snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common bnep uvcvideo snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof videobuf2_vmalloc videobuf2_memops nvidia_drm(POE) joydev videobuf2_v4l2 nvidia_modeset(POE) videobuf2_common mousedev snd_soc_skl btusb btrtl snd_soc_sst_ipc btbcm ucsi_ccg iTCO_wdt snd_hda_codec_realtek x86_pkg_temp_thermal btintel typec_ucsi
Feb 06 17:37:35 bto3-arch kernel: intel_powerclamp intel_pmc_bxt snd_soc_sst_dsp usbhid mei_hdcp snd_hda_codec_generic ee1004 typec iTCO_vendor_support iwlmvm wmi_bmof intel_wmi_thunderbolt mxm_wmi snd_hda_ext_core bluetooth ledtrig_audio kvm_intel nvidia(POE) snd_soc_acpi_intel_match ecdh_generic snd_soc_acpi mac80211 snd_hda_codec_hdmi ecc kvm snd_hda_intel snd_intel_dspcfg libarc4 soundwire_intel irqbypass soundwire_generic_allocation nls_iso8859_1 crct10dif_pclmul soundwire_cadence crc32_pclmul vfat ghash_clmulni_intel iwlwifi i915 fat aesni_intel snd_hda_codec crypto_simd cryptd glue_helper r8169 snd_hda_core rapl realtek snd_hwdep intel_cstate mdio_devres i2c_algo_bit cfg80211 intel_uncore soundwire_bus thunderbolt pcspkr drm_kms_helper libphy snd_soc_core rfkill mei_me mei i2c_i801 cec i2c_smbus intel_gtt intel_lpss_pci snd_compress syscopyarea intel_lpss sysfillrect ac97_bus sysimgblt idma64 i2c_nvidia_gpu snd_pcm_dmaengine intel_pch_thermal fb_sys_fops i2c_hid wmi video acpi_pad mac_hid coretemp
Feb 06 17:37:35 bto3-arch kernel: snd_aloop snd_pcm snd_timer snd soundcore v4l2loopback_dc(OE) videodev drm mc sg crypto_user fuse acpi_call(OE) agpgart bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 rtsx_pci_sdmmc mmc_core crc32c_intel serio_raw rtsx_pci xhci_pci xhci_pci_renesas
Feb 06 17:37:35 bto3-arch kernel: CPU: 2 PID: 8983 Comm: Discord Tainted: P OE 5.10.11-arch1-1 #1
Feb 06 17:37:35 bto3-arch kernel: Hardware name: Notebook PB50_70RF,RD,RC /PB50_70RF,RD,RC , BIOS 1.07.13 02/01/2019
Feb 06 17:37:35 bto3-arch kernel: RIP: 0010:__vunmap+0x6f/0x270
Feb 06 17:37:35 bto3-arch kernel: Code: 4c 3b 6b f0 73 31 48 8b 5b 10 48 85 db 75 f1 48 c7 c7 a4 f4 02 9e e8 50 82 80 00 4c 89 ee 48 c7 c7 60 d7 17 9d e8 1f a0 7a 00 <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 4c 3b 6b f8 72 06 48 8b 5b
Feb 06 17:37:35 bto3-arch kernel: RSP: 0018:ffffaaa407e3fe60 EFLAGS: 00010286
Feb 06 17:37:35 bto3-arch kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff98d7f0498bb8
Feb 06 17:37:35 bto3-arch kernel: RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff98d7f0498bb0
Feb 06 17:37:35 bto3-arch kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffaaa407e3fc98
Feb 06 17:37:35 bto3-arch kernel: R10: ffffaaa407e3fc90 R11: ffffffff9d8cb228 R12: 0000000000000001
Feb 06 17:37:35 bto3-arch kernel: R13: ffffaaa40b712000 R14: ffff98d085c96160 R15: 0000000000000000
Feb 06 17:37:35 bto3-arch kernel: FS: 00007fcf047a8640(0000) GS:ffff98d7f0480000(0000) knlGS:0000000000000000
Feb 06 17:37:35 bto3-arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 06 17:37:35 bto3-arch kernel: CR2: 00002940831cc788 CR3: 00000003dde06001 CR4: 00000000003706e0
Feb 06 17:37:35 bto3-arch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 06 17:37:35 bto3-arch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Feb 06 17:37:35 bto3-arch kernel: Call Trace:
Feb 06 17:37:35 bto3-arch kernel: v4l2_loopback_close+0x86/0xf0 [v4l2loopback_dc]
Feb 06 17:37:35 bto3-arch kernel: v4l2_release+0xb8/0xc0 [videodev]
Feb 06 17:37:35 bto3-arch kernel: __fput+0x8e/0x230
Feb 06 17:37:35 bto3-arch kernel: task_work_run+0x5c/0x90
Feb 06 17:37:35 bto3-arch kernel: exit_to_user_mode_prepare+0xf7/0x120
Feb 06 17:37:35 bto3-arch kernel: syscall_exit_to_user_mode+0x28/0x160
Feb 06 17:37:35 bto3-arch kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 06 17:37:35 bto3-arch kernel: RIP: 0033:0x7fcf11d0709b
Feb 06 17:37:35 bto3-arch kernel: Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 83 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 e1 fb ff ff 8b 44
Feb 06 17:37:35 bto3-arch kernel: RSP: 002b:00007fcf047a7610 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
Feb 06 17:37:35 bto3-arch kernel: RAX: 0000000000000000 RBX: 0000000000000002 RCX: 00007fcf11d0709b
Feb 06 17:37:35 bto3-arch kernel: RDX: 0000000000000002 RSI: 00007fcf047a7700 RDI: 000000000000004a
Feb 06 17:37:35 bto3-arch kernel: RBP: 00007fcf047a7750 R08: 0000000000000000 R09: 00007fcf047a73c7
Feb 06 17:37:35 bto3-arch kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 00007fcf047a7700
Feb 06 17:37:35 bto3-arch kernel: R13: 0000000000000000 R14: 000000000000004a R15: 0000000000000000
Feb 06 17:37:35 bto3-arch kernel: ---[ end trace 979d5a164fd5e45d ]---
Feb 06 17:48:00 bto3-arch audit[7019]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=7019 comm="GpuWatchdog" exe="/usr/lib/signal-desktop/signal-desktop" sig=11 res=1
Feb 06 17:48:00 bto3-arch kernel: GpuWatchdog[7034]: segfault at 0 ip 000055bfeed51107 sp 00007fbe969e1570 error 6 in signal-desktop[55bfebb70000+53d6000]
Feb 06 17:48:00 bto3-arch kernel: Code: 7d b7 00 79 09 48 8b 7d a0 e8 35 52 d3 fe 8b 83 00 01 00 00 85 c0 0f 84 91 00 00 00 48 8b 03 48 89 df be 01 00 00 00 ff 50 68 <c7> 04 25 00 00 00 00 37 13 00 00 c6 05 17 bc 6f 02 01 80 7d 87 00
Feb 06 17:48:00 bto3-arch kernel: audit: type=1701 audit(1612630080.006:216): auid=1000 uid=1000 gid=1000 ses=2 pid=7019 comm="GpuWatchdog" exe="/usr/lib/signal-desktop/signal-desktop" sig=11 res=1
Feb 06 17:48:00 bto3-arch systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Feb 06 17:48:00 bto3-arch audit: BPF prog-id=23 op=LOAD
Feb 06 17:48:00 bto3-arch kernel: audit: type=1334 audit(1612630080.029:217): prog-id=23 op=LOAD
Feb 06 17:48:00 bto3-arch kernel: audit: type=1334 audit(1612630080.032:218): prog-id=24 op=LOAD
Feb 06 17:48:00 bto3-arch audit: BPF prog-id=24 op=LOAD
Feb 06 17:48:00 bto3-arch systemd[1]: Started Process Core Dump (PID 9277/UID 0).
Feb 06 17:48:00 bto3-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-9277-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 17:48:00 bto3-arch kernel: audit: type=1130 audit(1612630080.032:219): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-9277-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 17:48:00 bto3-arch systemd-coredump[9278]: Process 7019 (signal-desktop) of user 1000 dumped core.
Stack trace of thread 7034:
#0 0x000055bfeed51107 n/a (signal-desktop + 0x48dc107)
#1 0x000055bfeda24620 n/a (signal-desktop + 0x35af620)
#2 0x000055bfeda35b9e n/a (signal-desktop + 0x35c0b9e)
#3 0x000055bfeda35967 n/a (signal-desktop + 0x35c0967)
#4 0x000055bfed9f723a n/a (signal-desktop + 0x358223a)
#5 0x000055bfeda36478 n/a (signal-desktop + 0x35c1478)
#6 0x000055bfeda0f657 n/a (signal-desktop + 0x359a657)
#7 0x000055bfeda4955a n/a (signal-desktop + 0x35d455a)
#8 0x000055bfeda806b5 n/a (signal-desktop + 0x360b6b5)
#9 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#10 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7027:
#0 0x00007fbe99fcc6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007fbe94c5eb3c n/a (iris_dri.so + 0x4edb3c)
#2 0x00007fbe94c5d308 n/a (iris_dri.so + 0x4ec308)
#3 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7043:
#0 0x00007fbe99fcc6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x000055bfeda7d512 n/a (signal-desktop + 0x3608512)
#2 0x000055bfeda7dbe9 n/a (signal-desktop + 0x3608be9)
#3 0x000055bfeda7da0f n/a (signal-desktop + 0x3608a0f)
#4 0x000055bfed9f7278 n/a (signal-desktop + 0x3582278)
#5 0x000055bfeda36478 n/a (signal-desktop + 0x35c1478)
#6 0x000055bfeda0f657 n/a (signal-desktop + 0x359a657)
#7 0x000055bfeda4955a n/a (signal-desktop + 0x35d455a)
#8 0x000055bfeda806b5 n/a (signal-desktop + 0x360b6b5)
#9 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#10 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7030:
#0 0x00007fbe99fcc6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007fbe94c5eb3c n/a (iris_dri.so + 0x4edb3c)
#2 0x00007fbe94c5d308 n/a (iris_dri.so + 0x4ec308)
#3 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7019:
#0 0x00007fbe9899046f __poll (libc.so.6 + 0xf546f)
#1 0x00007fbe99b0463b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007fbe99b0645b xcb_wait_for_special_event (libxcb.so.1 + 0xe45b)
#3 0x00007fbe9600b949 n/a (libGLX_mesa.so.0 + 0x50949)
#4 0x00007fbe96011e3b n/a (libGLX_mesa.so.0 + 0x56e3b)
#5 0x00007fbe960064db n/a (libGLX_mesa.so.0 + 0x4b4db)
#6 0x000055bfee5bb2ff n/a (signal-desktop + 0x41462ff)
#7 0x000055bfee5bc7a3 n/a (signal-desktop + 0x41477a3)
#8 0x000055bfeda24620 n/a (signal-desktop + 0x35af620)
#9 0x000055bfeda35b9e n/a (signal-desktop + 0x35c0b9e)
#10 0x000055bfeda35967 n/a (signal-desktop + 0x35c0967)
#11 0x000055bfed9f756a n/a (signal-desktop + 0x358256a)
#12 0x000055bfeda36478 n/a (signal-desktop + 0x35c1478)
#13 0x000055bfeda0f657 n/a (signal-desktop + 0x359a657)
#14 0x000055bff0537ac9 n/a (signal-desktop + 0x60c2ac9)
#15 0x000055bfed23d4a4 n/a (signal-desktop + 0x2dc84a4)
#16 0x000055bfeef703b4 n/a (signal-desktop + 0x4afb3b4)
#17 0x000055bfec5f0551 n/a (signal-desktop + 0x217b551)
#18 0x000055bfebb70e7b n/a (signal-desktop + 0x16fbe7b)
#19 0x00007fbe988c3152 __libc_start_main (libc.so.6 + 0x28152)
#20 0x000055bfebb70c2a _start (signal-desktop + 0x16fbc2a)
Stack trace of thread 7036:
#0 0x00007fbe99fcc9c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
#1 0x000055bfeda7d650 n/a (signal-desktop + 0x3608650)
#2 0x000055bfeda7dbc0 n/a (signal-desktop + 0x3608bc0)
#3 0x000055bfeda45db8 n/a (signal-desktop + 0x35d0db8)
#4 0x000055bfeda46504 n/a (signal-desktop + 0x35d1504)
#5 0x000055bfeda462c4 n/a (signal-desktop + 0x35d12c4)
#6 0x000055bfeda806b5 n/a (signal-desktop + 0x360b6b5)
#7 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#8 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7029:
#0 0x00007fbe99fcc6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007fbe94c5eb3c n/a (iris_dri.so + 0x4edb3c)
#2 0x00007fbe94c5d308 n/a (iris_dri.so + 0x4ec308)
#3 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7037:
#0 0x00007fbe9899b5de epoll_wait (libc.so.6 + 0x1005de)
#1 0x000055bfedb168ba n/a (signal-desktop + 0x36a18ba)
#2 0x000055bfedb14219 n/a (signal-desktop + 0x369f219)
#3 0x000055bfeda8b07f n/a (signal-desktop + 0x361607f)
#4 0x000055bfeda36478 n/a (signal-desktop + 0x35c1478)
#5 0x000055bfeda0f657 n/a (signal-desktop + 0x359a657)
#6 0x000055bfeda4955a n/a (signal-desktop + 0x35d455a)
#7 0x000055bfeda806b5 n/a (signal-desktop + 0x360b6b5)
#8 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#9 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7028:
#0 0x00007fbe99fcc6a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x00007fbe94c5eb3c n/a (iris_dri.so + 0x4edb3c)
#2 0x00007fbe94c5d308 n/a (iris_dri.so + 0x4ec308)
#3 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 7035:
#0 0x00007fbe9899b5de epoll_wait (libc.so.6 + 0x1005de)
#1 0x000055bfedb168ba n/a (signal-desktop + 0x36a18ba)
#2 0x000055bfedb14219 n/a (signal-desktop + 0x369f219)
#3 0x000055bfeda8b12c n/a (signal-desktop + 0x361612c)
#4 0x000055bfeda36478 n/a (signal-desktop + 0x35c1478)
#5 0x000055bfeda0f657 n/a (signal-desktop + 0x359a657)
#6 0x000055bfeda3f514 n/a (signal-desktop + 0x35ca514)
#7 0x000055bfeda4955a n/a (signal-desktop + 0x35d455a)
#8 0x000055bfeda806b5 n/a (signal-desktop + 0x360b6b5)
#9 0x00007fbe99fc63e9 start_thread (libpthread.so.0 + 0x93e9)
#10 0x00007fbe9899b293 __clone (libc.so.6 + 0x100293)
Feb 06 17:48:00 bto3-arch systemd[1]: systemd-coredump@0-9277-0.service: Succeeded.
Feb 06 17:48:00 bto3-arch kernel: audit: type=1131 audit(1612630080.426:220): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-9277-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 17:48:00 bto3-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-9277-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 06 17:48:00 bto3-arch systemd-logind[449]: Power key pressed.
Feb 06 17:48:00 bto3-arch systemd-logind[449]: Powering Off...
Feb 06 17:48:00 bto3-arch systemd-logind[449]: System is powering down.Offline
#25 2021-02-06 17:19:26
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,351
Re: Need advice on investigating system hangs
That's just a part of it redirect into a file and/or post to a pastebin or so, it might be helpful to have a bit of the information prior to that kernel dump.
However from what we see here there seems to be an issue with the v4l2 loopback kernel module, so you might want to try and disable/uninstall that and testing whether you can reproduce while it isn't loaded.
Assuming this is coming from droidcam or so, check /etc/modules-load.d and /etc/modprobe.d and remove the module from these files, set up an explicit blacklist to ensure it isn't getting loaded
Last edited by V1del (2021-02-06 17:24:36)
Offline