Suspending leads to complete shutdown

Leana_CHIANG · January 14, 2025, 12:28pm

Which Linux distro are you using?
NixOS

Which release version?
24.11.20250106.3f0a8ac

Which kernel are you using?
6.6.69

Which BIOS version are you using?
3.05

Framework 13 model
I’m using AMD Ryzen 7040 series

I have this issue that when I disconnect my USB-C dock, and close my framework for it to go to suspend (configured with nix + systemd), it would not suspend successfully. I have not been able to wake it up correctly – when I reopen the laptop, it would restart at the boot loader menu, followed by LUKS and a complete boot.

In the systemd log I couldn’t find information related to the suspend, beside that it succeeded. It seems like it suspended fine, except what follows it in the log seems to be a complete boot, similar to my observations.

Is there any documented issue like this?

Thank you for your time reading this post

... elided
Jan 14 09:04:50 vanadium systemd[1]: Starting Fingerprint Authentication Daemon...
Jan 14 09:04:50 vanadium systemd[1]: Starting System Suspend...
Jan 14 09:04:50 vanadium systemd-timesyncd[1573]: Network configuration changed, trying to establish connection.
Jan 14 09:04:50 vanadium systemd-sleep[489930]: Successfully froze unit 'user.slice'.
Jan 14 09:04:50 vanadium systemd-sleep[489930]: Performing sleep operation 'suspend'...
Jan 14 09:04:50 vanadium kernel: PM: suspend entry (s2idle)
-- Boot b61945b59e5944908537db7bd300d353 --
Jan 14 13:15:15 vanadium kernel: Linux version 6.6.69 (nixbld@localhost) (gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.43.1) #1-NixOS SMP PREEMPT_DYNAM>
Jan 14 13:15:15 vanadium kernel: Command line: initrd=\EFI\nixos\i573zmx5qbb0q3j5x2s3frn69w1z49jg-initrd-linux-6.6.69-initrd.efi init=/nix/store/4yf>
Jan 14 13:15:15 vanadium kernel: BIOS-provided physical RAM map:
Jan 14 13:15:15 vanadium kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Jan 14 13:15:15 vanadium kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000bffff] reserved
Jan 14 13:15:15 vanadium kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009afffff] usable
Jan 14 13:15:15 vanadium kernel: BIOS-e820: [mem 0x0000000009b00000-0x0000000009dfffff] reserved
... elided

dimitris · January 14, 2025, 7:39pm

Extremely speculative question: Could the SSD somehow be involved? Is it possible to try with a different SSD?

re: BIOS version: sudo dmidecode -t bios should print it, current release is 3.05.

Leana_CHIANG · January 14, 2025, 8:13pm

Thank you for your help!

I currently don’t have another NVME drive to test it out.
I also have noticed that it only happens after I undock my laptop: it only happens after the first suspend after undocking it.
Also, it’s odd because the command uptime doesn’t count from what seems like a full boot sequence.

I have checked the BIOS version with the command you provided, it’s of version 3.05.

dimitris · January 14, 2025, 8:36pm

Anything interesting in the log at/around undock time? Speculating about some driver getting into a funky state due to a suddenly disappeared device.

Also, while your kernel is LTS (edit: actually two point releases behind the currentl LTS of 6.6.71), it would also be worth trying with latest (currently 6.12.9) if possible.

Leana_CHIANG · January 15, 2025, 12:10pm

Hello, thanks again for your reply

I indeed had a lot of USB errors when I undock the laptop.
This was the case with the kernel 6.6.69. I read your message yesterday in my mails, and decided to switch to kernel 6.12.8 (I don’t know how to get 6.12.9 with NixOS, this is the one available). The USB errors persisted.

Here’s a log of that (kernel 6.12.8) (You can see I open the lid and undock it, and pipewire starts failing)

