Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Will Bush" <will@willbush.dev>
Cc: "Takashi Iwai" <tiwai@suse.de>, "Takashi Iwai" <tiwai@suse.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	linux-sound@vger.kernel.org, regressions@lists.linux.dev,
	stable@vger.kernel.org, "Jan Lentfer" <jan.lentfer@web.de>,
	"Sebastian Dalfuß" <sd@sedf.de>
Subject: Re: [REGRESSION] usb-audio: Behringer UMC204HD broken in 7.2.10
Date: Mon, 19 Oct 2026 11:23:48 +0200	[thread overview]
Message-ID: <87a4oaavrv.wl-tiwai@suse.de> (raw)
In-Reply-To: <bb9cad8e-48fc-4cc7-a893-1542270f2018@app.fastmail.com>

On Mon, 19 Oct 2026 10:39:46 +0200,
Will Bush wrote:
> 
> On Sun, Oct 18, 2026, at 11:42 AM, Takashi Iwai wrote:
> > Interesting, it's just a descriptor read and this fails on your device
> > by some reason.  Could you try to ignore the error like below, and
> > verify whether it continues to work?
> 
> Thanks for the quick reply. I reverted my patch and applied yours. Device keeps
> disconnecting and reconnecting (just more slowly). It never ends up working.
> 
>   ❯ journalctl -k -b -0 -o short-monotonic | grep -E 'usb 3-4|snd-usb-audio 3-4'
>   [    2.264012] blazar kernel: usb 3-4: new high-speed USB device number 3 using xhci_hcd
>   [    2.458009] blazar kernel: usb 3-4: New USB device found, idVendor=1397, idProduct=0508, bcdDevice= 1.35
>   [    2.484013] blazar kernel: usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>   [    2.484035] blazar kernel: usb 3-4: Product: UMC204HD 192k
>   [    2.484050] blazar kernel: usb 3-4: Manufacturer: BEHRINGER
>   [   12.976010] blazar kernel: usb 3-4: USB disconnect, device number 3
>   [   18.012013] blazar kernel: usb 3-4: failed to read device descriptor: -110
>   [   18.012623] blazar kernel: usb 3-4: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 41)
>   [   18.012768] blazar kernel: usb 3-4: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 41)
>   [   18.012903] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 1 (-19)
>   [   18.013047] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 2 (-19)
>   [   18.013181] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 3 (-19)
>   [   18.013309] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 4 (-19)
>   [   18.013434] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 0 (-19)
>   [   18.013565] blazar kernel: usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
>   [   18.013690] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [   18.013822] blazar kernel: usb 3-4: [10] FU [PCM Playback Volume] ch = 4, val = 0/1/1
>   [   18.013959] blazar kernel: usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
>   [   18.014102] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [   18.014239] blazar kernel: usb 3-4: [10] FU [PCM Playback Volume] ch = 1, val = 0/1/1
>   [   18.014374] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 1 (-19)
>   [   18.014508] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 2 (-19)
>   [   18.014635] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 0 (-19)
>   [   18.014763] blazar kernel: usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
>   [   18.014890] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [   18.015021] blazar kernel: usb 3-4: [11] FU [Mic Capture Volume] ch = 2, val = 0/1/1
>   [   18.015151] blazar kernel: usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
>   [   18.015278] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [   18.015408] blazar kernel: usb 3-4: [11] FU [Mic Capture Volume] ch = 1, val = 0/1/1
>   [   18.300040] blazar kernel: usb 3-4: new high-speed USB device number 6 using xhci_hcd
>   [   18.491087] blazar kernel: usb 3-4: New USB device found, idVendor=1397, idProduct=0508, bcdDevice= 1.35
>   [   18.517036] blazar kernel: usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>   [   18.517242] blazar kernel: usb 3-4: Product: UMC204HD 192k
>   [   18.517398] blazar kernel: usb 3-4: Manufacturer: BEHRINGER
>   [   23.644013] blazar kernel: usb 3-4: failed to read device descriptor: -110
>   [   33.884021] blazar kernel: usb 3-4: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 41)
>   [   49.244015] blazar kernel: usb 3-4: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 41)
>   [   59.484034] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 1 (-110)
>   [   69.725032] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 2 (-110)
>   [   79.965020] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 3 (-110)
>   [   90.204027] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 4 (-110)
>   [  100.444027] blazar kernel: usb 3-4: 10:0: failed to get current value for ch 0 (-110)
>   [  110.684056] blazar kernel: usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
>   [  110.684281] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [  110.684397] blazar kernel: usb 3-4: [10] FU [PCM Playback Volume] ch = 4, val = 0/1/1
>   [  115.804025] blazar kernel: usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
>   [  115.812386] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [  115.812521] blazar kernel: usb 3-4: [10] FU [PCM Playback Volume] ch = 1, val = 0/1/1
>   [  131.164026] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 1 (-110)
>   [  141.404011] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 2 (-110)
>   [  151.644020] blazar kernel: usb 3-4: 11:0: failed to get current value for ch 0 (-110)
>   [  161.885033] blazar kernel: usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
>   [  161.885326] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [  161.885446] blazar kernel: usb 3-4: [11] FU [Mic Capture Volume] ch = 2, val = 0/1/1
>   [  167.004009] blazar kernel: usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
>   [  167.004224] blazar kernel: usb 3-4: Warning! Unlikely small volume range (=1), linear volume or custom curve?
>   [  167.004341] blazar kernel: usb 3-4: [11] FU [Mic Capture Volume] ch = 1, val = 0/1/1
>   [  167.005012] blazar kernel: usb 3-4: Quirk or no altset; falling back to MIDI 1.0
>   [  187.486013] blazar kernel: usb 3-4: USB disconnect, device number 6
>   [  187.785034] blazar kernel: usb 3-4: new high-speed USB device number 7 using xhci_hcd
>   ...
>   [ 1035.327013] blazar kernel: usb 3-4: New USB device found, idVendor=1397, idProduct=0508, bcdDevice= 1.35
>   [ 1035.353013] blazar kernel: usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>   [ 1035.353185] blazar kernel: usb 3-4: Product: UMC204HD 192k
>   [ 1035.353301] blazar kernel: usb 3-4: Manufacturer: BEHRINGER
>   [ 1040.476017] blazar kernel: usb 3-4: failed to read device descriptor: -110
>   [ 1050.717019] blazar kernel: usb 3-4: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 41)
>   ...

