Comment 225 for bug 1667750

Revision history for this message
In , viniciuspython (viniciuspython-linux-kernel-bugs) wrote :

Just providing some information that could be helpful to debug the issue. It is also affecting me.

Kernel version:
# uname -a
Linux arch 5.3.1-arch1-1-ARCH #1 SMP PREEMPT Sat Sep 21 11:33:49 UTC 2019 x86_64 GNU/Linux

Hardware specs: AMD Ryzen 5 2400G

The issue happens when I plug in an Alfa AWUS036NH (148f:3070 Ralink Technology, Corp. RT2870/RT3070) - It uses the module rt2800usb

Below you can find my dmesg output when I plug in the Alfa device:

---
[ 1130.410091] usb 1-10: new high-speed USB device number 5 using xhci_hcd
[ 1130.653103] usb 1-10: New USB device found, idVendor=148f, idProduct=3070, bcdDevice= 1.01
[ 1130.653108] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1130.653111] usb 1-10: Product: 802.11 n WLAN
[ 1130.653113] usb 1-10: Manufacturer: Ralink
[ 1130.653114] usb 1-10: SerialNumber: 1.0
[ 1130.864470] usb 1-10: reset high-speed USB device number 5 using xhci_hcd
[ 1131.110058] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[ 1131.788103] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 1131.794331] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 1131.833798] rt2800usb 1-10:1.0 wlp1s0f0u10: renamed from wlan0
[ 1131.834234] audit: type=1130 audit(1569896348.109:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1131.867763] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 1131.867797] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[ 1136.117228] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 1136.840084] audit: type=1131 audit(1569896353.117:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
---

I don't know if this is useful, but I do have another USB WiFi that uses another module but doesn't trigger the issue when I plug in:
lsusb output: 2357:010c TP-Link TL-WN722N v2

Below is the dmesg output when I plug in the TP-LINK:

---
[ 1697.619576] usb 1-7: new high-speed USB device number 9 using xhci_hcd
[ 1697.846601] usb 1-7: New USB device found, idVendor=2357, idProduct=010c, bcdDevice= 0.00
[ 1697.846603] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1697.846605] usb 1-7: Product: 802.11n NIC
[ 1697.846606] usb 1-7: Manufacturer: Realtek
[ 1697.846607] usb 1-7: SerialNumber: 00E04C0001
[ 1697.858603] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 1698.262531] r8188eu 1-7:1.0 wlp1s0f0u7: renamed from wlan0
[ 1711.847379] MAC Address = c0:25:e9:1f:5c:3c
[ 1712.075372] R8188EU: indicate disassoc
---

Additionally, I see the warning when I plug in a Samsung Galaxy S5 device, but the warning appears only when I select certain "USB modes" in Android. Below you can see the dmesg log for each one of the USB modes:

--- dmesg log for "No data transfer" USB mode ---
[ 2523.666729] usb 1-7: USB disconnect, device number 32
[ 2524.157919] usb 1-7: new high-speed USB device number 33 using xhci_hcd
[ 2524.402980] usb 1-7: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.32
[ 2524.402985] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2524.402987] usb 1-7: Product: SAMSUNG_Android
[ 2524.402989] usb 1-7: Manufacturer: SAMSUNG
[ 2524.402991] usb 1-7: SerialNumber: 19a6e4d5

--- dmesg log for "PTP" USB mode ---
[ 2529.713679] usb 1-7: USB disconnect, device number 33
[ 2529.714018] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 2530.207346] usb 1-7: new high-speed USB device number 34 using xhci_hcd
[ 2530.452843] usb 1-7: New USB device found, idVendor=04e8, idProduct=6866, bcdDevice= 2.32
[ 2530.452847] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2530.452850] usb 1-7: Product: SAMSUNG_Android
[ 2530.452852] usb 1-7: Manufacturer: SAMSUNG
[ 2530.452854] usb 1-7: SerialNumber: 19a6e4d5

--- dmesg log for "USB Tethering" USB mode ---
[ 2533.697810] usb 1-7: USB disconnect, device number 34
[ 2533.698156] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 2534.183649] usb 1-7: new high-speed USB device number 35 using xhci_hcd
[ 2534.430728] usb 1-7: New USB device found, idVendor=04e8, idProduct=6864, bcdDevice= 2.32
[ 2534.430730] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2534.430732] usb 1-7: Product: SAMSUNG_Android
[ 2534.430733] usb 1-7: Manufacturer: SAMSUNG
[ 2534.430734] usb 1-7: SerialNumber: 19a6e4d5
[ 2534.464706] rndis_host 1-7:1.0: rndis media connect
[ 2534.510921] rndis_host 1-7:1.0 usb0: register 'rndis_host' at usb-0000:01:00.0-7, RNDIS device, 6e:36:5a:07:cd:06
[ 2534.552158] rndis_host 1-7:1.0 enp1s0f0u7: renamed from usb0
[ 2534.641284] audit: type=1130 audit(1569897751.028:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

--- dmesg log for "File Transfer" USB mode ---
[ 2536.996343] usb 1-7: USB disconnect, device number 35
[ 2536.996703] rndis_host 1-7:1.0 enp1s0f0u7: unregister 'rndis_host' usb-0000:01:00.0-7, RNDIS device
[ 2536.997131] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 2537.014124] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 2537.500061] usb 1-7: new high-speed USB device number 36 using xhci_hcd
[ 2537.754684] usb 1-7: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
[ 2537.754688] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2537.754690] usb 1-7: Product: SAMSUNG_Android
[ 2537.754691] usb 1-7: Manufacturer: SAMSUNG
[ 2537.754692] usb 1-7: SerialNumber: 19a6e4d5

I hope these logs can help you to debug the issue.