snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings

Bug #1863973 reported by Matthew Ruffell
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Eoan
Expired
Medium
Unassigned
Focal
Expired
Medium
Unassigned

Bug Description

[Impact]

I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for meetings.
I access Google Meet with Firefox.

During a meeting, or immediately after one, and especially so if I join a second meeting after one finishes, my input devices start acting up and my system becomes unstable.

Things start with my Headset getting reset:

[ 3153.811599] usb 3-3: reset high-speed USB device number 2 using xhci_hcd

This happens multiple times.

Then I get a long list of suppressed callbacks:

[13468.808356] retire_capture_urb: 133 callbacks suppressed

From there, things timeout and I get this stack trace:

hid-generic 0003:046D:0A38.0005: input,hiddev2,hidraw4: USB HID v1.11 Device [Logitech Inc. Logitech USB Headset H340] on usb-0000:06:00.0-2/input3
INFO: task kworker/0:1:366 blocked for more than 120 seconds.
      Not tainted 5.3.0-40-generic #32-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/0:1 D 0 366 2 0x80004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 __schedule+0x2b9/0x6c0
 ? unlink1+0x31/0x130
 schedule+0x42/0xb0
 usb_kill_urb+0x81/0xc0
 ? wait_woken+0x80/0x80
 usb_hcd_flush_endpoint+0x16c/0x180
 usb_disable_endpoint+0x9b/0xb0
 usb_disable_interface+0x43/0x60
 usb_unbind_interface+0x183/0x260
 device_release_driver_internal+0xe4/0x1c0
 device_release_driver+0x12/0x20
 bus_remove_device+0xe1/0x150
 device_del+0x168/0x370
 ? usb_remove_ep_devs+0x1f/0x30
 usb_disable_device+0x9f/0x250
 usb_disconnect+0xc0/0x270
 hub_port_connect+0x7d/0x850
 port_event+0x502/0x780
 ? __switch_to_asm+0x40/0x70
 hub_event+0x152/0x390
 ? __schedule+0x2c1/0x6c0
 process_one_work+0x1db/0x380
 worker_thread+0x4d/0x400
 kthread+0x104/0x140
 ? process_one_work+0x380/0x380
 ? kthread_park+0x80/0x80
 ret_from_fork+0x35/0x40

This is then followed by:

[14262.566484] xhci_hcd 0000:06:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1
[14262.566487] xhci_hcd 0000:06:00.0: Looking for event-dma 00000007ed5edff0 trb-start 00000007b4a5b000 trb-end 00000007b4a5b000 seg-start 00000007b4a5b000 seg-end 00000007b4a5bff0

During this time, video stutters and audio coming to the headphone stutters and repeats. It sometimes makes having meetings difficult.

This has happened since 4.18 on cosmic, and was just as bad on 5.0 disco. When I moved to 5.3 eoan things got better, but I still experience these problems.

Usually these problems make Firefox unusable too, but for this particular snapshot of logs, Firefox continued to work fine.

If I unplug the headset and move it from a USB 2 port to a USB 3 port I can usually get through the meeting okay.

[Test Case]

Use a Logitech H340 USB Headset with Google Meet on Firefox. This is not always reproducible, and I am still determining how to reliably reproduce.

Tags: eoan
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is dmesg for 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is syslog from jorunalctl --since today

Revision history for this message
Matthew Ruffell (mruffell) wrote :

Attached is lsusb -vvv

Changed in linux (Ubuntu Eoan):
importance: Undecided → Medium
Changed in linux (Ubuntu Focal):
importance: Undecided → Medium
summary: - Logitech USB Headset Causes Softlockups During Meetings
+ snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1863973

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Eoan):
status: New → Incomplete
tags: added: eoan
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Focal) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Focal):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Eoan) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Eoan):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.