Jan 15 07:57:00 vanadium systemd-logind[1575]: Lid opened.
Jan 15 07:57:02 vanadium kernel: usb 5-1: USB disconnect, device number 2
Jan 15 07:57:02 vanadium kernel: usb 5-1.1: USB disconnect, device number 3
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: Unable to submit urb #0: -19 at snd_usb_queue_pending_output_urbs
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb (err = -19)
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: Unable to submit urb #0: -19 at snd_usb_queue_pending_output_urbs
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 6-1: USB disconnect, device number 4
Jan 15 07:57:02 vanadium kernel: usb 6-1.3: USB disconnect, device number 5
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: r8152-cfgselector 6-1.4: USB disconnect, device number 6
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: [drm] DM_MST: stopping TM on aconnector: 00000000cf0c3024 [id: 107]
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3: USB disconnect, device number 4
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.3: USB disconnect, device number 6
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: cannot submit urb 0, error -19: no device
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.4: USB disconnect, device number 7
Jan 15 07:57:02 vanadium kernel: usb 5-1.3.5: USB disconnect, device number 8
Jan 15 07:57:02 vanadium kernel: usb 5-1.5: USB disconnect, device number 5
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: carrier lost
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting address fded:dbef:cb40::219/128
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: (0 suppressed) snd_pcm_avail after recover: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting address fded:dbef:cb40:0:dad0:90ff:fe5e:d2de/64
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting route to fded:dbef:cb40::/64
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockc: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting route to fded:dbef:cb40::/48 via fe80::82cc:9cff:feea:5f4b
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockc: (0 suppressed) snd_pcm_avail after recover: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting address fe80::dad0:90ff:fe5e:d2de
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting route to 10.0.0.0/23
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: (0 suppressed) snd_pcm_avail after recover: Broken pipe
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: deleting default route via 10.0.0.1
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium dhcpcd[1700]: enp195s0f3u1u4: removing interface
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium systemd[1]: Starting Autorandr execution hook...
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire-pulse[4324]: spa.loop: 0x7fe700000b70: queue full 64, need 160 (0 suppressed)
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire-pulse[4324]: spa.loop: 0x7fe700008cf0: queue full 64, need 160 (0 suppressed)
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire-pulse[4324]: spa.loop: 0x7fe700010d60: queue full 64, need 160 (0 suppressed)
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: Broken pipe
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_start: File descriptor in bad state
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: snd_pcm_drop: No such device
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dock,1p: close failed: No such device
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: snd_pcm_drop: No such device
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockp: close failed: No such device
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockc: snd_pcm_drop: No such device
Jan 15 07:57:02 vanadium pipewire[2408]: spa.alsa: hw:Dockc: close failed: No such device
... elided

Are there anything else I can try ?

dimitris · January 16, 2025, 4:12am

I don’t have any specific ideas unfortunately. Since whatever device/driver seems to be the trigger for this seems to be hanging off USB, you could try powering down that USB device/port before undocking. This is a diagnostic rather than a solution of course. If you can make the problem disappear this way, consider opening a bug either with NixOs or on the upstream kernel bugzilla.

Leana_CHIANG · January 16, 2025, 6:39pm

Thank you for your reply. I noticed that there were a lot of alsa related errors. I disabled alsa support from pipewire, I think it’s related to pipewire.

I’ll see if the problem persists, thanks

Topic		Replies	Views
Failing to wake from suspend Linux nixos	8	601	April 30, 2024
Framework NixOS (Linux) users self-help (Firmware/Fingerprint discussion) Linux nixos	23	3968	October 5, 2024
[SOLVED] Framework 16 cannot Hibernate, Shutdown, or Reboot under NixOS Linux nixos	4	1315	June 19, 2024
[SOLVED] FW16 Not powering down Linux nixos	4	806	June 16, 2024
[TRACKING] Cannot resume from suspend on AMD Linux	55	5921	January 4, 2025

Suspending leads to complete shutdown

Related topics