Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74605 - [linux] External sound card broken with Linxu 5.17.4+

Attached to Project: Arch Linux
Opened by Peter (protake) - Sunday, 01 May 2022, 10:50 GMT
Last edited by Toolybird (Toolybird) - Thursday, 14 September 2023, 07:10 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I'm using a FiiO USB DAC-E10 and it doesn't work with Linux 5.17.4 and 5.17.5. Downgrading my kernel to 5.17.3 makes the issue go away.

fuser:

USER PID ACCESS COMMAND
/dev/snd/controlC0: sf 1397 F.... pulseaudio
/dev/snd/controlC1: sf 1397 F.... pulseaudio
/dev/snd/controlC2: sf 1397 F.... pulseaudio
/dev/snd/controlC3: sf 1397 F.... pulseaudio
/dev/snd/pcmC3D0p: sf 1397 F...m pulseaudio

dmesg:

[ 16.436193] snd_hda_intel 0000:07:00.1: Handle vga_switcheroo audio client
[ 16.436195] snd_hda_intel 0000:07:00.1: Force to non-snoop mode
[ 16.436380] snd_hda_intel 0000:09:00.4: enabling device (0000 -> 0002)
[ 16.529966] snd_hda_intel 0000:07:00.1: bound 0000:07:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 16.543872] snd_hda_codec_realtek hdaudioC2D0: ALCS1200A: SKU not ready 0x00000000
[ 16.544225] snd_hda_codec_realtek hdaudioC2D0: autoconfig for ALCS1200A: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 16.544228] snd_hda_codec_realtek hdaudioC2D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 16.544230] snd_hda_codec_realtek hdaudioC2D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 16.544231] snd_hda_codec_realtek hdaudioC2D0: mono: mono_out=0x0
[ 16.544233] snd_hda_codec_realtek hdaudioC2D0: inputs:
[ 16.544234] snd_hda_codec_realtek hdaudioC2D0: Front Mic=0x19
[ 16.544235] snd_hda_codec_realtek hdaudioC2D0: Rear Mic=0x18
[ 16.544236] snd_hda_codec_realtek hdaudioC2D0: Line=0x1a
[ 16.859803] usbcore: registered new interface driver snd-usb-audio

aplay:

**** List of PLAYBACK Hardware Devices ****
card 0: E205U [Superlux E205U], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALCS1200A Analog [ALCS1200A Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: DACE10 [FiiO USB DAC-E10], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

(however, those logs are identical on a broken/not broken system)

Steps to reproduce:
It's a rather strange issue. Sound might work for a moment, but as soon as I start multiple apps using sound, it stops working. Videos in Firefox don't even play anymore.
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 14 September 2023, 07:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  Clearly not an Arch packaging issue. If still happening with latest kernels, please report it upstream to the kernel folks.
Comment by Peter (protake) - Sunday, 01 May 2022, 10:59 GMT
I just remembered my modified PA config and changing the resample method back from "soxr-vhq" to "speex" makes it work again.
Still definitely an issue in the kernel somewhere. I realize you guys can't do much about it either, though.
Comment by David Thurstenson (thurstylark) - Sunday, 01 May 2022, 13:59 GMT
Seeing as kernel version 4.17 is from 2018, do you happen to mean 5.17 instead?
Comment by Peter (protake) - Sunday, 01 May 2022, 14:05 GMT
Oh yeah, of course, sorry.
Comment by David Thurstenson (thurstylark) - Sunday, 01 May 2022, 14:10 GMT
No problem, I'll make the necessary edits :)

Loading...