From: Andreas Kempf <aakempf@gmail.com>
To: Oliver Neukum <oneukum@suse.com>, linux-usb@vger.kernel.org
Subject: Re: Slow enumeration of Creative Sound Blaster G3
Date: Mon, 13 Nov 2023 20:02:25 +0100 [thread overview]
Message-ID: <ZVJywfuXwJu7asbQ@ryzen7700x.fritz.box> (raw)
In-Reply-To: <f85ecc36-8e05-4595-8baa-5f4b48afc8df@suse.com>
>> On Sat, Nov 11, 2023 at 05:58:08PM +0100, Andreas Kempf wrote:
>>> Hi,
>>>
>>> I apologize if this is the wrong mailing list but my investigation
>>> led me to the USB subsystem and I do not know how to proceed.
>>>
>>> My system:
>>> Arch Linux
>>> Linux kernel 6.6.1 (-arch1-1)
>>> Motherboard: ASRock X670E PG Lightning
>>> Device: Creative Sound Blaster G3
>>>
>>> I have a Creative Technology Sound Blaster G3 USB sound device that
>>> seems to work perfectly on Windows. It used to work just fine on Linux,
>>> as well. However, at some point a few weeks ago, it started behaving
>>> oddly. Unfortunately, I cannot pinpoint exactly when the problems
>>> started happening because the symptoms did not immediately point me
>>> toward the device and I did not immediately figure out what was going
>>> on as I only noticed hangs when shutting down the system.
>>
>> Did you update your kernel between the time when the device was
>> working okay and now?
>
>If this is a regression the obvious suspect would be
>
>5fadc941d07530d681f3b7ec91e56d8445bc3825
>("ALSA: usb-audio: Fix init call orders for UAC1")
>
>I'd suggest you try reverting that.
Thank you for the suggestion. I figure that this commit made it into
6.1.52. Arch packaged 6.1.51, so I downgraded to that and then again to
6.1.12. Both showed the issue. Somehow, the kernel version does not seem
to matter. I am baffled by the whole thing as no other piece of software
should be involved here, as far a I can understand.
It could be some kind of hardware issue (Motherboard/Device) or an
extremely weird race condition that I somehow hit all of a sudden.
(I seem to have messed up my initial mutt setup for the mailing list, so
I hope this reply does not completely break the thread)
>
> Regards
> Oliver
Best regards,
Andreas
next prev parent reply other threads:[~2023-11-13 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 16:58 Slow enumeration of Creative Sound Blaster G3 Andreas Kempf
2023-11-11 19:56 ` Alan Stern
2023-11-13 11:40 ` Oliver Neukum
2023-11-13 19:02 ` Andreas Kempf [this message]
[not found] <e478e2c3-cc43-492a-989f-21bce674b1b8@rowland.harvard.edu>
2023-11-12 11:03 ` Andreas Kempf
2023-11-12 16:28 ` Alan Stern
2023-11-13 18:23 ` Alan Stern
2023-11-13 19:19 ` Andreas Kempf
2023-11-13 19:16 ` Andreas Kempf
2023-11-13 20:58 ` Alan Stern
2023-11-21 17:58 ` Andreas Kempf
2023-11-21 20:59 ` Alan Stern
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=ZVJywfuXwJu7asbQ@ryzen7700x.fritz.box \
--to=aakempf@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@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