Logitech BRIO webcam fails with "xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13"

[John Gilmore]

[ 450.844431] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
[ 450.844439] xhci_hcd 0000:02:00.0: Looking for event-dma 00000000fd473230 trb-start 00000000fd473210 trb-end 00000000fd473210 seg-start 00000000fd473000 seg-end 00000000fd473ff0

The above occurs while trying to use Cheese to access the Logitech BRIO webcam (USB device 046d:085e).

Ultimately the webcam doesn't work with Cheese. When it produces any image at all, it is full of vertical bars and is in greyscale. Meanwhile dmesg shows hundreds of the above kernel messages.

After getting out of Cheese, I unplugged and replugged the webcam. This produced:

Apr 17 03:58:30 shh kernel: [ 1218.202407] usb 2-8: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Apr 17 03:58:35 shh kernel: [ 1223.341073] usb 2-8: device descriptor read/8, error -110

then a new series when plugged in:
Apr 17 03:59:13 shh kernel: [ 1261.369494] usb 2-8: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Apr 17 03:59:18 shh kernel: [ 1266.604852] usb 2-8: device descriptor read/8, error -110

which repeated a few times, interspersed with:
Apr 17 03:59:34 shh kernel: [ 1282.848732] usb usb2-port8: attempt power cycle
Apr 17 03:59:35 shh kernel: [ 1283.361363] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
Apr 17 03:59:40 shh kernel: [ 1288.621098] usb 2-8: device descriptor read/8, error -110
Apr 17 03:59:40 shh kernel: [ 1288.728918] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
Apr 17 03:59:46 shh kernel: [ 1293.996668] usb 2-8: device descriptor read/8, error -110

and ultimately:
Apr 17 03:59:56 shh kernel: [ 1304.864636] usb usb2-port8: unable to enumerate USB device

This dustup with the webcam also seems to screw up the USB interface to a nearby disk drive on a completely different USB port on the motherboard.

The problem persists until the kernel is rebooted. Power cycling the webcam (it has no battery, so pulling the USB cord, waiting ten seconds, and replugging it suffices) does not fix the "error -110" issue, so the webcam can never be accessed again until the kernel is rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-24-generic 5.4.0-24.28
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 17 03:54:10 2020
InstallationDate: Installed on 2020-04-17 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
IwConfig:
 enp5s0 no wireless extensions.

 enp6s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-24-generic N/A
 linux-backports-modules-5.4.0-24-generic N/A
 linux-firmware 1.187
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming 5
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Peter Nijs (depeje)]

This bug seems to be related to the ASMedia USB3.1 host controller. I'm also experiencing this issue when my webcam is connected to my ASM1142 host controller. (Also under Windows it works quite flaky btw.) When connected to my Intel USB3.0 host controller, I have no issues.

@John: if you have external USB ports which are connected to your AMD USB3.0 host controller you can use these as a workaround.

[Tais P. Hansen (taisph)]

I have a similar issue with my Logitech Brio. Used with Google Meet I can usually get through one meeting after which the webcam hangs and the camera light stays on, even through a reboot. A combination of unplugging, rebooting and replugging seems to be necessary to recover it.

The webcam has the newest firmware (2.4).

I have it connected to an ASMedia controller as well.

0a:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller (prog-if 30 [XHCI])

Moving it to a different port on the same controller does not fix it, so presumably the controller crashes. Moving it to a different controller seems to work.

00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller (prog-if 30 [XHCI])

Note that this is a fairly recent issue for me. I have not always had the issue. I suspect the upgrade from Ubuntu 18.04 to 20.04 or a recent kernel update is where this issue started appearing.

[Tais P. Hansen (taisph)]

The command below gets the controller working again for me.

echo -n "0000:0a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
sleep 5
echo -n "0000:0a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind