You are not logged in.

#1 2023-01-27 11:53:12

DonCammne
Member
Registered: 2023-01-27
Posts: 10

Strange Freeze of my Laptop

I have Arch for 1 month now and only recently my laptop freezes (sometimes I'm unable to do anything, sometimes the cursor moves but nothing responds). I wasn't able to reproduce the error as I please, but I think it is linked with dunst and flameshot.

My laptop is a Lenovo ThinkPad X1 Carbon Gen 9, I have the system updated, awesome as WM, Xorg, picom and polybar (if you need more info, just tell me, this is my first post).

Here the result of "journal -p 3 -b" just after the freeze stopped:

archlinux kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Jan 25 17:11:06 archlinux kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
Jan 25 17:11:11 archlinux bluetoothd[497]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c)
Jan 25 17:11:20 archlinux bluetoothd[497]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Jan 26 09:27:44 archlinux sudo[10914]: pam_unix(sudo:auth): conversation failed
Jan 26 09:27:44 archlinux sudo[10914]: pam_unix(sudo:auth): auth could not identify password for [xutior]
Jan 26 11:01:08 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 26 15:05:39 archlinux python[29999]: io/hpmud/jd.c 93: unable to read device-id
Jan 26 15:05:39 archlinux hp-systray[29999]: [29997]: error: Unable to communicate with device (code=12): hp:/net/OfficeJet_Pro_6970?ip=192.168.1.128
Jan 26 15:05:39 archlinux hp-systray[29999]: hp-systray(hpdio)[29999]: error: Device not found
Jan 26 15:06:38 archlinux simple-scan[30082]: protocol/discovery/avahiDiscovery.c 472: Failed to create client object: Daemon not running
Jan 26 15:39:48 archlinux python[33351]: io/hpmud/jd.c 93: unable to read device-id
Jan 26 15:39:48 archlinux hp-systray[33351]: [33349]: error: Unable to communicate with device (code=12): hp:/net/OfficeJet_Pro_6970?ip=192.168.1.128
Jan 26 15:39:48 archlinux hp-systray[33351]: hp-systray(hpdio)[33351]: error: Device not found
Jan 26 15:40:40 archlinux simple-scan[33478]: protocol/discovery/avahiDiscovery.c 472: Failed to create client object: Daemon not running
Jan 26 15:41:50 archlinux systemd-coredump[33668]: [?] Process 602 (dunst) of user 1000 dumped core.

                                                   Stack trace of thread 602:
                                                   #0  0x00007f268218bb04 pthread_mutex_lock (libc.so.6 + 0x89b04)
                                                   #1  0x00007f2682734733 XrmDestroyDatabase (libX11.so.6 + 0x4c733)
                                                   #2  0x00007f268272e8c6 XrmSetDatabase (libX11.so.6 + 0x468c6)
                                                   #3  0x0000557fefc35561 n/a (dunst + 0x1d561)
                                                   #4  0x0000557fefc359e8 n/a (dunst + 0x1d9e8)
                                                   #5  0x00007f268235982b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b)
                                                   #6  0x00007f26823b0cc9 n/a (libglib-2.0.so.0 + 0xaccc9)
                                                   #7  0x00007f2682358d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                                                   #8  0x0000557fefc2563f n/a (dunst + 0xd63f)
                                                   #9  0x00007f2682125290 n/a (libc.so.6 + 0x23290)
                                                   #10 0x00007f268212534a __libc_start_main (libc.so.6 + 0x2334a)
                                                   #11 0x0000557fefc25ca5 n/a (dunst + 0xdca5)

                                                   Stack trace of thread 611:
                                                   #0  0x00007f26821fd37f __poll (libc.so.6 + 0xfb37f)
                                                   #1  0x00007f26823b0c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                                                   #2  0x00007f26823580e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                                                   #3  0x00007f2682358132 n/a (libglib-2.0.so.0 + 0x54132)
                                                   #4  0x00007f2682386db5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                   #5  0x00007f26821888fd n/a (libc.so.6 + 0x868fd)
                                                   #6  0x00007f268220ad20 n/a (libc.so.6 + 0x108d20)

                                                   Stack trace of thread 613:
                                                   #0  0x00007f26821fd37f __poll (libc.so.6 + 0xfb37f)
                                                   #1  0x00007f26823b0c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                                                   #2  0x00007f2682358d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                                                   #3  0x00007f26825b0aec n/a (libgio-2.0.so.0 + 0x10aaec)
                                                   #4  0x00007f2682386db5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                   #5  0x00007f26821888fd n/a (libc.so.6 + 0x868fd)
                                                   #6  0x00007f268220ad20 n/a (libc.so.6 + 0x108d20)
                                                   ELF object binary architecture: AMD x86-64