OK, thanks.  Then the only way to introduce some deny list.
Below is a quick fix.  I'm going to submit & merge this later.


thanks,

Takashi

-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: usb-audio: Avoid applying boot quirk for Behringer
 UMC204HD

Will reported that the recent boot quirk for Behringer devices broke
his UMC204HD (1397:0508).  The quirk was to just run
usb_get_descriptor(), so I expected it rather harmful, but in this
case, it doesn't look so.

As a quick workaround, skip the quirk for UMC204HD.

Fixes: b5c4823cf3e4 ("ALSA: usb-audio: Apply boot quirk for Behringer models generically")
Reported-by: Will Bush <will@willbush.dev>
Closes: https://lore.kernel.org/45162613-2802-401c-84c9-742f9c8c68e6@app.fastmail.com
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
 sound/usb/quirks.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index 4fadb1fdcdea..0dd06cc2c854 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -1790,8 +1790,14 @@ int snd_usb_apply_boot_quirk_once(struct usb_device *dev,
 	}
 
 	/* Behringer devices may need explicit device descriptor read at boot */
-	if (USB_ID_VENDOR(id) == 0x1397)
+	if (USB_ID_VENDOR(id) == 0x1397) {
+		/* the quirk seems breaking on some Behringer devices */
+		switch (id) {
+		case USB_ID(0x1397, 0x0508): /* UMC204HD */
+			return 0;
+		}
 		return snd_usb_cm1a_boot_quirk(dev);
+	}
 
 	return 0;
 }
-- 
2.55.0



  reply	other threads:[~2026-10-19  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 16:34 [REGRESSION] usb-audio: Behringer UMC204HD broken in 7.2.10 Will Bush
2026-10-18 16:42 ` Takashi Iwai
2026-10-19  8:39   ` Will Bush
2026-10-19  9:23     ` Takashi Iwai [this message]
2026-10-19 10:23       ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a4oaavrv.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=jan.lentfer@web.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --cc=sd@sedf.de \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=will@willbush.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox