Delayed failure in Genesys USB3 SD card reader

[Dave Jones]

I have a "UGreen USB3 Hub/SD card reader" which worked reliably under Ubuntu Xenial for many months. Recently, I re-installed the machine it was attached to with a fresh install of Ubuntu Focal. When initially booted, the device works perfectly (at least, the USB3 ports and SD card reader do; those are the only ports I use on it). However, after some period of time I inevitably find the device has stopped working, and dmesg is flooded with repeats of the following block of messages (I include several copies below so the typical time-delay between repeats can be observed):

[39695.777289] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[39695.777293] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39728.545725] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[39728.545728] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39761.313967] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[39761.313969] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39794.082286] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[39794.082289] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39826.850674] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr [39826.850677] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending. [39826.938742] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39859.618976] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr [39859.618979] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending. [39859.706965] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

The delay before failure (and these messages appearing) is highly variable. Sometimes it's within a couple of minutes of booting the machine; sometimes the device works happily for a couple of hours before failure.

I've found that simply replugging the device (temporarily) solves the issue, but obviously I'd prefer the device to be as reliable as it was under the Xenial kernel.

This may be related to LP: #1798979 which features extremely similar log messages on failure, but the symptoms are ever so slightly different (no CPU spike, no blinking LED), as is the model of card reader, hence why I've filed a separate bug. I'll add an apport report after filing this, but I should add there are multiple card-readers on this machine (my work involves raspberry pis, so I often find myself re-writing cards in bulk :). The specific one with the issue is listed as follows in the lsusb output:

Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and microSDXC CardReader

The other card reader listed in that output (realtek) is a separate device with no issues.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-09 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic N/A
 linux-firmware 1.187
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

[Dave Jones (waveform)]

apport information

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

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Which kernel did the system use in Xenial? Can you please roll back to the older kernel and test it?

[Dave Jones (waveform)]

> Which kernel did the system use in Xenial? Can you please roll back to the older kernel and test it?

Looks like 4.15.0-99 was the last kernel I used on Xenial before the upgrade. Is it possible to use a kernel that old on focal? If so, would the bisect instructions in LP: #1798979 be sufficient to follow? Happy to give it a shot if so.

[Kai-Heng Feng (kaihengfeng)]

Yes, Focal should work just fine on 4.15 kernel. And yes, the bisect instruction is sufficient.

[Dave Jones (waveform)]

Started the bisection; this may take several days to finish (each "good" result takes many hours to verify given that the problem sometimes didn't manifest for several hours). I'll update the ticket when I've got some further results.

[Dave Jones (waveform)]

I'm several steps down the bisect at this point and have overcome several compilation issues along the way (old kernels won't compile with gcc-9, so installed gcc-8, patched around an issue building with newer headers, https://gitlab.freedesktop.org/drm/msm/commit/dfbd199a7cfe3e3cd8531e1353cdbd7175bfbc5e, and dealt with some stale build artefacts, mainly vmlinux-gdb.py), but now I seem to have hit a build issue that I can't google around!

Specifically, I was at commit 2b7bee1a6df3e666e2ebf3e523ca9c1a98f931dd and got the following error during the build:

  CC /home/dave/projects/linux/tools/objtool/str_error_r.o
../lib/str_error_r.c: In function ‘str_error_r’:
../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified parameter aliases with argumen
t 5 [-Werror=restrict]
   snprintf(buf, buflen, "INTERNAL ERROR: strerror_r(%d, %p, %zd)=%d", errnum, buf, buflen, err);
   ^~~~~~~~
cc1: all warnings being treated as errors
mv: cannot stat '/home/dave/projects/linux/tools/objtool/.str_error_r.o.tmp': No such file or directory

I couldn't manage to successfully patch my way around that one, so I skipped that commit and instantly ran into exactly the same issue on the next try. Any ideas for working around this?

[Kai-Heng Feng (kaihengfeng)]

Please edit Makefile, and remove "-Werror" from KBUILD_CFLAGS.