Logitech Group USB audio stopped working in 5.1-rc6
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Takashi Iwai ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Sound(ALSA) |USB
Assignee|[email protected] |[email protected]
| |nel.org--- Comment #18 from Takashi Iwai ([email protected]) --- Sounds more like a USB issue. Reassigned.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
Mathias, maybe you should look at this.
Quoted 4 lines · On Wed, 1 Apr 2020 [email protected] wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Takashi Iwai ([email protected]) changed:
Quoted 8 lines
What |Removed |Added
----------------------------------------------------------------------------Component|Sound(ALSA) |USB Assignee|[email protected] |[email protected] | |nel.org--- Comment #18 from Takashi Iwai ([email protected]) --- 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
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #19 from Alan Stern ([email protected]) --- Mathias, maybe you should look at this.
Quoted 4 lines · On Wed, 1 Apr 2020 [email protected] wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Takashi Iwai ([email protected]) changed:
Quoted 8 lines
What |Removed |Added
----------------------------------------------------------------------------Component|Sound(ALSA) |USB Assignee|[email protected] |[email protected] | |nel.org--- Comment #18 from Takashi Iwai ([email protected]) --- 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
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #20 from Florian Meyer ([email protected]) ---
I get my sound system working if I use the version at the commit directly before ef513be0a905.
I just don't know if my bug is the same as the one originally reported here. The error messages are the same and the problem is the same, but the commit was applied during the 5.2 developement I think? Which would not fit the versions given in the first messages here.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Mathias Nyman ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] | |om
--- Comment #21 from Mathias Nyman ([email protected]) --- Any chance someone who could reproduce this on 5.1-rc6, 5.1 or 5.0 could bisect the kernel and find the problematic commit.
Also traces and logs with more usb details enabled could be useful. These can be taken with any recent kernel.
mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable < connect the logitec device >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Vincenzo Di Massa ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #22 from Vincenzo Di Massa ([email protected]) --- Hello all,
I don't have the HW to test, but I noticed that probably this bug is similar to bug 206897, which has been bisected to the same commit.
I have the HUION device and I could help until the end of the week (pandemic == no job for me :-( )
I can build, install and develop kernel code, but i don't know about USB internals.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #23 from Glen Ogilvie ([email protected]) --- (In reply to Mathias Nyman from comment #21)
Quoted 2 lines
Any chance someone who could reproduce this on 5.1-rc6, 5.1 or 5.0 could bisect the kernel and find the problematic commit.
I am happy to do this when back at work where the device is, but currently we are in lockdown in New Zealand.. so may not be for a month or more.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #24 from Florian Meyer ([email protected]) ---
I've also opened a new issue for the "same" problem that started appearing from 5.2 onwards for me.
https://bugzilla.kernel.org/show_bug.cgi?id=207065
I've posted the logs Mathias requested there.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #25 from Vincenzo Di Massa ([email protected]) --- Florian, ef513be0a9057cc6baf5d29566aaaefa214ba344 is not contained in the v5.2 kernel tag...
``` $ git tag --contains ef513be0a9057cc6baf5d29566aaaefa214ba344 | grep '^v5.[0-9]\+$' v5.3 v5.4 v5.5 v5.6 ```
do you mean that you were impacted by bug 207065 with kernels **after** v5.2 (i.e. v5.2 was the last good one)? For me 5.2.21 is unaffected.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #26 from Florian Meyer ([email protected]) ---
When building it, make menuconfig identified it as 5.2-rc3 which is why I thought it was part of 5.2. But yeah I think 5.3 was the first released version failing for me. Anyway, its definitely not part of 5.0 or 5.1, so the problem is different from the one discussed here.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #27 from Mathias Nyman ([email protected]) --- Created attachment 288295
--> https://bugzilla.kernel.org/attachment.cgi?id=288295&action=edit
testpatch that doesn't clear TT buffer after protocol STALL
Adding same patch and comment here as in bug #207065, it might help in this case as well.
"Traces show its related to Clearing TT buffer after a STALL on endpoint 0.
The first stall looks like a protocol stall, not a function stall, meaning that endpoint isn't really halted, just that the device does not support the request in the control transfer.
Anyway, xhci starts clearing what it assumes is a halted endpoint, including clearing the hub TT buffer.
Specs are a bit unclear if TT should be cleared in this case, or at least I couldn't find it."
Attached is a tespatch that doesn't clear TT buffer on protocol stalls, withexcessive tracing and debugging.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #28 from Vincenzo Di Massa ([email protected]) --- Applying the patches in bug 207065, comment 7 the problem reported in bug 206897 for HUION tablet is fixed. Looks promising :-)
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #30 from Mathias Nyman ([email protected]) --- (In reply to Marco S. from comment #29)
Quoted 2 lines
Hi, any news about it? when it's going to be implemented in stable kernel? Thanks
it's in 5.4.36 stable kernel:fceab238c534 xhci: Don't clear hub TT buffer on ep0 protocol stall
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #31 from Marco S. ([email protected]) --- (In reply to Mathias Nyman from comment #30)
Quoted 6 lines
(In reply to Marco S. from comment #29)
Quoted 2 lines
Hi, any news about it? when it's going to be implemented in stable kernel? Thanks
it's in 5.4.36 stable kernel:
fceab238c534xhci: Don't clear hub TT buffer on ep0 protocol stall
I'm running 5.7.6 and still have the issue with Logic Group USB
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #32 from Dominique Archambault ([email protected]) --- same here
$ uname -a Linux astrolabe11 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 GNU/Linux
connecting the ConfCam connect ruins all audio (even other cards become unavailable)
Quoted 18 lines · On Thu, 2 Jul 2020 at 16:15, <[email protected]> wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #31 from Marco S. ([email protected]) --- (In reply to Mathias Nyman from comment #30)
Quoted 2 lines
(In reply to Marco S. from comment #29)
Quoted 1 line
Hi, any news about it? when it's going to be implemented in stable
kernel?
Quoted 4 lines
Quoted 1 line
Thanks
it's in 5.4.36 stable kernel:
fceab238c534xhci: Don't clear hub TT buffer on ep0 protocol stallI'm running 5.7.6 and still have the issue with Logic Group USB
--
You are receiving this mail because:
You are on the CC list for the bug.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #33 from Mathias Nyman ([email protected]) --- So looks like patch:
8f97250c21f0 xhci: Don't clear hub TT buffer on ep0 protocol stall
Works for:
HUION tablet - Vincenzo Di Massa
C-Media Electronics, Inc. Audio Adapter - Florian Meyer
Doesn't work for:
Logitech ConfCam Connect - Dominique Archambault Logic Group USB - Marco S
For those that the patch doesn't work, could you take new traces and logs. See comment #21 for details
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Ikjoon Jang ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #37 from Ikjoon Jang ([email protected]) ---
like mentioned in #33, "8f97250c21f0 xhci: Don't clear hub TT buffer..." should be applied first. Moreover, it seems this device needs extra workaround in HID (This device is HUB + UVC + UAC + HID).
Adding "usbhid.quirks=0x046d:0x0882:0x4" to command line will block HID device initialized, and audio will be okay. but after this, pressing any key on a keypad will trigger disconnect.
FYI, the same bug is tracked on here: http://crbug.com/983482
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #38 from [email protected] ---
Created attachment 292255
--> https://bugzilla.kernel.org/attachment.cgi?id=292255&action=edit
trace ubuntu 20.04 5.8.4-050804-generic
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #39 from [email protected] ---
Created attachment 292257
--> https://bugzilla.kernel.org/attachment.cgi?id=292257&action=edit
dmesg ubuntu 20.04 5.8.4-050804-generic
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #40 from [email protected] ---
logitech group microphone and sounds does not work on ubuntu 20.04 with generic kernel 5.8.4. traces as in comment #21 attached.
I am available to test any build kernel. I have the device here
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #41 from Ikjoon Jang ([email protected]) ---
(In reply to Olivier R-D from comment #40)
Quoted 4 lines
logitech group microphone and sounds does not work on ubuntu 20.04 with generic kernel 5.8.4. traces as in comment #21 attached.
I am available to test any build kernel. I have the device here
comment #33:
Can you try this patch?
https://lkml.org/lkml/2020/7/21/89
note that "8f97250c21f0 xhci: Don't clear hub TT buffer..." should be included in your kernel before.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Stefan ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] | |et
--- Comment #42 from Stefan ([email protected]) --- (In reply to Ikjoon Jang from comment #41)
Quoted 4 lines
(In reply to Olivier R-D from comment #40)
Quoted 3 lines
logitech group microphone and sounds does not work on ubuntu 20.04 with generic kernel 5.8.4. traces as in comment #21 attached.
Quoted 8 lines
Quoted 1 line
I am available to test any build kernel. I have the device here
comment #33:
Can you try this patch?
https://lkml.org/lkml/2020/7/21/89note that "
8f97250c21f0xhci: Don't clear hub TT buffer..." should be included in your kernel before.
Hi Ikjoon Jang, the patch is working on our side butt there is a litte problem the device id is 0x0857 from our Logitech Group
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #43 from Ikjoon Jang ([email protected]) --- (In reply to Stefan from comment #42)
Quoted 11 lines
(In reply to Ikjoon Jang from comment #41)
Quoted 10 lines
(In reply to Olivier R-D from comment #40)
Quoted 4 lines
logitech group microphone and sounds does not work on ubuntu 20.04 with generic kernel 5.8.4. traces as in comment #21 attached.
I am available to test any build kernel. I have the device here
comment #33:
Can you try this patch?
https://lkml.org/lkml/2020/7/21/89
Quoted 8 lines
Quoted 2 lines
note that "
8f97250c21f0xhci: Don't clear hub TT buffer..." should be included in your kernel before.Hi Ikjoon Jang, the patch is working on our side butt there is a litte problem
the device id is0x0857from our Logitech Group
I don't have a device right now, from searching from saved logs, my device seems to be this (mine was 0x882) :
0x046d:0x085a - HS Hub
|- 0x046d:0x086e - Camera/HID
|- 0x046d:0x0882 - Audio/HID
We might need to add one more quirk like this?
USB_DEVICE_ID_LOGITECH_GROUP_AUDIOX 0x857USB_DEVICE_ID_LOGITECH_GROUP_AUDIOY 0x882
...
anyway let's go registering these ids: http://www.linux-usb.org/usb-ids.html
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #44 from Ulf ([email protected]) --- (In reply to Ikjoon Jang from comment #41)
Quoted 4 lines
(In reply to Olivier R-D from comment #40)
Quoted 3 lines
logitech group microphone and sounds does not work on ubuntu 20.04 with generic kernel 5.8.4. traces as in comment #21 attached.
Quoted 8 lines
Quoted 1 line
I am available to test any build kernel. I have the device here
comment #33:
Can you try this patch?
https://lkml.org/lkml/2020/7/21/89note that "
8f97250c21f0xhci: Don't clear hub TT buffer..." should be included in your kernel before.
Works for me on Logi Group 046d:0882 and kernel 5.8.5.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #45 from Olivier R-D ([email protected]) ---
I confirm the issues seems to be solved at kernel 5.8.6. Microphone and
speaker work for Logitech group
New USB device found, idVendor=046d, idProduct=0882, bcdDevice= 4.71
[ 32.853570] usb 2-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 32.853573] usb 2-4.2: Product: Logi Group Speakerphone [ 32.853576] usb 2-4.2: Manufacturer: Logitech
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #47 from Oliver Freyermuth ([email protected]) --- In my case, sadly, no matter wheter I add 084e or 084c to the list of quirked IDs, the issue seems to remain :-(.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Dirk Gajewski ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] | |e
--- Comment #48 from Dirk Gajewski ([email protected]) --- I can second the previous comment. Kernel 5.8.12: no success for Logitech conference cam. Camera is working but no audio (084b, 084c, 084e).
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #49 from Dirk Gajewski ([email protected]) --- Logitech conference cam (084b, 084c, 084e) is fully functional with kernel 5.9.0.
cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7d10000 irq 33
1 [Connect ]: USB-Audio - ConferenceCam Connect
Logitech ConferenceCam Connect at usb-0000:00:1d.0-1.7.1,full speed
lsusb
Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 002 Device 006: ID 046d:084b Logitech, Inc.
Bus 002 Device 005: ID 046d:084c Logitech, Inc.
Bus 002 Device 004: ID 046d:084e Logitech, Inc.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
Peter Newcomb ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #50 from Peter Newcomb ([email protected]) ---
I ran into this issue and found that my Logitech Group audio device shows up with id 0x0857, not 0x0882. I added the following patch and now it's working again:
drivers/hid/hid-ids.h +1 -0
@@ -775,6 +775,7 @@#define USB_DEVICE_ID_LOGITECH_WII_WHEEL 0xc29c#define USB_DEVICE_ID_LOGITECH_ELITE_KBD 0xc30a#define USB_DEVICE_ID_LOGITECH_GROUP_AUDIO 0x0882 +#define USB_DEVICE_ID_LOGITECH_GROUP_AUDIO_2 0x0857#define USB_DEVICE_ID_S510_RECEIVER 0xc50c#define USB_DEVICE_ID_S510_RECEIVER_2 0xc517#define USB_DEVICE_ID_LOGITECH_CORDLESS_DESKTOP_LX500 0xc512
drivers/hid/hid-quirks.c +0 -0
@@ -183,6 +183,7 @@ static const struct hid_device_id hid_quirks[] = { { HID_USB_DEVICE(USB_VENDOR_ID_WISEGROUP,
USB_DEVICE_ID_QUAD_USB_JOYPAD), HID_QUIRK_NOGET | HID_QUIRK_MULTI_INPUT },
{ HID_USB_DEVICE(USB_VENDOR_ID_XIN_MO,USB_DEVICE_ID_XIN_MO_DUAL_ARCADE), HID_QUIRK_MULTI_INPUT },
{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH,USB_DEVICE_ID_LOGITECH_GROUP_AUDIO), HID_QUIRK_NOGET },
+ { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH,USB_DEVICE_ID_LOGITECH_GROUP_AUDIO_2), HID_QUIRK_NOGET },
{ 0 }};
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #51 from [email protected] ---
Same issue here when I switched from 4.19 to 5.4. The original patch regarding 0x0882 did not resolve it for me. So I tried the extended patch by Peter, adding also 0x0857, and that made my setup work again. Any chance to get that patch accepted?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #52 from Takashi Iwai ([email protected]) ---
You'll need to show exactly what you've changed. And, at best, submit the patch by yourself to the upstream.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #53 from Peter Newcomb ([email protected]) --- FWIW, I eventually discovered that after I updated the firmware of the device I no longer needed the patch.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203419
--- Comment #54 from [email protected] ---
(In reply to Peter Newcomb from comment #53)
Quoted 2 lines
FWIW, I eventually discovered that after I updated the firmware of the device I no longer needed the patch.
Thanks for the hint about the firmware update, I did not expect one considering the advanced age of this model, for today's product lifecycle. Using another machine to run the latest updater (FWUpdateGroup_9.4.52.exe), it shows there is in fact an update available for my Logitech Group, 9.1 to 9.4. The info screen reports it would update "audio" and "codec" from 8.6.102 to 8.6.111, leaving both "video" and "eeprom" untouched at 1.4. Maybe someone who already has one with USB device id 0x0882 can verify it has 9.4/8.6.111?
As the updater does not hint any roll-back function, I guess there is no easy way to check things once I updated mine, so I did not do the update yet.
Considering that this updater is only available as exe, it would make sense from my perspective to submit the patch from comment 50 any way. So people who can not run the updater or when the updater is no longer available, could still use their Logitech Group.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.