[Solved] Applications not starting on some boots

Skoltr · 2024-05-29 05:05:17

Good day, I've recently started running into an issue where launching (almost) any application will hang indefinitely without any visible output.
Strangely it only happens on some boots, my Greeter always appears and allows me to log in, but then when I try to start applications nothing happens.

Usually I start applications through UI (using Xfce) but even when starting through terminal there is no output, and often I can't interrupt the process even.
This also happens when I try to run pacman for example.

I could use some pointers on where in such a scenario I should be looking for logs or such.
I frequently update all my packages so I guess it came with a recent update, I believe it started to happen last friday.

Last edited by Skoltr (2024-06-14 07:48:08)

impossibleveins23 · 2024-05-29 09:53:20

*What had changed? Did it start happening after a system update?
*Can you drop to a TTY (Ctrl+Shift+F4...) and upload the log? Can you upload the logs?

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

Skoltr · 2024-05-29 10:16:35

impossibleveins23 wrote:

*What had changed? Did it start happening after a system update?
*Can you drop to a TTY (Ctrl+Shift+F4...) and upload the log? Can you upload the logs?
journalctl -b | curl -F 'file=@-' 0x0.st

Unfortunately I don't know exactly what changed before it started happening, I noticed there were two kernel updates in the last week, but no clue if that's related.
Not sure if this is what you wanted but below is a log file. Ctrl+Shift+F4 doesn't do anything on my device, CTRL+ALT+F4 does.

These are taken when things were working fine, I don't know if that's helpful.

taken with term emulator
http://0x0.st/XNMY.txt
tty
http://0x0.st/XNMU.txt

This is the log, I noticed a lot of spam which afaik means something is up with one of my USB devices, but that would seem unrelated.
I don't know if it can be related but I believe I should consider updating my bios as last time my hardware was still relatively new and I saw some microcode warnings.
Just couldn't find my usb sticks this morning :-).

Last edited by Skoltr (2024-05-29 10:17:18)

impossibleveins23 · 2024-05-29 11:00:51

* Regarding system upgrade, you can check pacman log (/var/log/pacman.log) and correlate with the time the problem started.
* Is the CPU under load? Constantly? When you start the non-working applications?
* You mentioned the problem is when you start applications. Which applications did you mean? Graphical only? What do you see when you try to run them from CLI? With debug flags/env var?

seth · 2024-05-29 15:26:15

May 29 11:57:33 mathijs-arch kernel: xhci_hcd 0000:10:00.0: Host supports USB 3.2 Enhanced SuperSpeed
May 29 11:57:33 mathijs-arch kernel: usb usb1: SerialNumber: 0000:10:00.0
May 29 11:57:33 mathijs-arch kernel: usb usb2: SerialNumber: 0000:10:00.0
May 29 11:57:33 mathijs-arch kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.0/0003:046D:C52B.0006/input/input8
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:046D:C52B.0006: input,hidraw5: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:10:00.0-3/input0
May 29 11:57:33 mathijs-arch kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0007/input/input9
May 29 11:57:33 mathijs-arch kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0007/input/input10
May 29 11:57:33 mathijs-arch kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0007/input/input11
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:046D:C52B.0007: input,hiddev96,hidraw6: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:10:00.0-3/input1
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:046D:C52B.0008: hiddev97,hidraw7: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:10:00.0-3/input2
May 29 11:57:33 mathijs-arch kernel: logitech-djreceiver 0003:046D:C52B.0008: hiddev96,hidraw5: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:10:00.0-3/input2
May 29 11:57:33 mathijs-arch kernel: input: Logitech Wireless Device PID:4041 Keyboard as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.0009/input/input13
May 29 11:57:33 mathijs-arch kernel: input: Logitech Wireless Device PID:4041 Mouse as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.0009/input/input14
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:046D:4041.0009: input,hidraw6: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4041] on usb-0000:10:00.0-3/input2:1
May 29 11:57:33 mathijs-arch kernel: input: Logitech Wireless Device PID:4041 Keyboard as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.000A/input/input18
May 29 11:57:33 mathijs-arch kernel: input: Logitech Wireless Device PID:4041 Mouse as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.000A/input/input19
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:046D:4041.000A: input,hidraw7: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4041] on usb-0000:10:00.0-3/input2:2
May 29 11:57:33 mathijs-arch kernel: input: Logitech MX Master as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.0009/input/input23
May 29 11:57:33 mathijs-arch kernel: logitech-hidpp-device 0003:046D:4041.0009: input,hidraw6: USB HID v1.11 Keyboard [Logitech MX Master] on usb-0000:10:00.0-3/input2:1
May 29 11:57:33 mathijs-arch kernel: input: Logitech MX Master as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0008/0003:046D:4041.000A/input/input24
May 29 11:57:33 mathijs-arch kernel: logitech-hidpp-device 0003:046D:4041.000A: input,hidraw7: USB HID v1.11 Keyboard [Logitech MX Master] on usb-0000:10:00.0-3/input2:2
May 29 11:57:33 mathijs-arch kernel: hid-generic 0003:0DB0:422D.000B: hiddev97,hidraw8: USB HID v1.11 Device [Generic USB Audio] on usb-0000:10:00.0-6/input7
May 29 11:57:34 mathijs-arch kernel: input: MSI MYSTIC LIGHT  as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:10:00.0/usb1/1-10/1-10:1.0/0003:1462:7D75.000C/input/input34
May 29 11:57:34 mathijs-arch kernel: hid-generic 0003:1462:7D75.000C: input,hiddev98,hidraw9: USB HID v1.10 Device [MSI MYSTIC LIGHT ] on usb-0000:10:00.0-10/input0
May 29 11:58:01 mathijs-arch kernel: xhci_hcd 0000:10:00.0: WARN: buffer overrun event for slot 4 ep 6 on endpoint