Jan 26 16:50:43 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)

Looking at "coredumpctl list":

TIME                          PID  UID  GID SIG     COREFILE EXE                SIZE
Wed 2023-01-18 00:24:49 CET   569 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 00:27:37 CET  2147 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 00:27:48 CET   574 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 00:28:08 CET  3090 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 00:29:53 CET  2163 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 00:31:27 CET  3508 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 00:32:38 CET  3107 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 00:33:12 CET  3525 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 00:36:39 CET  4484 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 00:41:28 CET  4493 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 01:52:22 CET  5782 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 01:53:53 CET  5791 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 01:57:52 CET 15972 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 02:17:48 CET   566 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 02:18:32 CET   571 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 02:26:51 CET  4078 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 02:27:52 CET  4087 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 02:28:57 CET  5971 1000 1000 SIGSEGV missing  /usr/bin/polybar      -
Wed 2023-01-18 02:31:55 CET  5988 1000 1000 SIGSEGV missing  /usr/bin/xidlehook    -
Wed 2023-01-18 21:18:36 CET   567 1000 1000 SIGSEGV missing  /usr/bin/dunst        -
Thu 2023-01-26 15:41:50 CET   602 1000 1000 SIGSEGV present  /usr/bin/dunst     1.6M

The last one gives:

PID: 602 (dunst)
           UID: 1000 (xutior)
           GID: 1000 (xutior)
        Signal: 11 (SEGV)
     Timestamp: Thu 2023-01-26 15:41:50 CET (21h ago)
  Command Line: dunst -config /dev/fd/63
    Executable: /usr/bin/dunst
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (xutior)
       Boot ID: 912c82b5f8ac4712851e92f4208bb05d
    Machine ID: b23c23ad1d444eaabe9b470b3c1d1860
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.dunst.1000.912c82b5f8ac4712851e92f4208bb05d.602.1674744>
  Size on Disk: 1.6M
       Message: Process 602 (dunst) of user 1000 dumped core.

                Stack trace of thread 602:
                #0  0x00007f268218bb04 pthread_mutex_lock (libc.so.6 + 0x89b04)
                #1  0x00007f2682734733 XrmDestroyDatabase (libX11.so.6 + 0x4c733)
                #2  0x00007f268272e8c6 XrmSetDatabase (libX11.so.6 + 0x468c6)
                #3  0x0000557fefc35561 n/a (dunst + 0x1d561)
                #4  0x0000557fefc359e8 n/a (dunst + 0x1d9e8)
                #5  0x00007f268235982b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b)
                #6  0x00007f26823b0cc9 n/a (libglib-2.0.so.0 + 0xaccc9)
                #7  0x00007f2682358d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                #8  0x0000557fefc2563f n/a (dunst + 0xd63f)
                #9  0x00007f2682125290 n/a (libc.so.6 + 0x23290)
                #10 0x00007f268212534a __libc_start_main (libc.so.6 + 0x2334a)
                #11 0x0000557fefc25ca5 n/a (dunst + 0xdca5)

                Stack trace of thread 611:
                #0  0x00007f26821fd37f __poll (libc.so.6 + 0xfb37f)
                #1  0x00007f26823b0c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f26823580e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                #3  0x00007f2682358132 n/a (libglib-2.0.so.0 + 0x54132)
                #4  0x00007f2682386db5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f26821888fd n/a (libc.so.6 + 0x868fd)
                #6  0x00007f268220ad20 n/a (libc.so.6 + 0x108d20)

                Stack trace of thread 613:
                #0  0x00007f26821fd37f __poll (libc.so.6 + 0xfb37f)
                #1  0x00007f26823b0c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f2682358d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                #3  0x00007f26825b0aec n/a (libgio-2.0.so.0 + 0x10aaec)
                #4  0x00007f2682386db5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f26821888fd n/a (libc.so.6 + 0x868fd)
                #6  0x00007f268220ad20 n/a (libc.so.6 + 0x108d20)
                ELF object binary architecture: AMD x86-64

