From: Takashi Iwai <tiwai@suse.de>
To: London grad <londongrad@gmail.com>
Cc: clemens@ladisch.de, linux-sound@vger.kernel.org, tiwai@suse.com,
perex@perex.cz, Xiang Mei <xmei5@asu.edu>,
co+24304d323d28f156@bugs.sh, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: ua101: reject mismatched capture/playback packet sizes
Date: Thu, 12 Nov 2026 13:37:51 +0100 [thread overview]
Message-ID: <87ld6yrzs0.wl-tiwai@suse.de> (raw)
In-Reply-To: <CANd6Td+b6ituLFzkhvX09vricCY541fQapNOk3rTa=74zWA5LA@mail.gmail.com>
On Thu, 12 Nov 2026 10:25:39 +0100,
London grad wrote:
> Hello all
>
> This patch may have broken ua-101?
>
> Kernel 6.8.0-146 still works for me
>
> In kernel 6.8.0-149 my UA-1000 fails with
>
> `snd-ua101` rejects the device during probe at every physical sample rate
> setting (44.1, 48, 88.2, and 96 kHz), leaving the interface unregistered in
> ALSA.
>
> ### Relevant `dmesg` Output
> [ 2622.796887] usb 3-3: new high-speed USB device number 5 using xhci_hcd
> [ 2622.928793] usb 3-3: New USB device found, idVendor=0582, idProduct=0044,
> bcdDevice= 1.07
> [ 2622.928798] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber
> =3
> [ 2622.928800] usb 3-3: Product: UA-1000
> [ 2622.928801] usb 3-3: Manufacturer: EDIROL
> [ 2622.928802] usb 3-3: SerialNumber: ZT02743
> [ 2622.934792] usb 3-3: playback packet size 560 too small for 15 capture
> frames
>
> Submitted bug report here
> https://bugzilla.kernel.org/show_bug.cgi?id=222261
Could you verify that just reverting the commit fixes your problem?
It's quite possible that this patch is the cause, but just to be sure.
thanks,
Takashi
next parent reply other threads:[~2026-11-12 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANd6Td+b6ituLFzkhvX09vricCY541fQapNOk3rTa=74zWA5LA@mail.gmail.com>
2026-11-12 12:37 ` Takashi Iwai [this message]
2026-11-12 12:55 ` [PATCH] ALSA: ua101: reject mismatched capture/playback packet sizes London grad
2026-09-18 22:57 Xiang Mei
2026-09-28 11:10 ` 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=87ld6yrzs0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=co+24304d323d28f156@bugs.sh \
--cc=linux-sound@vger.kernel.org \
--cc=londongrad@gmail.com \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=xmei5@asu.edu \
/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