Hama "Slim" USB 3.0 Multi Card Reader doesn't work

[Lastique]

I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi-card-reader-black) attached to a USB 3.0. After attaching the reader (or booting the system) the device works for some time, about a minute or so. It's blue power led is on. Then CPU load goes up to 30-50% and the power led on the reader starts turning off and on with a several seconds interval. It looks like the device is being repeatedly reinitialized. dmesg shows these lines while this is happening:

[ 147.251654] xhci_hcd 0000:05:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 147.447251] xhci_hcd 0000:05:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 220.546280] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 220.546283] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 251.266583] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 251.266584] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 284.045003] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 284.045006] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 314.761869] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 314.761873] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

and so on.

No cards are inserted in the device and no user activity on the system, the problem starts happening "on its own". I tried plugging the device in a different USB 3.0 slot, it doesn't help. The device worked on the same system in Kubuntu 18.04, linux kernel 4.15.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-generic 4.18.0.10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: lastique 3112 F.... pulseaudio
 /dev/snd/controlC1: lastique 3112 F.... pulseaudio
CurrentDesktop: KDE
Date: Sat Oct 20 19:31:35 2018
InstallationDate: Installed on 2015-05-01 (1267 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic N/A
 linux-firmware 1.175
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
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 PRO
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-VPRO: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

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

This change was made by a bot.

[Cristian Aravena Romero (caravena)]

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

[Lastique (andysem)]

> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?

As said in the description, it started happening after upgrading from Kubuntu 18.04 to 18.10. 18.04 has kernel 4.15.

> Would it be possible for you to test the latest upstream kernel?

The problem reproduces with kernel 4.19 rc8. The is the dmesg lines that start appearing when the problem happens:

[ 136.161611] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 136.161615] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 136.293090] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 166.865743] xhci_hcd 0000:05:00.0: WARN Cannot submit Set TR Deq Ptr
[ 166.865747] xhci_hcd 0000:05:00.0: A Set TR Deq Ptr command is pending.
[ 167.001317] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel between v4.16-rc1 to v4.18, from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.