Bug 218823

Summary: Garbled sound at start of a playback after some inactivity on said channel with DP/HDMI on RDNA devices
Product: Drivers Reporter: Mete (yurnerolinux)
Component: Sound(ALSA)Assignee: Jaroslav Kysela (perex)
Status: NEW ---    
Severity: normal CC: tiwai
Priority: P3    
Hardware: All   
OS: Linux   
Kernel Version: Subsystem:
Regression: No Bisected commit-id:

Description Mete 2024-05-09 10:54:39 UTC 
As it is written like there, when said channels wakes up from a suspend state (inactivity) issue occurs as described. While i've applied noted workaround in there as a temp solution now, Nvidia gpus doesn't seem to suffer from it so that makes it a hw specific issue.


https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3953

Basic system info:


  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: Sapphire PULSE driver: amdgpu v: kernel arch: RDNA-3 bus-ID: 03:00.0
  Device-2: AMD Raphael vendor: Gigabyte driver: amdgpu v: kernel
    arch: RDNA-2 bus-ID: 12:00.0 temp: 39.0 C
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu,amdgpu
    resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
    navi31 LLVM 17.0.6 DRM 3.57 6.8.9-arch1-2)
  API: Vulkan v: 1.3.279 drivers: radv surfaces: xcb,xlib,wayland devices: 2
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 03:00.1
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 12:00.1
  Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 12:00.6
  API: ALSA v: k6.8.9-arch1-2 status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active
Comment 1 Takashi Iwai 2024-05-14 07:17:40 UTC 
It's hard to diagnose, unfortunately, as it could be rather an issue of the graphics driver, too.

You can try to isolate the issue whether it's the code flow that happens only in the HD-audio driver code (i.e. only the HD-audio runtime PM matters) or it influences on the amdgpu side, by checking the debug prints or such.
Comment 2 Mete 2024-09-15 22:53:42 UTC 
(In reply to Takashi Iwai from comment #1)
> It's hard to diagnose, unfortunately, as it could be rather an issue of the
> graphics driver, too.
> 
> You can try to isolate the issue whether it's the code flow that happens
> only in the HD-audio driver code (i.e. only the HD-audio runtime PM matters)
> or it influences on the amdgpu side, by checking the debug prints or such.

What kind of output can i provide for this?