Kernel Warning/ USB HUB issues

[xKaiser]

I'm in the process of debugging another issue with using a USB hub, modem, and RFID reader and I came across this in the log - first time I've seen it, so I don't think it's related, however I just switched to 4.14.79, so I figure I'd make an issue.

Nov 28 19:08:32 rfidpi kernel: [ 498.068294] ------------[ cut here ]------------
Nov 28 19:08:32 rfidpi kernel: [ 498.068350] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x294/0x298
Nov 28 19:08:32 rfidpi kernel: [ 498.068363] NETDEV WATCHDOG: wwan0 (qmi_wwan): transmit queue 0 timed out
Nov 28 19:08:32 rfidpi kernel: [ 498.068371] Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc bnep hci_uart btbcm serdev bluetooth ecdh_generic option qmi_wwan usb_wwan cdc_wdm usbserial cdc_acm spidev brcmfmac brcmutil cfg80211 rfkill snd_bcm2835(C) i2c_bcm2835 snd_pcm spi_bcm2835 snd_timer snd uio_pdrv_genirq uio fixed i2c_dev ip_tables x_tables ipv6
Nov 28 19:08:32 rfidpi kernel: [ 498.068562] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C 4.14.79-v7+ #1159
Nov 28 19:08:32 rfidpi kernel: [ 498.068567] Hardware name: BCM2835
Nov 28 19:08:32 rfidpi kernel: [ 498.068597] [<8010ff30>] (unwind_backtrace) from [<8010c174>] (show_stack+0x20/0x24)
Nov 28 19:08:32 rfidpi kernel: [ 498.068615] [<8010c174>] (show_stack) from [<80788fa4>] (dump_stack+0xd4/0x118)
Nov 28 19:08:32 rfidpi kernel: [ 498.068632] [<80788fa4>] (dump_stack) from [<8011dd50>] (__warn+0xf8/0x110)
Nov 28 19:08:32 rfidpi kernel: [ 498.068647] [<8011dd50>] (__warn) from [<8011ddb0>] (warn_slowpath_fmt+0x48/0x50)
Nov 28 19:08:32 rfidpi kernel: [ 498.068661] [<8011ddb0>] (warn_slowpath_fmt) from [<806bffec>] (dev_watchdog+0x294/0x298)
Nov 28 19:08:32 rfidpi kernel: [ 498.068679] [<806bffec>] (dev_watchdog) from [<8018a86c>] (call_timer_fn+0x40/0x19c)
Nov 28 19:08:32 rfidpi kernel: [ 498.068695] [<8018a86c>] (call_timer_fn) from [<8018aacc>] (expire_timers+0x104/0x168)
Nov 28 19:08:32 rfidpi kernel: [ 498.068711] [<8018aacc>] (expire_timers) from [<8018abd8>] (run_timer_softirq+0xa8/0x1c8)
Nov 28 19:08:32 rfidpi kernel: [ 498.068726] [<8018abd8>] (run_timer_softirq) from [<80101694>] (__do_softirq+0x18c/0x3d8)
Nov 28 19:08:32 rfidpi kernel: [ 498.068741] [<80101694>] (__do_softirq) from [<80123aec>] (irq_exit+0x108/0x164)
Nov 28 19:08:32 rfidpi kernel: [ 498.068759] [<80123aec>] (irq_exit) from [<80175c68>] (__handle_domain_irq+0x70/0xc4)
Nov 28 19:08:32 rfidpi kernel: [ 498.068776] [<80175c68>] (__handle_domain_irq) from [<80101504>] (bcm2836_arm_irqchip_handle_irq+0xa8/0xac)
Nov 28 19:08:32 rfidpi kernel: [ 498.068791] [<80101504>] (bcm2836_arm_irqchip_handle_irq) from [<807a4b7c>] (__irq_svc+0x5c/0x7c)
Nov 28 19:08:32 rfidpi kernel: [ 498.068798] Exception stack(0xae925f38 to 0xae925f80)
Nov 28 19:08:32 rfidpi kernel: [ 498.068807] 5f20: 00000000 011ed220
Nov 28 19:08:32 rfidpi kernel: [ 498.068819] 5f40: 2e568000 00000000 ae924000 80c03dcc 80c03d68 80c885b2 00000001 410fd034
Nov 28 19:08:32 rfidpi kernel: [ 498.068833] 5f60: 00000000 ae925f94 80c04174 ae925f88 80108a0c 80108a10 60000013 ffffffff
Nov 28 19:08:32 rfidpi kernel: [ 498.068850] [<807a4b7c>] (__irq_svc) from [<80108a10>] (arch_cpu_idle+0x34/0x4c)
Nov 28 19:08:32 rfidpi kernel: [ 498.068869] [<80108a10>] (arch_cpu_idle) from [<807a42dc>] (default_idle_call+0x34/0x48)
Nov 28 19:08:32 rfidpi kernel: [ 498.068887] [<807a42dc>] (default_idle_call) from [<8016177c>] (do_idle+0xd8/0x150)
Nov 28 19:08:32 rfidpi kernel: [ 498.068903] [<8016177c>] (do_idle) from [<80161a90>] (cpu_startup_entry+0x28/0x2c)
Nov 28 19:08:32 rfidpi kernel: [ 498.068918] [<80161a90>] (cpu_startup_entry) from [<8010deac>] (secondary_start_kernel+0x134/0x140)
Nov 28 19:08:32 rfidpi kernel: [ 498.068932] [<8010deac>] (secondary_start_kernel) from [<0010196c>] (0x10196c)
Nov 28 19:08:32 rfidpi kernel: [ 498.068945] ---[ end trace 5aeecf6213cac216 ]---

To reproduce
D-Link DUB-H4
Hologram Nova Modem R410M / U201
ThingMagic M6E RFID reader (various models).

Use the devices, see devices disconnect occasionally and error messages.

System

• Which model of Raspberry Pi? Pi 3B
• Which OS and version (cat /etc/rpi-issue)? Raspberry Pi reference 2017-11-29
  Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, b71bf3179310aadf9aaf2ffcdf094a88e488dce8, stage2
• Which firmware version (vcgencmd version)? version ed5baf9520a3c4ca82ba38594b898f0c0446da66 (clean) (release)
• Which kernel version (uname -a)? Linux rfidpi 4.14.79-v7+ USB-Harddrive gets fully powered down #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

Logs
Full logs (dmesg + lsusb -v)
https://pastebin.com/WVhhukya

Additional context
Investigating another issue with some devices working well, and others not working at all. This dmesg snippet indicates the errors I was seeing on 4.14.71:
https://pastebin.com/mqV8p3KQ

This is the 4.14.79 log of a different pi, same issue, different error messaging:
https://pastebin.com/sCzDTc2E

---

Edit: I thought I was on 4.19, as I did a BRANCH=next rpi-update yesterday, but somehow I'm on 4.14.79. Maybe I did an apt upgrade or something that reverted me back... I'm investigating. Going to try again when I'm sure I'm on 4.19 and update this ticket.

Edit 2: I so far haven't been able to reproduce this on 4.19. I'm going to leave three devices running overnight, so hopefully I'll have something to report then.

[xKaiser]

I've reproduced the issue on 4.19.5, but I've narrowed it down to some of these D-Link DUB-H4s cause "Cannot enable. Maybe the USB cable is bad?" messages in the kernel logs, where as others do not, but because it is easily reproduced with the bad hubs, I think it is a hardware issue. Closing the issue.