You are not logged in.
Hi there
After my weekly update discord is no longer functioning - to be more precise: Opening discord and using an audio device leads to a full crash that makes the PC unusable.
What I do:
- Open discord
- Join any voice chat
Result:
All USB devices unusable - plugging off any device brings no result, I can no longer use the system and need to manually shut down.
On next reboot, all works fine.
What I verified:
- Open discord via web interface: same result
- Open another app like Zoom: audio works fine
USB devices I use:
- ZSA Moonlander Keyboard
- Logitech Gaming Mouse
- Beyerdynamics MMX 150 USB Headset
- Logitech C920 webcam
Output of lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 003: ID 0db0:422d Micro Star International USB Audio
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 007: ID 0e8d:0616 MediaTek Inc. Wireless_Device
Bus 001 Device 008: ID 1462:7d75 Micro Star International MYSTIC LIGHT
Bus 001 Device 009: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 010: ID 046d:c088 Logitech, Inc. G Pro Wireless gaming mouse (wired mode)
Bus 001 Device 011: ID 2e50:0026 Solid State System Co.,Ltd. MMX 150
Bus 001 Device 012: ID 3297:1969 ZSA Moonlander Mark I
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 003: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 004: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubOutput of dmesg -T -l err:
[Mo Feb 5 21:24:43 2024] hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Mo Feb 5 21:24:45 2024] snd_hda_intel 0000:10:00.6: no codecs found!
[Mo Feb 5 21:24:45 2024] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023This is the output of journalctl -xe | grep -iE 'alsa|pulseaudio|audio|error|warning':
Feb 05 21:25:02 oc-arch gnome-session[1979]: gnome-session-binary[1979]: GnomeDesktop-WARNING: Could not create transient scope for PID 1986: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 05 21:25:02 oc-arch gnome-session-binary[1979]: GnomeDesktop-WARNING: Could not create transient scope for PID 1986: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86CameraAccessEnable
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86CameraAccessDisable
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86CameraAccessToggle
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86NextElement
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86PreviousElement
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86AutopilotEngageToggle
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86MarkWaypoint
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86Sos
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86NavChart
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86FishingChart
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86SingleRangeRadar
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86DualRangeRadar
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86RadarOverlay
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86TraditionalSonar
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86ClearvuSonar
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86SidevuSonar
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: > Warning: Could not resolve keysym XF86NavInfo
Feb 05 21:25:03 oc-arch /usr/lib/gdm-x-session[2062]: Errors from xkbcomp are not fatal to the X server
Feb 05 21:25:03 oc-arch systemd[1794]: Started PipeWire PulseAudio.
Feb 05 21:25:03 oc-arch wireplumber[2283]: [0:00:22.634474159] [2283] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Feb 05 21:25:03 oc-arch wireplumber[2283]: [0:00:22.634484199] [2283] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Feb 05 21:25:03 oc-arch wireplumber[2283]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
Feb 05 21:25:03 oc-arch gsd-usb-protect[2135]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Feb 05 21:25:03 oc-arch gnome-shell[2002]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Feb 05 21:25:03 oc-arch mutter-x11-fram[2039]: Theme parser error: gtk.css:2667:14-18: Negative values are not allowed
Feb 05 21:25:03 oc-arch mutter-x11-fram[2039]: Theme parser error: gtk.css:5639:3-9: No property named "height"
Feb 05 21:25:03 oc-arch xdg-desktop-por[2365]: Theme parser error: gtk.css:2667:14-18: Negative values are not allowed
Feb 05 21:25:03 oc-arch xdg-desktop-por[2365]: Theme parser error: gtk.css:5639:3-9: No property named "height"
Feb 05 21:25:05 oc-arch pipewire[2279]: [0:00:24.642516083] [2279] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Feb 05 21:25:05 oc-arch pipewire[2279]: [0:00:24.642523753] [2279] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Feb 05 21:25:05 oc-arch wireplumber[2283]: <WpSiAudioAdapter:0x63582a8a09a0> Object activation aborted: proxy destroyed
Feb 05 21:25:05 oc-arch wireplumber[2283]: <WpSiAudioAdapter:0x63582a8a09a0> failed to activate item: Object activation aborted: proxy destroyed
Feb 05 21:25:05 oc-arch wireplumber[2283]: <WpPortalPermissionStorePlugin:0x63582a6028b0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Feb 05 21:25:05 oc-arch wireplumber[2283]: <WpPortalPermissionStorePlugin:0x63582a6028b0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Feb 05 21:25:14 oc-arch systemd[992]: Stopping PipeWire PulseAudio...
Feb 05 21:25:14 oc-arch systemd[992]: Stopped PipeWire PulseAudio.
Feb 05 21:25:14 oc-arch systemd[992]: Closed PipeWire PulseAudio.Sidenote: I removed some Bitwarden stuff from the logs, but I don't think that should be relevant.
Thanks & regards
Last edited by unbekanntespferd (2024-02-25 17:28:31)
Offline
Grepping the session journal for random tokens will hardly reveal discord related USB issues.
Also "need to manually shut down" that means with the power button? Because in that case you also won't be able to preserve the journal of the bad boot.
Does it work if you detach the webcam?
Or replace the usb headset w/ some phone-jack wired headphones?
Can you ssh into the discord-locked system?
Offline
Thank you for the ideas. After unplugging the web cam (Logitech C920 webcam) it works fine.
So it is an issue with the webcam - I'll provide logs via ssh later.
Offline
Unfortunately I was wrong - it is not an issue with the webcam and re-appeared again.
Now the interesting part is: if I log in PRIOR the freeze via ssh, the freeze does not happen.
Therefore I'm currently unable to provide any other more meaningful logs.
Any other ideas on how to dig deeper here?
Offline
if I log in PRIOR the freeze via ssh, the freeze does not happen.
Network?
Does it help to throw yourself a lifeline and just keep "ping 8.8.8.8" running to avoid the freeze?
Avoid hard reboots at all costs, try https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - this should preserve the journal so you can inspect it after a reboot ("…-b -1…")
Offline
So throwing the lifeline does not work using "ping 8.8.8.8" (it does keep pinging but all devices are unresponsive).
I can still log in via ssh afterwards but the USB devices are unusable.
This is the output of journalctl --since "2024-02-25 17:50" --until "tomorrow" -p 4 on the relevant time where my usb devices became unresponsive.
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:07 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: WARN: buffer overrun event for slot 9 ep 4 on endpoint
Feb 25 18:02:08 oc-arch kernel: xhci_hcd 0000:0e:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0019 address=0xffdc5000 flags=0x0000]
Feb 25 18:02:33 oc-arch kernel: usb 1-5.1.3.3: 2:0: usb_set_interface failed (-110)The output of dmesg is this
[So Feb 25 18:00:07 2024] hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
[So Feb 25 18:00:10 2024] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023
[So Feb 25 18:00:10 2024] snd_hda_intel 0000:10:00.6: no codecs found!
[So Feb 25 18:02:08 2024] xhci_hcd 0000:0e:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0019 address=0xffdc5000 flags=0x0000]
[So Feb 25 18:02:33 2024] usb 1-5.1.3.3: 2:0: usb_set_interface failed (-110)In any case, I can access the journal during / after a freeze and still interact with the system.
Using reboot via ssh though does not restart the system correctly and the reboot process freezes as well.
Is there any other command I can use to gracefully shut down via ssh?
To narrow down the problem:
When I use any video / audio related software like Discord - meaning: open a new video / audio call (also happens when using Google Meet) and I am not connected prior via SSH my USB devices die.
Last edited by unbekanntespferd (2024-02-25 17:31:36)
Offline
skip the "-p 4", the filtered journal just lists the failure.
Is there any other command I can use to gracefully shut down via ssh?
https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
https://en.wikipedia.org/wiki/Magic_Sys … agic_SysRq
To narrow down the problem:
Likely pipewire/wireplumber/pulseaudio…
Offline