From: Takashi Iwai <tiwai@suse.de>
To: Michael Ralston <michael@ralston.id.au>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
alsa-devel@alsa-project.org, regressions@lists.linux.dev,
stable@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: USB-Audio regression on behringer UMC404HD
Date: Tue, 03 Jan 2023 16:13:10 +0100 [thread overview]
Message-ID: <87bknfr6rd.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAC2975+cUqiFC0LO-D-fi0swH+x=_FMuG+==mhg6HH4pc_YDRA@mail.gmail.com>
On Tue, 03 Jan 2023 16:05:18 +0100,
Michael Ralston wrote:
>
> On Wed, 4 Jan 2023 at 00:38, Takashi Iwai <tiwai@suse.de> wrote:
> >
> > Thanks; that's helpful.
> >
> > Could you try to revert the commit
> > 9902b303b5ade208b58f0dd38a09831813582211
> > ALSA: usb-audio: Avoid unnecessary interface change at EP close
> as a blind shot?
> >
> > Also, there has been a series of fixes for other issues, and it might
> > be worth to try as well:
> > https://lore.kernel.org/r/20230102170759.29610-1-tiwai@suse.de
> >
>
> I built 3 kernels: one with the reverted commit, one with the patches
> you linked, and one with both. These builds were based on 6.1.2.
>
> None of them worked. Also, even though I continued to boot with
> snd_usb_audio.dyndbg=+p, none of the kernel logs showed the debug
> messages that the other versions did. I'm baffled why this is.
That's weird. Is snd_usb_audio driver bound with the device at all?
That is, does it appear in /proc/asound/cards?
Takashi
next prev parent reply other threads:[~2023-01-03 15:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 17:29 USB-Audio regression on behringer UMC404HD Michael Ralston
2023-01-02 17:43 ` Michael Ralston
2023-01-03 9:07 ` Thorsten Leemhuis
2023-01-03 9:33 ` Takashi Iwai
2023-01-03 13:10 ` Michael Ralston
2023-01-03 13:38 ` Takashi Iwai
2023-01-03 15:05 ` Michael Ralston
2023-01-03 15:13 ` Takashi Iwai [this message]
2023-01-03 15:14 ` Michael Ralston
2023-01-03 15:19 ` Michael Ralston
2023-01-03 15:21 ` Takashi Iwai
2023-01-03 15:31 ` Michael Ralston
2023-01-03 16:03 ` Takashi Iwai
2023-01-03 19:09 ` Michael Ralston
2023-01-03 19:24 ` Michael Ralston
2023-01-03 19:27 ` Michael Ralston
2023-01-03 19:29 ` Michael Ralston
2023-01-04 8:16 ` Takashi Iwai
2023-01-04 14:22 ` Michael Ralston
2023-01-04 14:42 ` Takashi Iwai
2023-01-04 14:47 ` Michael Ralston
2023-01-04 14:54 ` Takashi Iwai
2023-01-04 14:56 ` Michael Ralston
2023-01-04 15:17 ` 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=87bknfr6rd.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=michael@ralston.id.au \
--cc=perex@perex.cz \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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