The log is massive and proactically only xhci_hcd warnings
Remove/replace the logitech devices and/or plug them into another port - does the issue remain?

Skoltr · 2024-05-29 18:02:10

accidentally double posted.

Last edited by Skoltr (2024-05-29 18:04:46)

Skoltr · 2024-05-29 18:04:26

I had the problem again, I think most of the USB spam is gone I did remove my microphone (I don't need it anymore anyway),
as I mentioned the log I posted previously was likely not ideal as it was from a session where I could actually start apps etc.
I have a log here that was preventing me to actually start applications, it also has some stack traces I believe of tasks not being able to complete.
http://0x0.st/XNe6.txt

The microcode warning seems scary I'll look into that one.

impossibleveins23 wrote:

* Regarding system upgrade, you can check pacman log (/var/log/pacman.log) and correlate with the time the problem started.
* Is the CPU under load? Constantly? When you start the non-working applications?
* You mentioned the problem is when you start applications. Which applications did you mean? Graphical only? What do you see when you try to run them from CLI? With debug flags/env var?

I can see the pacman log in a bit, It will likely be hard to see what has changed as I had a lot of packages updating over the last week afaik.
The CPU was running at 0.3 percent when I checked earlier.
When I run things from the CLI I see nothing, no output; I do see the timeouts that are in the last log I posted now, I forgot to check if I could add debug flags, but I think it just doesn't start.

I thought it started happening before, but it might have come when I installed blueman last week.

Last edited by Skoltr (2024-05-29 18:28:48)

seth · 2024-05-29 20:50:04

May 29 19:25:46 mathijs-arch kernel: Bluetooth: hci0: Device setup in 20240917 usecs
May 29 19:25:46 mathijs-arch kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
May 29 19:25:46 mathijs-arch kernel: Bluetooth: hci0: AOSP extensions version v1.00
May 29 19:25:46 mathijs-arch kernel: Bluetooth: hci0: AOSP quality report is supported
May 29 19:25:46 mathijs-arch bluetoothd[835]: Battery Provider Manager created
May 29 19:25:46 mathijs-arch kernel: Bluetooth: MGMT ver 1.22
May 29 19:25:46 mathijs-arch kernel: NET: Registered PF_ALG protocol family
May 29 19:25:46 mathijs-arch bluetoothd[835]: Failed to set mode: Failed (0x03)
May 29 19:25:46 mathijs-arch bluetoothd[835]: Failed to set mode: Failed (0x03)
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 2 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Successfully made thread 1133 of process 950 owned by '1000' RT at priority 5.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 3 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 3 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Successfully made thread 1135 of process 950 owned by '1000' RT at priority 5.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 4 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 4 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Successfully made thread 1137 of process 950 owned by '1000' RT at priority 5.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 5 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 5 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Successfully made thread 1139 of process 950 owned by '1000' RT at priority 5.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 6 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 6 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Successfully made thread 1141 of process 950 owned by '1000' RT at priority 5.
May 29 19:25:47 mathijs-arch rtkit-daemon[762]: Supervising 7 threads of 1 processes of 1 users.
May 29 19:25:47 mathijs-arch pulseaudio[950]: Failed to find a working profile.
May 29 19:25:47 mathijs-arch pulseaudio[950]: Failed to load module "module-alsa-card" (argument: "device_id="3" name="pci-0000_12_00.6" card_name="alsa_card.pci-0000_12_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
May 29 19:25:47 mathijs-arch systemd[862]: Started Sound Service.
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_453
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_453
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_512
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_512
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_552
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_552
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/faststream
May 29 19:25:47 mathijs-arch bluetoothd[835]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/faststream
May 29 19:25:47 mathijs-arch kernel: Bluetooth: RFCOMM TTY layer initialized
May 29 19:25:47 mathijs-arch kernel: Bluetooth: RFCOMM socket layer initialized
May 29 19:25:47 mathijs-arch kernel: Bluetooth: RFCOMM ver 1.11
May 29 19:25:55 mathijs-arch systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 29 19:26:25 mathijs-arch systemd-udevd[461]: 0000:0f:00.0: Worker [506] processing SEQNUM=4508 is taking a long time
May 29 19:26:26 mathijs-arch systemd-udevd[461]: enp14s0: Worker [514] processing SEQNUM=5374 is taking a long time
May 29 19:28:25 mathijs-arch systemd-udevd[461]: 0000:0f:00.0: Worker [506] processing SEQNUM=4508 killed
May 29 19:28:26 mathijs-arch systemd-udevd[461]: enp14s0: Worker [514] processing SEQNUM=5374 killed
May 29 19:29:19 mathijs-arch kernel: INFO: task kworker/7:1:137 blocked for more than 122 seconds.
May 29 19:29:19 mathijs-arch kernel:       Not tainted 6.9.2-arch1-1 #1
May 29 19:29:19 mathijs-arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 29 19:29:19 mathijs-arch kernel: task:kworker/7:1     state:D stack:0     pid:137   tgid:137   ppid:2      flags:0x00004000
May 29 19:29:19 mathijs-arch kernel: Workqueue: events hidpp_connect_event [hid_logitech_hidpp]
May 29 19:29:19 mathijs-arch kernel: Call Trace:
May 29 19:29:19 mathijs-arch kernel:  <TASK>
May 29 19:29:19 mathijs-arch kernel:  __schedule+0x3c7/0x1510
May 29 19:29:19 mathijs-arch kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 29 19:29:19 mathijs-arch kernel:  schedule+0x27/0xf0
May 29 19:29:19 mathijs-arch kernel:  schedule_preempt_disabled+0x15/0x30
May 29 19:29:19 mathijs-arch kernel:  rwsem_down_write_slowpath+0x1d3/0x660
May 29 19:29:19 mathijs-arch kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
May 29 19:29:19 mathijs-arch kernel:  down_write+0x5a/0x60
May 29 19:29:19 mathijs-arch kernel:  led_trigger_register+0x125/0x1a0

It's down to the specific input device and some bluetooth relation seems likely.
You can probably plug some wired keybaord/mouse in and use them?

You're using a unifying receiver? Can you attach the devices via regular bluetooth?

Skoltr · 2024-05-30 04:35:32

Do you think it could be conflicting with connecting my recent Bluetooth headphones?
I will try to run with my MX master connected regularly for a bit.

I just realized the Unifying receiver was also in my front USB so perhaps I might have screwed up the installation of the cables a little; however it has been working fine for over a year now.
Anyways I will test this setup for a bit.

seth · 2024-05-30 06:16:36

Actually I confused this thread w/ a "my input stops working" one, sorry.

Bluetooth starts and then there're hanging udev jobs on your wifi and ethernet device - your MT7922 wifi doesn't get picked up at all.
This is probably all symptom of the same IO stall and the most likely culprit actually your wifi NIC not showing up to the party.

Does it matter whether you boot cold or warm?
Can you reproduce this w/ the LTS kernel?

Skoltr · 2024-06-03 04:52:17

seth wrote:

Actually I confused this thread w/ a "my input stops working" one, sorry.
Bluetooth starts and then there're hanging udev jobs on your wifi and ethernet device - your MT7922 wifi doesn't get picked up at all.
This is probably all symptom of the same IO stall and the most likely culprit actually your wifi NIC not showing up to the party.
Does it matter whether you boot cold or warm?
Can you reproduce this w/ the LTS kernel?

I've not yet had this ussue after installing LTS, afaik it boots with it as default now but I'm not always there to check.

Last edited by Skoltr (2024-06-03 04:54:18)

seth · 2024-06-03 07:22:16

https://bbs.archlinux.org/viewtopic.php?id=295942 but that's supposed to be fixed w/ 6.9.2 and you don't have teh FW loading issues in your journal.

Does it help to add mt7921e to the MODULES hook (and thus the initramfs)?

Edit: if not try to add "pcie_aspm=off" to the https://wiki.archlinux.org/title/Kernel_parameters
There's also "mt7921e. disable_aspm" but the module doesn't even seem to load…

Last edited by seth (2024-06-03 07:24:42)

Skoltr · 2024-06-14 07:46:24

Sorry for not coming back to you.
I have been using LTS since it was suggested without any issues.

I might look into your suggestions later, but perhaps it is best to solve this for now.

Arch Linux

#1 2024-05-29 05:05:17

[Solved] Applications not starting on some boots

#2 2024-05-29 09:53:20

Re: [Solved] Applications not starting on some boots

#3 2024-05-29 10:16:35

Re: [Solved] Applications not starting on some boots

#4 2024-05-29 11:00:51

Re: [Solved] Applications not starting on some boots

#5 2024-05-29 15:26:15

Re: [Solved] Applications not starting on some boots

#6 2024-05-29 18:02:10

Re: [Solved] Applications not starting on some boots

#7 2024-05-29 18:04:26

Re: [Solved] Applications not starting on some boots

#8 2024-05-29 20:50:04

Re: [Solved] Applications not starting on some boots

#9 2024-05-30 04:35:32

Re: [Solved] Applications not starting on some boots

#10 2024-05-30 06:16:36

Re: [Solved] Applications not starting on some boots

#11 2024-06-03 04:52:17

Re: [Solved] Applications not starting on some boots

#12 2024-06-03 07:22:16

Re: [Solved] Applications not starting on some boots

#13 2024-06-14 07:46:24

Re: [Solved] Applications not starting on some boots

Board footer