At boot, the result of "journal -p 3 -b" is:

Jan 27 12:09:29 archlinux kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Jan 27 12:09:29 archlinux kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
Jan 27 12:09:34 archlinux bluetoothd[503]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c)
Jan 27 12:09:42 archlinux bluetoothd[503]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

Apart for this freeze problem, I never had any problem that I couldn't solve by myself (looking at the archwiki, searching for similar problems, etc).

Thank you very.

Offline

#2 2023-01-27 15:15:04

seth
Member
Registered: 2012-09-03
Posts: 53,555

Re: Strange Freeze of my Laptop

Jan 26 16:50:43 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)

Please post the complete journal of a boot covering such freeze, but I'll guess you've an nvme?

See whether you get anything like https://wiki.archlinux.org/title/Solid_ … leshooting and regardless try "nvme_core.default_ps_max_latency_us=0" and "iommu=soft"

Offline

#3 2023-01-30 08:31:00

DonCammne
Member
Registered: 2023-01-27
Posts: 10

Re: Strange Freeze of my Laptop

Thank you very much for the reply and sorry for responding only now, I was out of the grid for the entire weekend.

Yes, I have a nvme SSD.

About the journalctl, to see if that could be the problem, I ran

journalctl | grep "ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)"

and I got:

Jan 17 20:29:43 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 18 03:02:23 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 18 18:16:18 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 18 19:58:59 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 19 15:26:48 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 26 11:01:08 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)
Jan 26 16:50:43 archlinux kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-16)

The number of times and the date I get the error seem to be connected to when I recall getting these freezes.

The complete journal from the boot that you requested is too big (9000 lines) and pastebin doesn't let me post it. By using this line:

journalctl -b -2 -p 5 

I get this journal (less big and pastebin let me post it).

When I have some free time, I'll try what you suggested and I'll get back here with the infos.

Thanks again for the help, Seth.

Offline

#4 2023-01-30 08:46:28

seth
Member
Registered: 2012-09-03
Posts: 53,555

Re: Strange Freeze of my Laptop

The complete journal from the boot that you requested is too big

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#5 2023-01-30 09:30:14

DonCammne
Member
Registered: 2023-01-27
Posts: 10

Re: Strange Freeze of my Laptop

Ok, I tried with your prompt:

sudo journalctl -b -2 | curl -F 'file=@-' 0x0.st

If it's not working let me know, thanks.

The journal.

Offline

#6 2023-01-30 09:54:45

seth
Member
Registered: 2012-09-03
Posts: 53,555

Re: Strange Freeze of my Laptop

The errors in the wiki aren't present, but you could still try the suggested mitigations and see whether that has positive impact, notably because

The number of times and the date I get the error seem to be connected to when I recall getting these freezes.

Offline

#7 2023-01-30 15:12:26

DonCammne
Member
Registered: 2023-01-27
Posts: 10

Re: Strange Freeze of my Laptop

I tried this https://wiki.archlinux.org/title/Solid_ … leshooting and in the entire journal there is nothing.

About this "nvme_core.default_ps_max_latency_us=0" and this "iommu=soft" suggestions, I don't get how to try them, they aren't prompts nor journal logs.

I think that the best way to go now, is to wait that I get another freeze and when it happens, I note the time and I post here the journal of the entire boot, to target the relevant logs.

Thank you very much for your time, Seth. In the best case that I have no more freeses in, say, 3 months, I'll close the thread as solved (if that's ok).

Offline

#8 2023-01-30 17:20:37

seth
Member
Registered: 2012-09-03
Posts: 53,555

Offline

#9 2023-01-31 08:51:47

DonCammne
Member
Registered: 2023-01-27
Posts: 10

Re: Strange Freeze of my Laptop

Thank you, I'll try with that and see.

Offline

Board footer

Powered by FluxBB