From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6
Date: Wed, 01 Apr 2020 16:00:44 +0000 [thread overview]
Message-ID: <bug-203419-208809-FazjE3AIZJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203419-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #19 from Alan Stern (stern@rowland.harvard.edu) ---
Mathias, maybe you should look at this.
On Wed, 1 Apr 2020 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203419
>
> Takashi Iwai (tiwai@suse.de) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Component|Sound(ALSA) |USB
> Assignee|perex@perex.cz |drivers_usb@kernel-bugs.ker
> | |nel.org
>
> --- Comment #18 from Takashi Iwai (tiwai@suse.de) ---
> Sounds more like a USB issue. Reassigned.
In the bug report, Florian Meyer tentatively identified commit
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer") as the one causing the
problem. No one else has verified this, however -- and as far as I can
see, even Florian hasn't tried starting from that commit and reverting
it.
Alan Stern
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-01 16:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203419-208809@https.bugzilla.kernel.org/>
2020-04-01 13:10 ` [Bug 203419] Logitech Group USB audio stopped working in 5.1-rc6 bugzilla-daemon
2020-04-01 16:00 ` Alan Stern
2020-04-01 16:00 ` bugzilla-daemon [this message]
2020-04-01 19:22 ` bugzilla-daemon
2020-04-02 13:34 ` bugzilla-daemon
2020-04-08 9:43 ` bugzilla-daemon
2020-04-08 10:00 ` bugzilla-daemon
2020-04-08 10:04 ` bugzilla-daemon
2020-04-08 12:49 ` bugzilla-daemon
2020-04-08 16:30 ` bugzilla-daemon
2020-04-09 12:39 ` bugzilla-daemon
2020-04-10 18:04 ` bugzilla-daemon
2020-07-02 14:13 ` bugzilla-daemon
2020-07-02 14:15 ` bugzilla-daemon
2020-07-02 19:10 ` bugzilla-daemon
2020-07-03 11:23 ` bugzilla-daemon
2020-07-09 9:22 ` bugzilla-daemon
2020-08-31 7:55 ` bugzilla-daemon
2020-08-31 7:56 ` bugzilla-daemon
2020-08-31 7:57 ` bugzilla-daemon
2020-09-01 6:55 ` bugzilla-daemon
2020-09-02 6:05 ` bugzilla-daemon
2020-09-02 11:34 ` bugzilla-daemon
2020-09-03 9:52 ` bugzilla-daemon
2020-09-04 12:29 ` bugzilla-daemon
2020-09-10 14:25 ` bugzilla-daemon
2020-10-06 14:22 ` bugzilla-daemon
2020-10-12 12:37 ` bugzilla-daemon
2020-12-01 4:27 ` bugzilla-daemon
2022-10-31 14:29 ` bugzilla-daemon
2022-10-31 15:15 ` bugzilla-daemon
2022-10-31 17:09 ` bugzilla-daemon
2022-10-31 19:11 ` bugzilla-daemon
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=bug-203419-208809-FazjE3AIZJ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.