Linksys MR8300, OpenWrt 22.03.0-rc4, USB port-powered storage devices not working

Installing and Using OpenWrt
24

Ok. Here is another Kernel Log. This one is from the first bootup of the MR8300 right after a "Reset to defaults" was performed. So, this is the bare firmware image, without a single setting having been changed and without any additional package having been installed. But it still doesn't like to take any USB thumb drives.

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.138 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r19685-512e76967f) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Sat Sep 3 02:55:34 2022
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Linksys MR8300 (Dallas)
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000080000000-0x000000009fffffff]
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x0000000087dfffff]
[    0.000000]   node   0: [mem 0x0000000087e00000-0x0000000087ffffff]
[    0.000000]   node   0: [mem 0x0000000088000000-0x000000009fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000009fffffff]
[    0.000000] On node 0 totalpages: 131072
[    0.000000]   Normal zone: 1152 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] percpu: Embedded 15 pages/cpu s30860 r8192 d22388 u61440
[    0.000000] pcpu-alloc: s30860 r8192 d22388 u61440 alloc=15*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: init=/sbin/init rootfstype=ubifs ubi.mtd=11,2048 root=ubi0:ubifs rootwait rw root=/dev/ubiblock0_0 rootfstype=squashfs ro
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 506816K/524288K available (6445K kernel code, 608K rwdata, 948K rodata, 1024K init, 246K bss, 17472K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] 	Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 48.00MHz (virt).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb11fd3bfb, max_idle_ns: 440795203732 ns
[    0.000009] sched_clock: 56 bits at 48MHz, resolution 20ns, wraps every 4398046511096ns
[    0.000025] Switching to timer-based delay loop, resolution 20ns
[    0.000330] Calibrating delay loop (skipped), value calculated using timer frequency.. 96.00 BogoMIPS (lpj=480000)
[    0.000358] pid_max: default: 32768 minimum: 301
[    0.000549] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000569] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001582] CPU: Testing write buffer coherency: ok
[    0.001949] qcom_scm: convention: smc legacy
[    0.002915] Setting up static identity map for 0x80300000 - 0x8030003c
[    0.003080] rcu: Hierarchical SRCU implementation.
[    0.003341] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
[    0.003705] smp: Bringing up secondary CPUs ...
[    0.007203] smp: Brought up 1 node, 4 CPUs
[    0.007229] SMP: Total of 4 processors activated (384.00 BogoMIPS).
[    0.007239] CPU: All CPU(s) started in SVC mode.
[    0.012324] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[    0.012490] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.012518] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.012757] pinctrl core: initialized pinctrl subsystem
[    0.014555] NET: Registered protocol family 16
[    0.014981] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.016075] thermal_sys: Registered thermal governor 'step_wise'
[    0.016496] cpuidle: using governor ladder
[    0.016551] cpuidle: using governor menu
[    0.043145] cryptd: max_cpu_qlen set to 1000
[    0.047405] usbcore: registered new interface driver usbfs
[    0.047486] usbcore: registered new interface driver hub
[    0.047547] usbcore: registered new device driver usb
[    0.047597] pps_core: LinuxPPS API ver. 1 registered
[    0.047611] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.047638] PTP clock support registered
[    0.049599] clocksource: Switched to clocksource arch_sys_counter
[    0.050630] NET: Registered protocol family 2
[    0.050903] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.052042] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.052110] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.052173] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.052265] TCP: Hash tables configured (established 4096 bind 4096)
[    0.052404] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.052446] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.052730] NET: Registered protocol family 1
[    0.052777] PCI: CLS 0 bytes, default 64
[    0.055246] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.059754] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.059778] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.190701] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    0.192960] qcom-pcie 40000000.pci: host bridge /soc/pci@40000000 ranges:
[    0.193020] qcom-pcie 40000000.pci:       IO 0x0040200000..0x00402fffff -> 0x0040200000
[    0.193054] qcom-pcie 40000000.pci:      MEM 0x0040300000..0x0040ffffff -> 0x0040300000
[    0.471168] qcom-pcie 40000000.pci: Link up
[    0.471333] qcom-pcie 40000000.pci: PCI host bridge to bus 0000:00
[    0.471356] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.471377] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0x40200000-0x402fffff])
[    0.471393] pci_bus 0000:00: root bus resource [mem 0x40300000-0x40ffffff]
[    0.471444] pci 0000:00:00.0: [17cb:1001] type 01 class 0x060400
[    0.471475] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff]
[    0.471548] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.473067] PCI: bus0: Fast back to back transfers disabled
[    0.473392] pci 0000:01:00.0: [168c:0056] type 00 class 0x028000
[    0.473574] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    0.474407] pci 0000:01:00.0: PME# supported from D0 D3hot
[    0.476146] PCI: bus1: Fast back to back transfers disabled
[    0.476201] pci 0000:00:00.0: BAR 8: assigned [mem 0x40400000-0x405fffff]
[    0.476221] pci 0000:00:00.0: BAR 0: assigned [mem 0x40300000-0x40300fff]
[    0.476245] pci 0000:01:00.0: BAR 0: assigned [mem 0x40400000-0x405fffff 64bit]
[    0.476334] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    0.476351] pci 0000:00:00.0:   bridge window [mem 0x40400000-0x405fffff]
[    0.479189] pcieport 0000:00:00.0: AER: enabled with IRQ 102
[    0.481341] bam-dma-engine 8e04000.dma: num-channels unspecified in dt
[    0.481365] bam-dma-engine 8e04000.dma: num-ees unspecified in dt
[    0.482748] tcsr 1949000.tcsr: setting wifi_glb_cfg = 41000000
[    0.482849] tcsr 194b000.tcsr: setting usb hs phy mode select = e700e7
[    0.482941] tcsr 1953000.ess_tcsr: setting ess interface select = 0
[    0.483031] tcsr 1957000.tcsr: setting wifi_noc_memtype_m0_m2 = 2222222
[    0.483346] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.485147] msm_serial 78af000.serial: msm_serial: detected port #0
[    0.485197] msm_serial 78af000.serial: uartclk = 1843200
[    0.485256] 78af000.serial: ttyMSM0 at MMIO 0x78af000 (irq = 32, base_baud = 115200) is a MSM
[    0.485286] msm_serial: console setup on port #0
[    1.177760] printk: console [ttyMSM0] enabled
[    1.182978] msm_serial: driver initialized
[    1.191784] loop: module loaded
[    1.193447] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
[    1.193741] nand: Macronix MX30LF2G18AC
[    1.200389] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.203909] Block protection check failed
[    1.211659] 16 fixed-partitions partitions found on MTD device qcom_nand.0
[    1.215616] Creating 16 MTD partitions on "qcom_nand.0":
[    1.222434] 0x000000000000-0x000000100000 : "sbl1"
[    1.229516] 0x000000100000-0x000000200000 : "mibib"
[    1.234003] 0x000000200000-0x000000300000 : "qsee"
[    1.238669] 0x000000300000-0x000000380000 : "cdt"
[    1.243130] 0x000000380000-0x000000400000 : "appsblenv"
[    1.247836] 0x000000400000-0x000000480000 : "ART"
[    1.252930] 0x000000480000-0x000000680000 : "appsbl"
[    1.259069] 0x000000680000-0x000000700000 : "u_env"
[    1.262820] 0x000000700000-0x000000740000 : "s_env"
[    1.267147] 0x000000740000-0x000000780000 : "devinfo"
[    1.272072] 0x000000780000-0x000005f80000 : "kernel"
[    1.354382] 0x000000a80000-0x000005f80000 : "rootfs"
[    1.429527] mtd: device 11 (rootfs) set to be root filesystem
[    1.429898] mtdsplit: no squashfs found in "rootfs"
[    1.434277] 0x000005f80000-0x00000b780000 : "alt_kernel"
[    1.516786] 0x000006280000-0x00000b780000 : "alt_rootfs"
[    1.591954] 0x00000b780000-0x00000b880000 : "sysdiag"
[    1.593426] 0x00000b880000-0x00000ff00000 : "syscfg"
[    1.697739] ESS reset ok!
[    1.771984] ESS reset ok!
[    2.448340] EDMA using MAC@ - using
[    2.448356] 4e:56:03:6d:ca:3e
[    2.534788] i2c /dev entries driver
[    2.536630] sdhci: Secure Digital Host Controller Interface driver
[    2.537090] sdhci: Copyright(c) Pierre Ossman
[    2.543423] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.551867] NET: Registered protocol family 10
[    2.555087] Segment Routing with IPv6
[    2.557840] NET: Registered protocol family 17
[    2.561609] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    2.565837] 8021q: 802.1Q VLAN Support v1.8
[    2.579111] Registering SWP/SWPB emulation handler
[    2.593775] ubi0: attaching mtd11
[    3.196833] ubi0: scanning is finished
[    3.213285] ubi0: attached mtd11 (name "rootfs", size 85 MiB)
[    3.213378] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    3.218069] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    3.224983] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    3.231763] ubi0: good PEBs: 680, bad PEBs: 0, corrupted PEBs: 0
[    3.238465] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    3.244771] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1662173734
[    3.251813] ubi0: available PEBs: 0, total reserved PEBs: 680, PEBs reserved for bad PEB handling: 40
[    3.261232] ubi0: background thread "ubi_bgt0d" started, PID 123
[    3.262494] block ubiblock0_0: created from ubi0:0(rootfs)
[    3.282182] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    3.284156] Freeing unused kernel memory: 1024K
[    3.309998] Run /sbin/init as init process
[    3.310036]   with arguments:
[    3.310044]     /sbin/init
[    3.310051]   with environment:
[    3.310058]     HOME=/
[    3.310067]     TERM=linux
[    3.770348] init: Console is alive
[    3.770670] init: - watchdog -
[    4.052419] random: crng init done
[    4.546730] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    4.633393] genirq: irq_chip msmgpio did not update eff. affinity mask of irq 103
[    4.868300] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.868388] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    4.873042] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f665 hci version 0x100 quirks 0x0000000002010010
[    4.880396] xhci-hcd xhci-hcd.0.auto: irq 105, io mem 0x08a00000
[    4.890575] hub 1-0:1.0: USB hub found
[    4.895927] hub 1-0:1.0: 1 port detected
[    4.899825] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.903526] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    4.908823] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    4.919859] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.923548] hub 2-0:1.0: USB hub found
[    4.931277] hub 2-0:1.0: 1 port detected
[    4.935256] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.938866] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[    4.944416] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220f665 hci version 0x100 quirks 0x0000000002010010
[    4.951788] xhci-hcd xhci-hcd.1.auto: irq 106, io mem 0x06000000
[    4.961935] hub 3-0:1.0: USB hub found
[    4.967364] hub 3-0:1.0: 1 port detected
[    4.971244] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.974970] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[    4.980398] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
[    4.987926] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.995004] hub 4-0:1.0: USB hub found
[    5.002782] hub 4-0:1.0: config failed, hub doesn't have any ports! (err -19)
[    5.008479] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    5.023997] init: - preinit -
[    5.869217] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.070340] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[   10.095502] UBIFS (ubi0:1): Mounting in unauthenticated mode
[   10.095613] usb 1-1: USB disconnect, device number 2
[   10.096071] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 210
[   10.144576] UBIFS (ubi0:1): recovery needed
[   10.341765] UBIFS (ubi0:1): recovery completed
[   10.342182] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[   10.345175] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   10.353246] UBIFS (ubi0:1): FS size: 74915840 bytes (71 MiB, 590 LEBs), journal size 3809280 bytes (3 MiB, 30 LEBs)
[   10.363038] UBIFS (ubi0:1): reserved for root: 3538460 bytes (3455 KiB)
[   10.373275] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 18E4D7E3-ED7C-4422-9E4E-64AA260E47AA, small LPT model
[   10.381465] mount_root: overlay filesystem has not been fully initialized yet
[   10.391985] mount_root: switching to ubifs overlay
[   10.404580] urandom-seed: Seed file not found (/etc/urandom.seed)
[   10.562981] procd: - early -
[   10.563198] procd: - watchdog -
[   11.070578] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[   11.193400] procd: - watchdog -
[   11.219711] usb 1-1: Device not responding to setup address.
[   11.313872] procd: - ubus -
[   11.439743] usb 1-1: Device not responding to setup address.
[   11.488551] procd: - init -
[   11.659675] usb 1-1: device not accepting address 3, error -71
[   12.171750] kmodloader: loading kernel modules from /etc/modules.d/*
[   12.263542] Loading modules backported from Linux version v5.15.58-0-g7d8048d4e064
[   12.263590] Backport generated by backports.git v5.15.58-1-0-g42a95ce7
[   12.266797] urngd: v1.0.2 started.
[   12.355779] PPP generic driver version 2.4.2
[   12.360351] NET: Registered protocol family 24
[   12.384633] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x56.
[   12.385617] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[   12.392231] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   13.459702] usb 1-1: new high-speed USB device number 4 using xhci-hcd
[   13.898412] ath10k_pci 0000:01:00.0: qca9888 hw2.0 target 0x01000000 chip_id 0x00000000 sub 0000:0000
[   13.898466] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   13.911036] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9888-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 59e741e7
[   14.227080] ath10k_pci 0000:01:00.0: Loading BDF type 0
[   14.228029] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:23 crc32 1236d4f6
[   15.988555] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[   15.988609] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[   16.043390] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[   16.044477] ath10k_pci 0000:01:00.0: wmi print 'free: 114572 iram: 12644 sram: 29508'
[   16.293261] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   16.404548] ath: EEPROM regdomain: 0x833a
[   16.404563] ath: EEPROM indicates we should expect a country code
[   16.404573] ath: doing EEPROM country->regdmn map search
[   16.404582] ath: country maps to regdmn code: 0x37
[   16.404590] ath: Country alpha2 being used: GB
[   16.404596] ath: Regpair used: 0x37
[   16.426643] usb 1-1: USB disconnect, device number 4
[   17.399686] usb 1-1: new high-speed USB device number 5 using xhci-hcd
[   18.390203] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[   18.390256] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   18.402191] ath10k_ahb a000000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b
[   18.453845] ath10k_ahb a000000.wifi: Loading BDF type 0
[   18.481712] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:20 crc32 92fcc3a6
[   19.769116] ath10k_ahb a000000.wifi: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[   19.769175] ath10k_ahb a000000.wifi: msdu-desc: 2500  skid: 32
[   19.818901] ath10k_ahb a000000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[   19.820581] ath10k_ahb a000000.wifi: wmi print 'free: 53252 iram: 13432 sram: 35752'
[   19.970474] ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   20.167330] ath: EEPROM regdomain: 0x833a
[   20.167345] ath: EEPROM indicates we should expect a country code
[   20.167355] ath: doing EEPROM country->regdmn map search
[   20.167365] ath: country maps to regdmn code: 0x37
[   20.167372] ath: Country alpha2 being used: GB
[   20.167379] ath: Regpair used: 0x37
[   20.392141] usb 1-1: USB disconnect, device number 5
[   21.117260] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[   21.117313] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   21.129304] ath10k_ahb a800000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b
[   21.159672] usb 1-1: new high-speed USB device number 6 using xhci-hcd
[   21.180950] ath10k_ahb a800000.wifi: Loading BDF type 0
[   21.181694] ath10k_ahb a800000.wifi: board_file api 2 bmi_id 0:21 crc32 92fcc3a6
[   22.473245] ath10k_ahb a800000.wifi: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[   22.473312] ath10k_ahb a800000.wifi: msdu-desc: 2500  skid: 32
[   22.524288] ath10k_ahb a800000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[   22.524722] ath10k_ahb a800000.wifi: wmi print 'free: 53252 iram: 13432 sram: 35752'
[   22.666777] ath10k_ahb a800000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   22.831139] ath: EEPROM regdomain: 0x833a
[   22.831153] ath: EEPROM indicates we should expect a country code
[   22.831164] ath: doing EEPROM country->regdmn map search
[   22.831173] ath: country maps to regdmn code: 0x37
[   22.831181] ath: Country alpha2 being used: GB
[   22.831186] ath: Regpair used: 0x37
[   22.836362] usb 1-1: USB disconnect, device number 6
[   22.843388] kmodloader: done loading kernel modules from /etc/modules.d/*
[   23.339659] usb 1-1: new high-speed USB device number 7 using xhci-hcd
[   25.429828] usb 1-1: new high-speed USB device number 8 using xhci-hcd
[   27.009726] usb 1-1: device descriptor read/64, error -71
[   28.452528] usb 1-1: device descriptor read/64, error -71
[   29.019675] usb 1-1: new high-speed USB device number 9 using xhci-hcd
[   43.420154] usb 1-1: USB disconnect, device number 9
[   45.259699] usb 1-1: new high-speed USB device number 10 using xhci-hcd
[   47.525187] usb 1-1: USB disconnect, device number 10
[   47.785027] br-lan: port 1(eth0) entered blocking state
[   47.785087] br-lan: port 1(eth0) entered disabled state
[   47.789489] device eth0 entered promiscuous mode
[   47.911533] ess_edma c080000.edma eth1: Link is Down
[   48.279689] usb 1-1: new high-speed USB device number 11 using xhci-hcd
[   48.809732] br-lan: port 1(eth0) entered blocking state
[   48.809784] br-lan: port 1(eth0) entered forwarding state
[   48.815171] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   49.169805] usb 1-1: device descriptor read/64, error -71
[   52.513170] usb 1-1: USB disconnect, device number 11
[   53.059719] usb 1-1: new high-speed USB device number 12 using xhci-hcd
[   54.281005] usb 1-1: USB disconnect, device number 12
[   54.730735] usb 1-1: new high-speed USB device number 13 using xhci-hcd
[   61.038390] usb 1-1: USB disconnect, device number 13
[   61.500213] usb 1-1: new high-speed USB device number 14 using xhci-hcd
[   63.195579] usb 1-1: USB disconnect, device number 14
[   65.100955] usb 1-1: new high-speed USB device number 16 using xhci-hcd
[   67.474985] usb 1-1: USB disconnect, device number 16
[   68.939756] usb 1-1: new high-speed USB device number 17 using xhci-hcd
[   69.813162] usb 1-1: USB disconnect, device number 17
[   70.262017] usb 1-1: new high-speed USB device number 18 using xhci-hcd
[   74.554850] usb 1-1: USB disconnect, device number 18
[   74.999885] usb 1-1: new high-speed USB device number 19 using xhci-hcd
[   75.610597] usb 1-1: device descriptor read/64, error -71
[   76.205264] usb 1-1: USB disconnect, device number 19
[   77.169766] usb 1-1: new high-speed USB device number 20 using xhci-hcd
[   84.263565] usb 1-1: USB disconnect, device number 20
[   84.720690] usb 1-1: new high-speed USB device number 21 using xhci-hcd
25

I've heard, that the UAS implementation of some host controllers and some clients is broken. AFAIK the UAS module is not necessary. Did you try to operate your SSD drive without the UAS module?

I use every USB3 storage device without the UAS module and never had a problem with any device and/or host. Just give it a try. It doesn't hurt. :wink:

26

Looks like I'm also having issues. Just tried copying files and while it seemed fine, it errored half way while copying a large file.

Here's my log.

Mine seems to be recognising the device though but something goes wrong at some point.

Thu Sep 15 21:17:01 2022 kern.info kernel: [260459.563038] usb 2-1: new SuperSpeed Gen 1 USB device number 64 using xhci-hcd
Thu Sep 15 21:17:01 2022 kern.info kernel: [260459.598937] scsi host0: uas
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.600378] scsi 0:0:0:0: Direct-Access     External USB3.0           0204 PQ: 0 ANSI: 6
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.605766] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.608983] sd 0:0:0:0: [sda] 4096-byte physical blocks
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.619221] sd 0:0:0:0: [sda] Write Protect is off
Thu Sep 15 21:17:01 2022 kern.debug kernel: [260459.622093] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.629289] sd 0:0:0:0: [sda] Disabling FUA
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.631903] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Thu Sep 15 21:17:01 2022 kern.warn kernel: [260459.638658] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Thu Sep 15 21:17:01 2022 kern.info kernel: [260459.726505]  sda: sda1 sda2
Thu Sep 15 21:17:01 2022 kern.notice kernel: [260459.738426] sd 0:0:0:0: [sda] Attached SCSI disk
Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.110940] usb 2-1: USB disconnect, device number 64
Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.112134] sd 0:0:0:0: [sda] tag#7 uas_zap_pending 0 uas-tag 1 inflight: CMD
Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.115061] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00
Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.125748] sd 0:0:0:0: [sda] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 cmd_age=0s
Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.130014] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00
Thu Sep 15 21:17:02 2022 kern.err kernel: [260460.139306] blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Thu Sep 15 21:17:02 2022 kern.err kernel: [260460.147596] blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Thu Sep 15 21:17:02 2022 kern.err kernel: [260460.157161] Buffer I/O error on dev sda, logical block 0, async page read
Thu Sep 15 21:17:02 2022 kern.notice kernel: [260460.169256] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Thu Sep 15 21:17:02 2022 daemon.err smbd[16154]: [2022/09/15 21:17:02.882708,  0] ../../source3/smbd/service.c:167(chdir_current_service)

@Barney Thanks for the suggestion. Just removed it. I will switch back to the SSD disk and let you know.

27

According to the logs my MR8300 also recognizes all the devices I have, the problem is that a moment after the USB device was recognized something goes wrong and then the USB device is getting disconnected. This goes on and on.

Like can be seen in your log as well. The USB device is recognized:

Thu Sep 15 21:17:01 2022 kern.info kernel: [260459.563038] usb 2-1: new SuperSpeed Gen 1 USB device number 64 using xhci-hcd

... and just one second later the USB device disconnects.

Thu Sep 15 21:17:02 2022 kern.info kernel: [260460.110940] usb 2-1: USB disconnect, device number 64

The "device number" starts at 1 after a reboot and counts up by 1 every time a device is recognized. So, "device number 64" means that your device was recognized (and then disconnected) more than 60 times already.

28

@Barney I tested and without the kmod-usb-storage-uas it won't even load the disk to /dev/sdxx

As soon as I installed uas, it loaded /dev/sda and /dev/sda1. Unfortunately, I was not able to mount it. No specific error in dmesg

@dr123 You are absolutely right. Mine has been OK so far though. It might have tried so many times and got there in the end. I wonder if this count includes the SSD which in the end did not work as I had thought. It merely loaded it and as soon as I tried accessing the data, it worked briefly before the device becoming unavailable. The whole thing is messy. There must be a bug in the software that is specific to the MR8300, either the OS or the drivers.

29

Okay, loading or not loading kmod-usb-storage-uas makes no difference: you are not able to use your ssd as storage device.

Last idea: when you connect your ssd to a normal PC, does the ssd (with usb enclosure) work with or without the uas driver? If the ssd works with a PC, then (that's my personal conclusion) the mess is with the MR8300 router (hardware and/or software). Or did I miss anything?

30

I am experiencing the same issue. Any kind of external USB storage is being reset a short time after being plugged in. I tried various external drives as well as USB3 to sdcard adapters. See attached log.

Is this an issue only related to this device or is the whole platform range using this same SoC affected?

[51714.770225] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1532 PQ: 0 ANSI: 6
[51715.151030] sd 0:0:0:0: [sda] 249737216 512-byte logical blocks: (128 GB/119 GiB)
[51715.151763] sd 0:0:0:0: [sda] Write Protect is off
[51715.157573] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[51715.162782] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[51715.172652]  sda: sda1 sda2
[51715.179067] sd 0:0:0:0: [sda] Attached SCSI removable disk
[51715.240490] usb 2-1: USB disconnect, device number 57
[51715.824163] usb 2-1: new SuperSpeed Gen 1 USB device number 58 using xhci-hcd
[51715.861981] usb-storage 2-1:1.0: USB Mass Storage device detected
[51715.868764] scsi host0: usb-storage 2-1:1.0
[51716.927349] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1532 PQ: 0 ANSI: 6
[51717.311279] sd 0:0:0:0: [sda] 249737216 512-byte logical blocks: (128 GB/119 GiB)
[51717.312317] sd 0:0:0:0: [sda] Write Protect is off
[51717.328673] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[51717.329739] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[51717.341583]  sda: sda1 sda2
[51717.350848] sd 0:0:0:0: [sda] Attached SCSI removable disk
[51717.404092] usb 2-1: USB disconnect, device number 58
[51717.954464] usb 2-1: new SuperSpeed Gen 1 USB device number 59 using xhci-hcd
[51717.992934] usb-storage 2-1:1.0: USB Mass Storage device detected
[51717.995773] scsi host0: usb-storage 2-1:1.0
[51719.005569] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1532 PQ: 0 ANSI: 6
[51719.369221] sd 0:0:0:0: [sda] 249737216 512-byte logical blocks: (128 GB/119 GiB)
[51719.370413] sd 0:0:0:0: [sda] Write Protect is off
[51719.380813] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[51719.389187] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[51719.404396]  sda: sda1 sda2
[51719.407860] sd 0:0:0:0: [sda] Attached SCSI removable disk
[51719.472022] usb 2-1: USB disconnect, device number 59
[51720.035088] usb 2-1: new SuperSpeed Gen 1 USB device number 60 using xhci-hcd
[51720.068566] usb-storage 2-1:1.0: USB Mass Storage device detected
[51720.069404] scsi host0: usb-storage 2-1:1.0
31

Hi guys. Just tried the latest release 22.03.2 and the problem is still there. How can we report this to the developers to look into this?

33

Update:
It does not work with an active / powered USB-HUB at all! At least not with an USB3 Hub.
In hope of an interim fix I bought this USB3 powered/active hub on amazon: https://www.amazon.de/gp/product/B0BCPB7HQX/ but the result is still the same.

I am not able to mount the drive. Every single attached USB-Storage device I tried is reset upon accessing. To be sure it is not a matter of specific hardware I tried it with various external devices, including USB-Sticks, SD-Card to USB-Adapters, a few Samsung SSDs, Seagate Baracuda SSD and some SSD (different brands) in USB to SSD adapter cases. It is always the same disconnect.

I already thougt about replacing the MR8300 with a Linksys 1900ACs but besides being twice as expensive it has only half the FLASH and is not available here at the moment.

Can anyone on here forward this please to the according developer?
Or name us a forum or thread where we can reach the developer?

Thank you!

34

I have same issue, with the stock firmware mechanical hard drive and SSD work flawless with unpowered hub.
Openwrt only power with powered hub DIY, the hub is only power from external source I cut the 5v from router.

35

Cross posting here, in case somebody has some hints (from https://github.com/openwrt/openwrt/issues/11187).

I can definitively confirm this behavior, although I am unsure whether it's actually the power draw that's an issue.
I have tried a vast amount of different USB sticks (everything from USB 1 to latest USB 3.2 Gen 1), both with and without active USB hub and all showed the very same behavior.
The USB device was recognized and immediatly afterwards resetted. This already happens during the boot time multiple times (can be confirmed via logread or serial access).
What I have found that did also not work, was generally managing a USB device from within the original Linksys firmware - the page simply never loaded. This happened with both preformatted (as FAT, EXFAT, NFTS, EXT4) as well as raw (unformatted) USB devices - I am actually unsure if this USB port is even properly working.

Further, I have measured the power draw of all of these devices and found that enough power was in fact drawn by the device (compared the values of the USB devices inserted to a default Fedora installation) when it is inserted into the router.
I also tried to mess around with kernel USB quirks to see if there is some flag that could help to resolve that issue or at least make it less often happen, but I couldn't make any meaningful progress there either.

Unfortunately, I am now out of ideas. Maybe somebody has some hints on how to debug this further, as the MR8300 seems to be the only available replacement for my beloved EA8300 devices.

I really appreciate any hints.

All the best,
Steffen

1 Like
36

Thanks for your post.

Does you last line indicate that you also own at least one EA8300 running OpenWrt?
If yes, do the same USB devices that don't work on the MR8300 work fine on the USB port of the EA8300?

By the way, when I first got my MR8300 I also had the problem with the USB in the Linksys firmware.
It turned out that on this router model it is mandatory to go through the official "setup process", which I falsely deemed to be something for "beginner" users and hence I skipped it.
I believe as long as the main LED on the MR8300 lights up in purple color the router is still waiting for the setup process to be completed by the user and once that is done the LED will turn blue and the USB starts working. At least that was the case for me.
I can't remember now whether this "setup" required using some smartphone app or not.

1 Like
37

I own multiple EA8300s running for years with the same type of USB devices.

With regards to the Linksys firmware: Good hint, maybe I should try that out (setting up the router "properly") - on the other hand you tried it already, so we can definitely rule out a non-functional port, I guess.

... which brings us back to square one, as I am out of ideas.

38

So, I did a bit more fiddling around.
I decided to open my device and see if it has the same pin out for accessing a serial console like the EA8330. Luckily it not only has the pin out but actual pins soldered on for easy access.
I booted into the Linksys firmware and tried to setup a few USB devices and see if they would stay mounted: they do! I not only tried the small USB sticks but also some that are USB 3 Gen 2 or whatever the new fancy name is - they work without any issue. I could mount them and copy several GB of dummy data (using dd) on them and they would not disconnect a single time.

What I found interesting is, that they seemed to be mounted using EHCI instead of XHCI, although the hub itself is apparently using the XHCI module. I will post the complete boot log here later (it is on my notebook, not on this device).
Trying to reproduce the behavior on Openwrt, no matter how hard I tried, I was unable to figure out how to make a USB device mounted via EHCI instead of XHCI. Whenever I unload the kernel modules xhci_hcd{_pci,platform} the entire USB hub of the MR8300 will go silent even if I load the EHCI kernel modules.

I'll do a bit more digging with debugfs and usbmon and see if something sticks.

If anybody knows how to enforce a USB device to mounted with a specific driver, please let me know!

39

Long story short: I couldn't make any progress. Unless somewhen with actual kernel knowledge wants to dive in to this, USB is simply not working on this device.
I am more than happy to help troubleshooting to get proper USB support for the MR8300, but I am unable to accomplish that myself.

Any help of a person that has kernel knowledge is highly appreciated.

All the best

40

Have you tried to make a custom build with kmod-usb2 instead of kmod-usb3 which is by default?

41

Thanks for your response.
I just tried it, but unfortunately, this leads to the USB hub not being discovered. Once I install kmod-usb3 and the module is loaded, the hub and the USB stick is immediately discovered and the USB stick gets mounted. Unfortunately, the USB stick keeps resetting over and over and over :confused:

1 Like
42

Worthy to try at least.
I own a MR8300 but I have never tried to plug anything in the USB. I'm following this thread anyway.

An idea to investigate. Maybe the OEM firmware limits itself to USB2 performance for a matter of power consumption. USB3 demands more. On the other hand, OpenWrt try to use USB3, and the hardware can't offer the power needed. Is there a way to tell OpenWrt to limit itself to USB2 despite USB3 capable port?

43

Some of the USB thumb drives I have tested are only capable of USB 2 (without the additional 5 pins used for USB 3) and the problem was exactly the same. And the power they draw from the USB port is very low.

By the way.
According to the official firmware release notes for the MR8300 it appears that it even took Linksys considerable time to enable support for storage devices via the USB port on this router model. (on the box that my MR8300 V1.1 came in the USB port is still marked with "For future expansion" and no word about USB storage support)
https://downloads.linksys.com/support/assets/releasenotes/MR8300_1.1.10.210186_Customer_ReleaseNotes.txt

Given that the older EA8300 already supported USB storage devices before the MR8300 even existed and both router models are based on the same Qualcomm chips, it would seem illogical that Linksys didn't provide USB storage support on the MR8300 right from the start. Unless they were maybe facing some unexpected problem with the re-designed PCB?

I wonder if Linksys had to come up with an unusual solution to make the USB port on the MR8300 work, like implement some sophisticated load balancing or pause some other system component(s) whenever a data packet is to be sent or received from the USB port?

1 Like
44

Interesting analysis.