Audio across system is shut down when most applications are launched

Hello, for a few days now on kernels 6.10.9-zen1-1 and 6.10.9-zen1-2, there is an issue on my system where if I launch most applications, all audio sinks for my system vanish, causing my speakers to emit a loud screech, and then shortly later audio is returned but needs to be configured if the system doesn’t auto-default back to the correct settings for the audio sink.

Before continuing, garuda-inxi:

System:
  Kernel: 6.10.9-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=d04bc699-4389-4e74-8fe2-fc7b2354f103 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A info: frameworks v: 6.5.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 3602 date: 03/05/2021
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201009
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3999 high: 4000 min/max: 2200/5352 boost: disabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 4000 2: 4000
    3: 3999 4: 4000 5: 4000 6: 4000 7: 4000 8: 4000 9: 4000 10: 4000 11: 4000
    12: 3998 13: 4000 14: 4000 15: 4000 16: 4000 17: 4000 18: 4000 19: 4000
    20: 4000 21: 4000 22: 4000 23: 4000 24: 4000 bogomips: 191984
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: XFX RX-79XMERCB9 driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
    process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-1,DP-2 empty: DP-3,HDMI-A-1,Writeback-1 bus-ID: 0d:00.0
    chip-ID: 1002:744c class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 4-4:2 chip-ID: 046d:085e
    class-ID: 0300 serial: <filter>
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1354x381mm (53.31x15.00")
    s-diag: 1407mm (55.38")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
    model: Gigabyte G32QC serial: <filter> built: 2020 res: 2560x1440 dpi: 93
    gamma: 1.2 size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9
    modes: max: 2560x1440 min: 640x480
  Monitor-2: DP-2 mapped: DisplayPort-1 pos: right model: Gigabyte G32QC
    serial: <filter> built: 2020 res: 2560x1440 dpi: 93 gamma: 1.2
    size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 18.1.8 DRM 3.57 6.10.9-zen1-2-zen) device-ID: 1002:744c
    memory: 23.44 GiB unified: no
  API: Vulkan v: 1.3.295 layers: 18 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 XTX (RADV NAVI31) driver: mesa radv v: 24.2.2-arch1.1
    device-ID: 1002:744c surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.2-arch1.1 (LLVM
    18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.1 chip-ID: 1002:ab30
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Focusrite-Novation Focusrite Scarlett 2i2 driver: snd-usb-audio
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:2
    chip-ID: 1235:8016 class-ID: fe01
  Device-4: Logitech BRIO Ultra HD Webcam
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 4-4:2 chip-ID: 046d:085e
    class-ID: 0300 serial: <filter>
  Device-5: Valve VR Radio driver: cdc_acm,hid-generic,usbhid type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-3.3.2:6
    chip-ID: 28de:2102 class-ID: 0a00 serial: <filter>
  Device-6: Valve VR Radio & HMD Mic
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 7-3.3.3:7 chip-ID: 28de:2102 class-ID: 0102
    serial: <filter>
  API: ALSA v: k6.10.9-zen1-2-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: httpd, NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:4 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
    status: discoverable: no pairing: no
Drives:
  Local Storage: total: 9.1 TiB used: 1.69 TiB (18.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Reletech
    model: P400 M.2 Pro Q2000GB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EGFM52.3 temp: 50.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: Expansion Desk
    size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 9401 scheme: GPT
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 468.96 GiB (25.2%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 468.96 GiB (25.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 468.96 GiB (25.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 468.96 GiB (25.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.24 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 39.0 C mobo: 31.0 C gpu: amdgpu temp: 45.0 C
    mem: 55.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB available: 31.24 GiB used: 6.44 GiB (20.6%)
  Processes: 445 Power: uptime: 7m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2091 libs: 575 tools: octopi,paru Compilers:
    clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
    running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-05-05
  Last full system update: 2024-09-11
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:            

Details of problem:
During system runtime at any point, if an application that was not already running before the current wireplumber/pipewire instance was running, the system appears to cause the audio service overall to crash/be terminated, emit a screech, then shortly later audio services are rebooted.

Example A)
I am in a call on Discord with a friend and we go to play Overwatch or Satisfactory, the audio gets cut out, a screech is emitted, Discord hangs, and the application loads. To get sound I must reconfigure my audio sink after it reappears. To fix Discord from it’s frozen state (audio stops, visuals stops, does not fade to show it hung), I must simply reboot it, then it’s working fine and outputting it.

Example B)
I go to watch a video on Youtube in the FireDragon browser, it plays fine. While that is still playing, I open Steam which does not cause the audio to break as described. I then launch any game where the audio now gets shuts down, a screech is emitted, the video buffers until the audio sink returns. If the game has a launcher like Minecraft, Stellaris, Star Citizen, or Wizard101; the audio will become terminated as described for both the launcher and for the game when it too gets launched. In this case, games from launchers are stuck in perma-silent from my testing even once audio is restored.

I am able to restart the user services for pipewire, pipewire-pulse, and wireplumber, all using the command systemctl --user restart <service> but doing this does not resolve the audio being shut down later on if another application triggers it to terminate for whatever reason.

For the screech, I have found it very much is just the sound my speakers make when they become suspended or such. This used to be heard during normal runtime in the past if I did not follow the steps on the following Arch wiki page category to stop the speakers from entering a power saving state: https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback. As of this issue, this 1) doesn’t seem to be needed (right now), but 2) the speakers enter power_saving/suspension from the current problem.

When I check log entries for pipewire, pipewire-pulse, and wireplumber, I can see various points where the systems are shutting down and start in relation to me opening software like OBS or Overwatch, but the cause to me doesn’t feel related to them initially. For example in the wireplumber link for it’s journalctl entry, you can find that there are parts where wireplumber is stating “stopped by signal: Terminated”, which makes me think something outside wireplumber/pipewire that is causing this issue here. The journalctl entries for each of those can be viewed in the following:
pipewire: gist:c886b659327405a5575eba3b1abee87e · GitHub
pipewire-pulse: gist:c6aa6bdaffc918b4c8a7fc3c193c4bd3 · GitHub
wireplumber: gist:ade44030182d72ee972aee01e7e6bebf · GitHub
overall, generic: gist:f673dfdb1ad247a58790be2e832d9293 · GitHub

I am still trying to figure out how to find what might be sending a SIGTERM to wireplumber but I’m not fully versed yet with debugging completely still.

I should also add that this issue was not able to be fixed by rolling back to a previous point via Snapper that I had from about 10 days ago before updating initially 3 days ago. For whatever reason, when I went back to a restore point prior to the garuda-update I did that took me to kernel 6.10.9-zen1-1 initially, the issue persisted on that restore point after rebooting despite it not being a thing back then in time. So as of writing this I am now on 6.10.9-zen1-2 with the issue still present and thus wondering on how I can further debug the problem at hand to eventually find a resolution for it.

If there’s other details needed, I can certainly provide them once I’m aware to what is being inquired. In the meantime, thanks in advance!

1 Like

First, I would update your BIOS to the latest version. v 3603 states that it fixed a USB connectivity issue which might explain some of your I/O errors in your logs. Later versions also note improvements to system compatibility and stability (among other things like security fixes of course).

If that doesn’t fix it itself, I would also test the LTS kernel and see if you still are getting similar errors.

4 Likes

Howdy Kayo, thank you for your reply! I went ahead and did both of what you suggested; despite neither leading to an immediate solution, some steps I tried afterward appear to have solved the issue.

Given that it seems to not be kernel related after testing it in the linux-lts kernel, I went to start checking packages on an individual level:

  • I replaced wireplumber with pipewire-media-session, which of course is depreciated, to test if it was the session manager at fault. When I followed the steps to trigger the issue, the same outcome continued with no deviation thus marking it wasn’t related to wireplumber to begin with.
  • I upped the logging levels for pipewire which to my unsatisfaction still wasn’t giving any immediate “ah-ha” moments for me. So it made me wonder if something was wrong directly with pipewire itself. To test that, I went and reinstalled it using the typical sudo pacman -S pipewire then rebooted. Upon doing this, the issue, just as magically as it appeared, appears to be fixed.

After getting it to work with no issues in linux-lts I switched back to zen and all is fine again with no problem. Guess there was just a small hiccup after updating. I feel silly after running around checking logs and whatever else I could find; all while not even thinking to try testing individual packages to see when the behavior starts to change. Trial and error I suppose, exhaust all options one at a time. Anywho with the fix, however mundane it ended up being, I thank you for your time and suggestions, definitely needed to update the bios in due time anyway, was a good time to do just that.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.