Wi-Fi reconnection issue on Verdin iMX8M Plus (Dahlia)

Dear all,

I am experiencing an issue with the Verdin iMX8M Plus on the Dahlia board.
The device disconnects from the company Wi-Fi network and does not reconnect automatically.

To handle this, I implemented a test that periodically checks the connection, and if Wi-Fi is down, I restart Linux. However, in some situations, a software reboot does not restore the connection. On the other hand, when I perform a power cycle, the device always reconnects successfully.

It seems to me that the problem might be related to the physical Wi-Fi driver, since it only works reliably after a power reset.

I am facing this problem on both Toradex devices deployed in the field. The image I am using is 6.6.84-7.2.0-devel, built with YOCTO, where I only added one custom layer to create a service and launch my application.

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:


Wi-Fi Connection Issues on Verdin iMX8M Plus

Based on your description of Wi-Fi disconnection issues that require power cycling to resolve, this appears to be related to the Wi-Fi module driver behavior. The Verdin iMX8M Plus uses the Azurewave AW-CM276NF Wi-Fi module based on the NXP 88W8997 chipset (1).

Known Driver Limitations

The documentation indicates that there are some use case limitations with the mainline driver used in BSP releases (1). Specifically:

  • Some use cases don’t work with the mainline Marvell WiFi-Ex driver included in BSP 5 and later versions (1)
  • The driver included is the Marvell WiFi-Ex driver from Mainline Linux kernel along with its corresponding firmware (1)
  • Downstream NXP drivers have been tested and seem to work well for some use cases that are not supported by the mainline driver (1)

Potential Hardware-Related Considerations

Your observation about power cycling being necessary suggests a potential hardware state issue. The Verdin iMX8M Mini Errata documents a related issue where Wi-Fi module power rails cannot be turned off properly (2). While this specific errata is for the Mini variant, similar power management issues could affect the Plus variant.

The errata states that after booting, you should turn on the power rails for the Wi-Fi and Bluetooth module only if the radio is required and keep the rails turned on or reboot the system if the rails need to be turned off again (2).

Recommended Troubleshooting Steps

  1. Check driver logs during disconnection events using dmesg to identify specific error patterns
  2. Monitor Wi-Fi module power state during software reboots vs. power cycles
  3. Consider testing with downstream NXP drivers if the mainline driver continues to exhibit issues (1)

Additional Context

Community reports show similar Wi-Fi subsystem issues where the mwifiex_sdio driver can experience command timeout errors and bridge packet limit issues, particularly under heavy network load scenarios (3).

Since you’re using a custom Yocto build with BSP 7.2.0, the issue appears to be related to the driver’s ability to properly reinitialize the Wi-Fi hardware state during software reboot compared to a full power cycle reset.

Best regards, Toradex AI Assistant.

Hello @josiassas !

To better understand your issue and narrow down the root cause, could you please provide us with the following information:

  • The output of dmesg right after the disconnection and after a failed software reboot.
  • Logs from the network manager in use (NetworkManager or connman) around the time of failure.
  • Whether the connection is on 2.4GHz or 5GHz, and if enterprise authentication is required.
  • As an additional test, instead of rebooting Linux, could you try resetting only the Wi-Fi interface when the issue occurs?

Finally, to help isolate whether the issue is related to your Yocto build, we would also ask you to test with our TorizonCore 7 (without custom layers) on one of your devices.

All of this will clarify if the problem persists on our validated image or if it might be linked to your custom build.

Unfortunately, I was not able to collect the dmesg output after the disconnections, since the errors only occurred with the Verdin device installed in the field, where I do not have physical access to retrieve the logs via wired network or debug UART.

The connection is on 2.4GHz, and enterprise authentication is not required.

What I did, which apparently prevented the device from disconnecting, was to implement a service that disabling Wi-Fi power save mode after boot:

/sbin/iw dev mlan0 set power_save off

In parallel, I requested our IT team to analyze the hardware and network conditions. Their preliminary report indicates the following:

  • The WLC analysis shows that the device presents signal parameters within the expected standards for proper operation.
  • The association history indicates that, between 25/08 and 28/08, the device has alternated connections between four different Access Points: APFIA01L-03, APFIAR04H-12, APFIAR04H-05, APFIAR04H-03.
  • Most of the connections occur in the area covered by rack BRFIAR04H. However, a high rate of disconnections and reconnections has been observed, with frequent roaming between these APs, which may indicate excessive roaming or instability at the wireless layer.
  • Validation confirmed that the APs are properly configured, and the SSID FG-PROD-04 is correctly associated with the AP-Group for all three devices, being propagated as expected.

Additional notes:

  • If the device is stationary in a single location, the roaming aggressiveness settings on the device should be verified, as constant migration between APs was observed within short intervals.
  • If the device is mobile, this behavior of multiple associations/disassociations may be expected due to natural client movement within the Wi-Fi coverage area.

Could you please provide support in analyzing this behavior and confirming whether there is any configuration adjustment or firmware update required to mitigate this issue?

Unfortunately, without kernel or network manager logs, there isn’t much we can do to properly identify the root cause of the disconnections. Knowing which APs or racks the device roams between is not enough for us to determine whether the issue lies in the Wi-Fi firmware/driver or in the network configuration.

Since your devices are connected to the cloud, you should be able to SSH into the affected modules remotely. From there, you can retrieve the relevant logs at the time of failure. Having these logs will give us a much clearer picture of what is happening at the driver and kernel level, and allow us to move forward with actionable analysis.

Please try to collect and share these logs on the next occurrence, so we can investigate further.

Here is the dmesg log.

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.6.84-7.2.0-devel-g87bfb710b6f1 (oe-user@oe-host) (aarch64-tdx-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1-Torizon SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
[    0.000000] KASLR disabled due to lack of seed
[    0.000000] Machine model: Toradex Verdin iMX8M Plus WB on Verdin Development Board
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000a0000000, size 512 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a0000000..0x00000000bfffffff (524288 KiB) map reusable linux,cma
[    0.000000] OF: reserved mem: 0x0000000000900000..0x000000000096ffff (448 KiB) nomap non-reusable ocram@900000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000013fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x000000013fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000013fffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.4
[    0.000000] percpu: Embedded 29 pages/cpu s80040 r8192 d30552 u118784
[    0.000000] pcpu-alloc: s80040 r8192 d30552 u118784 alloc=29*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/25e793cfce8d75f3366d0cbdf086cb12815074ce489eb19ef74a74eded8be9af/0
[    0.000000] Unknown kernel command line parameters "splash ostree=/ostree/boot.1/torizon/25e793cfce8d75f3366d0cbdf086cb12815074ce489eb19ef74a74eded8be9af/0", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1032192
[    0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    0.000000] software IO TLB: area num 4.
[    0.000000] software IO TLB: mapped [mem 0x00000000faa90000-0x00000000fea90000] (64MB)
[    0.000000] Memory: 3480048K/4194304K available (15680K kernel code, 2966K rwdata, 6292K rodata, 4352K init, 605K bss, 189968K reserved, 524288K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU event tracing is enabled.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000] 	Trampoline variant of Tasks RCU enabled.
[    0.000000] 	Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 160 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: GICv3 features: 16 PPIs
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000000] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.000577] Console: colour dummy device 80x25
[    0.000587] printk: console [tty0] enabled
[    0.000665] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=80000)
[    0.000679] pid_max: default: 32768 minimum: 301
[    0.000807] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.000825] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.002320] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    0.002392] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    0.002578] rcu: Hierarchical SRCU implementation.
[    0.002583] rcu: 	Max phase no-delay instances is 1000.
[    0.003667] EFI services will not be available.
[    0.003955] smp: Bringing up secondary CPUs ...
[    0.004430] Detected VIPT I-cache on CPU1
[    0.004488] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.004525] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.005051] Detected VIPT I-cache on CPU2
[    0.005093] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.005114] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.005600] Detected VIPT I-cache on CPU3
[    0.005642] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.005660] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.005733] smp: Brought up 1 node, 4 CPUs
[    0.005746] SMP: Total of 4 processors activated.
[    0.005754] CPU features: detected: 32-bit EL0 Support
[    0.005758] CPU features: detected: CRC32 instructions
[    0.005813] CPU: All CPU(s) started at EL2
[    0.005817] alternatives: applying system-wide alternatives
[    0.007589] devtmpfs: initialized
[    0.019705] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.019729] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.033431] pinctrl core: initialized pinctrl subsystem
[    0.034533] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.035356] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[    0.035505] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.035700] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.036192] thermal_sys: Registered thermal governor 'step_wise'
[    0.036197] thermal_sys: Registered thermal governor 'user_space'
[    0.036201] thermal_sys: Registered thermal governor 'power_allocator'
[    0.036240] cpuidle: using governor menu
[    0.036404] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.036483] ASID allocator initialised with 65536 entries
[    0.036718] Serial: AMBA PL011 UART driver
[    0.036774] imx mu driver is registered.
[    0.036799] imx rpmsg driver is registered.
[    0.046115] /soc@0: Fixed dependency cycle(s) with /soc@0/bus@30000000/efuse@30350000/unique-id@8
[    0.046603] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.046629] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /hdmi-connector
[    0.046933] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[    0.046973] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a50000/hdmi@48
[    0.047051] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.047332] /soc@0/bus@30c00000/lcd-controller@32fc6000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/hdmi@32fd8000
[    0.047430] /soc@0/bus@30c00000/hdmi@32fd8000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/lcd-controller@32fc6000
[    0.047549] /soc@0/interrupt-controller@38800000: Fixed dependency cycle(s) with /soc@0/interrupt-controller@38800000
[    0.049760] /soc@0/bus@30000000/pinctrl@30330000: Fixed dependency cycle(s) with /soc@0/bus@30000000/pinctrl@30330000/gpio-qspi-pins
[    0.050332] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.050971] /soc@0/bus@30000000/efuse@30350000: Fixed dependency cycle(s) with /soc@0/bus@30000000/clock-controller@30380000
[    0.052114] /soc@0/bus@30000000/efuse@30350000: Fixed dependency cycle(s) with /soc@0/bus@30000000/clock-controller@30380000
[    0.055029] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.055058] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /hdmi-connector
[    0.058559] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.058588] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /hdmi-connector
[    0.061120] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[    0.061163] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a50000/hdmi@48
[    0.061283] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.061537] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.061628] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[    0.061663] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a50000/hdmi@48
[    0.061893] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/lcd-controller@32e80000
[    0.061998] /soc@0/bus@32c00000/lcd-controller@32e80000: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    0.063890] /soc@0/bus@30c00000/lcd-controller@32fc6000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/hdmi@32fd8000
[    0.063973] /soc@0/bus@30c00000/hdmi@32fd8000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/lcd-controller@32fc6000
[    0.066154] /soc@0/bus@30c00000/lcd-controller@32fc6000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/hdmi@32fd8000
[    0.066512] /soc@0/bus@30c00000/lcd-controller@32fc6000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/hdmi@32fd8000
[    0.066612] /soc@0/bus@30c00000/hdmi@32fd8000: Fixed dependency cycle(s) with /soc@0/bus@30c00000/lcd-controller@32fc6000
[    0.074485] Modules: 25264 pages in range for non-PLT usage
[    0.074497] Modules: 516784 pages in range for PLT usage
[    0.075264] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.075275] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.075281] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.075285] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.075292] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.075299] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.075306] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.075312] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.075771] cryptd: max_cpu_qlen set to 1000
[    0.077941] iommu: Default domain type: Translated
[    0.077949] iommu: DMA domain TLB invalidation policy: strict mode
[    0.078286] SCSI subsystem initialized
[    0.078542] libata version 3.00 loaded.
[    0.078718] usbcore: registered new interface driver usbfs
[    0.078749] usbcore: registered new interface driver hub
[    0.078782] usbcore: registered new device driver usb
[    0.080059] mc: Linux media interface: v0.10
[    0.080095] videodev: Linux video capture interface: v2.00
[    0.080162] pps_core: LinuxPPS API ver. 1 registered
[    0.080167] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.080184] PTP clock support registered
[    0.080465] scmi_core: SCMI protocol bus registered
[    0.080779] Advanced Linux Sound Architecture Driver Initialized.
[    0.081548] Bluetooth: Core ver 2.22
[    0.081572] NET: Registered PF_BLUETOOTH protocol family
[    0.081579] Bluetooth: HCI device and connection manager initialized
[    0.081586] Bluetooth: HCI socket layer initialized
[    0.081592] Bluetooth: L2CAP socket layer initialized
[    0.081604] Bluetooth: SCO socket layer initialized
[    0.082405] clocksource: Switched to clocksource arch_sys_counter
[    0.082717] VFS: Disk quotas dquot_6.6.0
[    0.082747] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.090324] NET: Registered PF_INET protocol family
[    0.090503] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.093366] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    0.093411] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.093423] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.093636] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    0.094536] TCP: Hash tables configured (established 32768 bind 32768)
[    0.094642] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.094734] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.094964] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.095341] RPC: Registered named UNIX socket transport module.
[    0.095348] RPC: Registered udp transport module.
[    0.095351] RPC: Registered tcp transport module.
[    0.095355] RPC: Registered tcp-with-tls transport module.
[    0.095358] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.095369] PCI: CLS 0 bytes, default 64
[    0.095683] Trying to unpack rootfs image as initramfs...
[    0.785703] Freeing initrd memory: 12820K
[    0.872506] Initialise system trusted keyrings
[    0.872716] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    0.873202] NFS: Registering the id_resolver key type
[    0.873239] Key type id_resolver registered
[    0.873246] Key type id_legacy registered
[    0.873263] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.873268] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.907214] NET: Registered PF_ALG protocol family
[    0.907230] Key type asymmetric registered
[    0.907235] Asymmetric key parser 'x509' registered
[    0.907272] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.907379] io scheduler mq-deadline registered
[    0.907385] io scheduler kyber registered
[    0.907407] io scheduler bfq registered
[    0.920815] mxs-dma 33000000.dma-apbh: initialized
[    0.921611] SoC: i.MX8MP revision 1.1
[    0.922004] Bus freq driver module loaded
[    0.980408] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
[    0.984480] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 15, base_baud = 1500000) is a IMX
[    0.985270] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 16, base_baud = 1500000) is a IMX
[    0.985288] imx-uart 30880000.serial: Console IMX rounded baud rate from 114286 to 114300
[    0.985318] printk: console [ttymxc2] enabled
[    0.986248] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 17, base_baud = 1500000) is a IMX
[    0.986974] 30a60000.serial: ttymxc3 at MMIO 0x30a60000 (irq = 18, base_baud = 1500000) is a IMX
[    0.987113] serial serial0: tty port ttymxc3 registered
[    1.004744] brd: module loaded
[    1.009404] loop: module loaded
[    1.009867] zram: Added device: zram0
[    1.014838] usbcore: registered new interface driver usb-storage
[    1.014906] usbcore: registered new interface driver usbserial_generic
[    1.014932] usbserial: USB Serial support registered for generic
[    1.015547] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.017204] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc1
[    1.017369] i2c_dev: i2c /dev entries driver
[    1.022106] sdhci: Secure Digital Host Controller Interface driver
[    1.022118] sdhci: Copyright(c) Pierre Ossman
[    1.022422] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.025374] ledtrig-cpu: registered to indicate activity on CPUs
[    1.026260] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.027380] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9)
[    1.027398] caam 30900000.crypto: job rings = 2, qi = 0
[    1.032998] caam algorithms registered in /proc/crypto
[    1.033160] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.033183] caam 30900000.crypto: rng crypto API alg registered prng-caam
[    1.033193] caam 30900000.crypto: registering rng-caam
[    1.036031] Device caam-keygen registered
[    1.038350] hid: raw HID events driver (C) Jiri Kosina
[    1.038470] usbcore: registered new interface driver usbhid
[    1.038476] usbhid: USB HID core driver
[    1.039884] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    1.041170]  cs_system_cfg: CoreSight Configuration manager initialised
[    1.042139] /soc@0: Fixed dependency cycle(s) with /soc@0/bus@30000000/efuse@30350000
[    1.045045] hantrodec 0 : module inserted. Major = 239
[    1.045530] hantrodec 1 : module inserted. Major = 239
[    1.045948] random: crng init done
[    1.046412] hantroenc: HW at base <0000000038320000> with ID <0x80006200>
[    1.046543] hx280enc: module inserted. Major <238>
[    1.047769] usbcore: registered new interface driver snd-usb-audio
[    1.049269] NET: Registered PF_INET6 protocol family
[    1.050239] Segment Routing with IPv6
[    1.050265] In-situ OAM (IOAM) with IPv6
[    1.050328] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    1.050786] NET: Registered PF_PACKET protocol family
[    1.050807] Key type dns_resolver registered
[    1.050935] NET: Registered PF_VSOCK protocol family
[    1.058155] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.060252] registered taskstats version 1
[    1.060369] Loading compiled-in X.509 certificates
[    1.066504] Key type .fscrypt registered
[    1.066518] Key type fscrypt-provisioning registered
[    1.079408] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.081126] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.082505] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.084713] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.086490] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.089073] reg-fixed-voltage regulator-force-sleep-moci: nonexclusive access to GPIO for (null)
[    1.090863] i2c i2c-0: using pinctrl states for GPIO recovery
[    1.093985] rtc-ds1307 0-0032: registered as rtc0
[    1.095164] rtc-ds1307 0-0032: setting system clock to 2025-08-29T12:08:54 UTC (1756469334)
[    1.095781] at24 0-0050: supply vcc not found, using dummy regulator
[    1.096404] at24 0-0050: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[    1.096446] i2c i2c-0: IMX I2C adapter registered
[    1.097462] i2c i2c-1: using pinctrl states for GPIO recovery
[    1.097580] i2c i2c-1: IMX I2C adapter registered
[    1.098378] i2c i2c-2: using pinctrl states for GPIO recovery
[    1.098419] i2c i2c-2: IMX I2C adapter registered
[    1.099240] i2c i2c-3: using pinctrl states for GPIO recovery
[    1.099710] pca953x 3-0021: using no AI
[    1.099949] pca953x 3-0021: failed writing register
[    1.105493] /soc@0/bus@32c00000/mipi_dsi@32e60000: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a50000/hdmi@48
[    1.105577] /hdmi-connector: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a50000/hdmi@48
[    1.105718] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /soc@0/bus@32c00000/mipi_dsi@32e60000
[    1.105793] /soc@0/bus@30800000/i2c@30a50000/hdmi@48: Fixed dependency cycle(s) with /hdmi-connector
[    1.106371] at24 3-0050: supply vcc not found, using dummy regulator
[    1.106738] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.107339] mmcblk2: mmc2:0001 IX2932 29.1 GiB
[    1.107487] at24 3-0050: 256 byte 24c02 EEPROM, writable, 16 bytes/write
[    1.107754] at24 3-0057: supply vcc not found, using dummy regulator
[    1.108648] nxp-pca9450 0-0025: pca9450bc probed.
[    1.108740]  mmcblk2: p1
[    1.109211] mmcblk2boot0: mmc2:0001 IX2932 4.00 MiB
[    1.110171] mmcblk2boot1: mmc2:0001 IX2932 4.00 MiB
[    1.111016] mmcblk2rpmb: mmc2:0001 IX2932 4.00 MiB, chardev (242:0)
[    1.136103] i2c i2c-3: IMX I2C adapter registered
[    1.147923] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 7 mkt segment 2 supported-hw 0x80 0x4
[    1.151992] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.156871] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[    1.157364] clk: Disabling unused clocks
[    1.161194] ALSA device list:
[    1.161205]   No soundcards found.
[    1.183041] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA
[    1.263294] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    1.294013] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.364398] Freeing unused kernel memory: 4352K
[    1.364527] Run /init as init process
[    1.364534]   with arguments:
[    1.364540]     /init
[    1.364544]     splash
[    1.364549]   with environment:
[    1.364553]     HOME=/
[    1.364558]     TERM=linux
[    1.364562]     ostree=/ostree/boot.1/torizon/25e793cfce8d75f3366d0cbdf086cb12815074ce489eb19ef74a74eded8be9af/0

Continuation

[    1.364958] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found
[    1.366371] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51
[    1.366399] imx-dwmac 30bf0000.ethernet: 	DWMAC4/5
[    1.366411] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported
[    1.366418] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported
[    1.366425] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported
[    1.366503] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    1.366513] imx-dwmac 30bf0000.ethernet: Enabled L3L4 Flow TC (entries=8)
[    1.366532] imx-dwmac 30bf0000.ethernet: Enabled RFS Flow TC (entries=10)
[    1.366551] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256)
[    1.366567] imx-dwmac 30bf0000.ethernet: Using 34/40 bits DMA host/device width
[    1.559704] Kernel module loaded from ramdisk: sec_dsim - result: 0
[    1.566475] Kernel module loaded from ramdisk: display_connector - result: 0
[    1.572622] Kernel module loaded from ramdisk: sec_mipi_dsim_imx - result: 0
[    1.577484] Kernel module loaded from ramdisk: ti_sn65dsi83 - result: 0
[    1.582090] lt8912 3-0048: supply vccmipirx not found, using dummy regulator
[    1.582194] lt8912 3-0048: supply vccsysclk not found, using dummy regulator
[    1.582245] lt8912 3-0048: supply vcclvdstx not found, using dummy regulator
[    1.582288] lt8912 3-0048: supply vcchdmitx not found, using dummy regulator
[    1.582329] lt8912 3-0048: supply vcclvdspll not found, using dummy regulator
[    1.582374] lt8912 3-0048: supply vcchdmipll not found, using dummy regulator
[    1.583499] Kernel module loaded from ramdisk: lontium_lt8912b - result: 0
[    2.179609] EXT4-fs (mmcblk2p1): mounted filesystem 603c27d0-175f-4441-b59a-f11181e7bb29 r/w with ordered data mode. Quota mode: none.
[    2.491410] systemd[1]: systemd 255.17^ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    2.491438] systemd[1]: Detected architecture arm64.
[    2.495578] systemd[1]: Hostname set to <verdin-imx8mp-15503049>.
[    2.558803] systemd[1]: Using hardware watchdog 'imx2+ watchdog', version 0, device /dev/watchdog0
[    2.558840] systemd[1]: Watchdog running with a hardware timeout of 30s.
[    3.969440] systemd[1]: Queued start job for default target Multi-User System.
[    4.029508] systemd[1]: Created slice Slice /system/getty.
[    4.031387] systemd[1]: Created slice Slice /system/modprobe.
[    4.033158] systemd[1]: Created slice Slice /system/serial-getty.
[    4.034524] systemd[1]: Created slice User and Session Slice.
[    4.034797] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    4.034997] systemd[1]: Reached target Remote File Systems.
[    4.035054] systemd[1]: Reached target Slice Units.
[    4.035128] systemd[1]: Reached target Swaps.
[    4.053089] systemd[1]: Listening on RPCbind Server Activation Socket.
[    4.053279] systemd[1]: Reached target RPC Port Mapper.
[    4.053689] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    4.060766] systemd[1]: Journal Audit Socket was skipped because of an unmet condition check (ConditionSecurity=audit).
[    4.061495] systemd[1]: Listening on Journal Socket (/dev/log).
[    4.062069] systemd[1]: Listening on Journal Socket.
[    4.062925] systemd[1]: Listening on Network Service Netlink Socket.
[    4.068059] systemd[1]: Listening on udev Control Socket.
[    4.068564] systemd[1]: Listening on udev Kernel Socket.
[    4.069050] systemd[1]: Listening on User Database Manager Socket.
[    4.073831] systemd[1]: Mounting Huge Pages File System...
[    4.077749] systemd[1]: Mounting POSIX Message Queue File System...
[    4.082286] systemd[1]: Mounting Kernel Debug File System...
[    4.089883] systemd[1]: Mounting Kernel Trace File System...
[    4.102821] systemd[1]: Mounting Temporary Directory /tmp...
[    4.108090] systemd[1]: Starting Create List of Static Device Nodes...
[    4.111890] systemd[1]: Starting Load Kernel Module configfs...
[    4.122234] systemd[1]: Starting Load Kernel Module drm...
[    4.127629] systemd[1]: Starting Load Kernel Module fuse...
[    4.128084] systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
[    4.138485] systemd[1]: Starting Journal Service...
[    4.145072] systemd[1]: Starting Load Kernel Modules...
[    4.150932] systemd[1]: Starting Generate network units from Kernel command line...
[    4.162645] systemd[1]: Starting Remount Root and Kernel File Systems...
[    4.168571] systemd[1]: Starting Wait Until Kernel Time Synchronized...
[    4.173964] systemd[1]: Starting Coldplug All udev Devices...
[    4.176513] fuse: init (API version 7.39)
[    4.189091] systemd[1]: Starting Virtual Console Setup...
[    4.195378] systemd[1]: Mounted Huge Pages File System.
[    4.196206] systemd[1]: Mounted POSIX Message Queue File System.
[    4.196934] systemd[1]: Mounted Kernel Debug File System.
[    4.197530] systemd[1]: Mounted Kernel Trace File System.
[    4.198125] systemd[1]: Mounted Temporary Directory /tmp.
[    4.199304] systemd[1]: Finished Create List of Static Device Nodes.
[    4.200335] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[    4.200852] systemd[1]: Finished Load Kernel Module configfs.
[    4.201803] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    4.202323] systemd[1]: Finished Load Kernel Module drm.
[    4.204008] systemd[1]: modprobe@fuse.service: Deactivated successfully.
[    4.204597] systemd[1]: Finished Load Kernel Module fuse.
[    4.209853] systemd[1]: Mounting FUSE Control File System...
[    4.217295] galcore: loading out-of-tree module taints kernel.
[    4.235170] module built by  at Tue Jul 15 22:44:46 UTC 2025
[    4.235680] systemd[1]: Mounting Kernel Configuration File System...
[    4.241365] Galcore version 6.4.11.p2.745085
[    4.246302] systemd-journald[387]: Collecting audit messages is disabled.
[    4.248999] systemd[1]: Starting Create Static Device Nodes in /dev gracefully...
[    4.253201] systemd[1]: Finished Generate network units from Kernel command line.
[    4.254904] systemd[1]: Mounted FUSE Control File System.
[    4.256904] systemd[1]: Mounted Kernel Configuration File System.
[    4.273270] EXT4-fs (mmcblk2p1): re-mounted 603c27d0-175f-4441-b59a-f11181e7bb29 r/w. Quota mode: none.
[    4.278728] systemd[1]: Finished Remount Root and Kernel File Systems.
[    4.280409] systemd[1]: Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc).
[    4.307641] systemd[1]: Started Journal Service.
[    4.342329] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0
[    4.375500] openvswitch: Open vSwitch switching datapath
[    4.898139] systemd-journald[387]: Received client request to flush runtime journal.
[    5.537191] imx-dwmac 30bf0000.ethernet ethernet0: renamed from eth0
[    6.190266] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.203027] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.204481] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    6.356887] Hot alarm is canceled. GPU3D clock will return to 64/64
[    6.447458] CAN device driver interface
[    6.574103] imx-bus-devfreq 32700000.interconnect: failed to fetch clk: -2
[    6.581033] imx-bus-devfreq: probe of 32700000.interconnect failed with error -2
[    6.582283] imx-sdma 30bd0000.dma-controller: firmware found.
[    6.582665] imx-sdma 30bd0000.dma-controller: loaded firmware 4.6
[    6.603768] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    6.610149] imx-sdma 30e00000.dma-controller: firmware found.
[    6.614489] nau8822 3-001a: Failed to issue reset: -6
[    6.624563] imx-sdma 30e10000.dma-controller: firmware found.
[    6.684333] hwmon hwmon2: temp1_input not attached to any thermal zone
[    6.684354] lm75 0-0048: hwmon2: sensor 'tmp1075'
[    6.684875] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2)
[    6.686247] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver
[    6.779769] ina2xx 3-0040: supply vs not found, using dummy regulator
[    6.784724] ina2xx 3-0040: power monitor ina219 (Rshunt = 10000 uOhm)
[    6.785490] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[    6.785560] imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops)
[    6.785801] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
[    6.785853] imx_sec_dsim_drv 32e60000.mipi_dsi: [drm] *ERROR* modalias failure on /soc@0/bus@32c00000/mipi_dsi@32e60000/port@1
[    6.804015] imx8mq-usb-phy 381f0040.usb-phy: supply vbus not found, using dummy regulator
[    6.833632] Bluetooth: HCI UART driver ver 2.3
[    6.833650] Bluetooth: HCI UART protocol H4 registered
[    6.833655] Bluetooth: HCI UART protocol BCSP registered
[    6.833742] Bluetooth: HCI UART protocol LL registered
[    6.833748] Bluetooth: HCI UART protocol ATH3K registered
[    6.833782] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.834024] Bluetooth: HCI UART protocol Intel registered
[    6.834274] Bluetooth: HCI UART protocol Broadcom registered
[    6.834317] Bluetooth: HCI UART protocol QCA registered
[    6.834378] Bluetooth: HCI UART protocol Marvell registered
[    6.863493] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops [sec_mipi_dsim_imx])
[    6.863632] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops)
[    6.864211] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1
[    7.017513] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device
[    7.051330] imx-dwmac 30bf0000.ethernet ethernet0: Register MEM_TYPE_PAGE_POOL RxQ-0
[    7.051742] imx-dwmac 30bf0000.ethernet ethernet0: Register MEM_TYPE_PAGE_POOL RxQ-1
[    7.052149] imx-dwmac 30bf0000.ethernet ethernet0: Register MEM_TYPE_PAGE_POOL RxQ-2
[    7.053250] imx-dwmac 30bf0000.ethernet ethernet0: Register MEM_TYPE_PAGE_POOL RxQ-3
[    7.053654] imx-dwmac 30bf0000.ethernet ethernet0: Register MEM_TYPE_PAGE_POOL RxQ-4
[    7.069803] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    7.069843] imx6q-pcie 33800000.pcie:       IO 0x001ff80000..0x001ff8ffff -> 0x0000000000
[    7.069860] imx6q-pcie 33800000.pcie:      MEM 0x0018000000..0x001fefffff -> 0x0018000000
[    7.137647] imx-dwmac 30bf0000.ethernet ethernet0: PHY [stmmac-0:07] driver [Microchip KSZ9131 Gigabit PHY] (irq=43)
[    7.151533] imx-dwmac 30bf0000.ethernet ethernet0: No Safety Features support found
[    7.151574] imx-dwmac 30bf0000.ethernet ethernet0: IEEE 1588-2008 Advanced Timestamp supported
[    7.151790] imx-dwmac 30bf0000.ethernet ethernet0: registered PTP clock
[    7.196632] imx-dwmac 30bf0000.ethernet ethernet0: FPE workqueue start
[    7.196653] imx-dwmac 30bf0000.ethernet ethernet0: configuring for phy/rgmii-id link mode
[    7.302633] imx6q-pcie 33800000.pcie: iATU: unroll T, 4 ob, 4 ib, align 64K, limit 16G
[    7.717350] mwifiex_sdio mmc0:0001:1: info: FW download over, size 624880 bytes
[    7.826118] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.826138] Bluetooth: BNEP filters: protocol multicast
[    7.826152] Bluetooth: BNEP socket layer initialized
[    8.302488] imx6q-pcie 33800000.pcie: Phy link never came up
[    8.552468] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[    8.607723] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x81
[    8.607843] mwifiex_sdio mmc0:0001:1: Unknown GET_HW_SPEC TLV type: 0x23e
[    8.622913] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.92.21.p137) 
[    8.622933] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (16.92.21.p137) 
[    9.302510] imx6q-pcie 33800000.pcie: Phy link never came up
[    9.302964] imx6q-pcie 33800000.pcie: PCI host bridge to bus 0000:00
[    9.302981] pci_bus 0000:00: root bus resource [bus 00-ff]
[    9.302991] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    9.302999] pci_bus 0000:00: root bus resource [mem 0x18000000-0x1fefffff]
[    9.303031] pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
[    9.303048] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
[    9.303062] pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
[    9.303114] pci 0000:00:00.0: supports D1
[    9.303122] pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
[    9.306582] pci 0000:00:00.0: BAR 0: assigned [mem 0x18000000-0x180fffff]
[    9.306608] pci 0000:00:00.0: BAR 6: assigned [mem 0x18100000-0x1810ffff pref]
[    9.306619] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    9.307075] pcieport 0000:00:00.0: PME: Signaling with IRQ 230
[    9.307372] pcieport 0000:00:00.0: AER: enabled with IRQ 230
[    9.314998] Bluetooth: MGMT ver 1.22
[    9.328263] dwc3 38100000.usb: UDC doesn't support SSP
[    9.329908] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card0/input2
[    9.330034] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    9.330055] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
[    9.330406] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe65 hci version 0x110 quirks 0x000000a001000010
[    9.330461] xhci-hcd xhci-hcd.1.auto: irq 231, io mem 0x38100000
[    9.330618] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    9.330633] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
[    9.330650] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
[    9.330964] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    9.330979] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.330985] usb usb1: Product: xHCI Host Controller
[    9.330990] usb usb1: Manufacturer: Linux 6.6.84-7.2.0-devel-g87bfb710b6f1 xhci-hcd
[    9.330995] usb usb1: SerialNumber: xhci-hcd.1.auto
[    9.334206] hub 1-0:1.0: USB hub found
[    9.334257] hub 1-0:1.0: 1 port detected
[    9.338795] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    9.338890] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    9.338900] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.338906] usb usb2: Product: xHCI Host Controller
[    9.338911] usb usb2: Manufacturer: Linux 6.6.84-7.2.0-devel-g87bfb710b6f1 xhci-hcd
[    9.338916] usb usb2: SerialNumber: xhci-hcd.1.auto
[    9.339664] hub 2-0:1.0: USB hub found
[    9.339704] hub 2-0:1.0: 1 port detected
[    9.349896] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    9.349924] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3
[    9.350279] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220fe65 hci version 0x110 quirks 0x000000a001000010
[    9.350332] xhci-hcd xhci-hcd.2.auto: irq 232, io mem 0x38200000
[    9.350482] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    9.350498] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4
[    9.350514] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0 SuperSpeed
[    9.350651] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    9.350661] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.350667] usb usb3: Product: xHCI Host Controller
[    9.350672] usb usb3: Manufacturer: Linux 6.6.84-7.2.0-devel-g87bfb710b6f1 xhci-hcd
[    9.350677] usb usb3: SerialNumber: xhci-hcd.2.auto
[    9.351143] hub 3-0:1.0: USB hub found
[    9.351178] hub 3-0:1.0: 1 port detected
[    9.351565] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    9.351652] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    9.351660] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.351666] usb usb4: Product: xHCI Host Controller
[    9.351671] usb usb4: Manufacturer: Linux 6.6.84-7.2.0-devel-g87bfb710b6f1 xhci-hcd
[    9.351676] usb usb4: SerialNumber: xhci-hcd.2.auto
[    9.352200] hub 4-0:1.0: USB hub found
[    9.352233] hub 4-0:1.0: 1 port detected
[    9.632420] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    9.632435] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    9.812941] usb 1-1: New USB device found, idVendor=0424, idProduct=2744, bcdDevice= 2.21
[    9.812962] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    9.812970] usb 1-1: Product: USB2744
[    9.812977] usb 1-1: Manufacturer: Microchip Tech
[    9.812993] usb 3-1: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01
[    9.813005] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    9.813013] usb 3-1: Product: Movidius MyriadX
[    9.813019] usb 3-1: Manufacturer: Movidius Ltd.
[    9.813025] usb 3-1: SerialNumber: 03e72485
[    9.874961] hub 1-1:1.0: USB hub found
[    9.875037] hub 1-1:1.0: 4 ports detected
[    9.956853] usbcore: registered new device driver onboard-usb-hub
[    9.970707] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[    9.992841] usb 2-1: New USB device found, idVendor=0424, idProduct=5744, bcdDevice= 2.21
[    9.992858] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[    9.992866] usb 2-1: Product: USB5744
[    9.992874] usb 2-1: Manufacturer: Microchip Tech
[   10.018972] hub 2-1:1.0: USB hub found
[   10.019050] hub 2-1:1.0: 3 ports detected
[   10.066976] hub 2-1:1.0: USB hub found
[   10.067043] hub 2-1:1.0: 3 ports detected
[   10.226979] hub 1-1:1.0: USB hub found
[   10.227044] hub 1-1:1.0: 4 ports detected
[   10.386949] hub 1-1:1.0: USB hub found
[   10.387018] hub 1-1:1.0: 4 ports detected
[   10.610957] hub 2-1:1.0: USB hub found
[   10.611012] hub 2-1:1.0: 3 ports detected
[   10.772440] usb 1-1.4: new high-speed USB device number 3 using xhci-hcd
[   10.903099] usb 1-1.4: New USB device found, idVendor=0424, idProduct=2740, bcdDevice= 2.00
[   10.903118] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.903126] usb 1-1.4: Product: Hub Controller
[   10.903132] usb 1-1.4: Manufacturer: Microchip Tech

Continuation

[   13.076228] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[   13.081185] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[   13.084445] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[   14.355416] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   14.357505] Bridge firewalling registered
[   14.502624] Initializing XFRM netlink socket
[   21.148485] platform sound: deferred probe pending
[   21.148503] platform 30be0000.ethernet: deferred probe pending
[   21.148508] platform regulator-eth2phy: deferred probe pending
[   23.500962] br-52843f9ca546: port 1(vetha72f6de) entered blocking state
[   23.501004] br-52843f9ca546: port 1(vetha72f6de) entered disabled state
[   23.501038] vetha72f6de: entered allmulticast mode
[   23.503047] vetha72f6de: entered promiscuous mode
[   23.503483] br-52843f9ca546: port 1(vetha72f6de) entered blocking state
[   23.503506] br-52843f9ca546: port 1(vetha72f6de) entered forwarding state
[   23.503685] br-52843f9ca546: port 1(vetha72f6de) entered disabled state
[   23.526044] br-52843f9ca546: port 2(veth7977710) entered blocking state
[   23.526069] br-52843f9ca546: port 2(veth7977710) entered disabled state
[   23.526108] veth7977710: entered allmulticast mode
[   23.526838] veth7977710: entered promiscuous mode
[   23.527603] br-52843f9ca546: port 2(veth7977710) entered blocking state
[   23.527624] br-52843f9ca546: port 2(veth7977710) entered forwarding state
[   23.531212] br-52843f9ca546: port 2(veth7977710) entered disabled state
[   23.606476] br-52843f9ca546: port 3(veth0ac1cb9) entered blocking state
[   23.606501] br-52843f9ca546: port 3(veth0ac1cb9) entered disabled state
[   23.606545] veth0ac1cb9: entered allmulticast mode
[   23.606811] veth0ac1cb9: entered promiscuous mode
[   23.607170] br-52843f9ca546: port 3(veth0ac1cb9) entered blocking state
[   23.607195] br-52843f9ca546: port 3(veth0ac1cb9) entered forwarding state
[   23.630907] br-52843f9ca546: port 4(vethdbf31d5) entered blocking state
[   23.630948] br-52843f9ca546: port 4(vethdbf31d5) entered disabled state
[   23.630994] vethdbf31d5: entered allmulticast mode
[   23.631226] vethdbf31d5: entered promiscuous mode
[   23.631695] br-52843f9ca546: port 4(vethdbf31d5) entered blocking state
[   23.631717] br-52843f9ca546: port 4(vethdbf31d5) entered forwarding state
[   23.922477] br-52843f9ca546: port 3(veth0ac1cb9) entered disabled state
[   23.922685] br-52843f9ca546: port 4(vethdbf31d5) entered disabled state
[   24.570732] eth0: renamed from veth2d551e2
[   24.671166] br-52843f9ca546: port 1(vetha72f6de) entered blocking state
[   24.671191] br-52843f9ca546: port 1(vetha72f6de) entered forwarding state
[   24.804243] eth0: renamed from vethc253b5a
[   24.852577] br-52843f9ca546: port 2(veth7977710) entered blocking state
[   24.852602] br-52843f9ca546: port 2(veth7977710) entered forwarding state
[   24.963197] eth0: renamed from veth6f44f5c
[   25.047815] br-52843f9ca546: port 4(vethdbf31d5) entered blocking state
[   25.047840] br-52843f9ca546: port 4(vethdbf31d5) entered forwarding state
[   25.124486] eth0: renamed from veth318a0ac
[   25.170381] br-52843f9ca546: port 5(veth06433b4) entered blocking state
[   25.170426] br-52843f9ca546: port 5(veth06433b4) entered disabled state
[   25.170470] veth06433b4: entered allmulticast mode
[   25.170806] veth06433b4: entered promiscuous mode
[   25.172842] br-52843f9ca546: port 5(veth06433b4) entered blocking state
[   25.172870] br-52843f9ca546: port 5(veth06433b4) entered forwarding state
[   25.174251] br-52843f9ca546: port 5(veth06433b4) entered disabled state
[   25.174588] br-52843f9ca546: port 3(veth0ac1cb9) entered blocking state
[   25.174613] br-52843f9ca546: port 3(veth0ac1cb9) entered forwarding state
[   25.831046] eth0: renamed from veth18a9133
[   25.912148] br-52843f9ca546: port 5(veth06433b4) entered blocking state
[   25.912172] br-52843f9ca546: port 5(veth06433b4) entered forwarding state
[   32.336367] usb 3-1: USB disconnect, device number 2
[   33.225923] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[   33.271344] usb 4-1: New USB device found, idVendor=03e7, idProduct=f63b, bcdDevice= 1.00
[   33.271365] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   33.271371] usb 4-1: Product: Luxonis Device
[   33.271376] usb 4-1: Manufacturer: Intel Corporation
[   33.271381] usb 4-1: SerialNumber: 18443010011141F500
[   33.305023] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 3
[   37.119464] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[   37.122672] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[   37.126945] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[29466.248042] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[29469.991562] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[29470.012390] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[29470.016133] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[34557.966873] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[34557.969194] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[34557.971966] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[34557.976734] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[34557.980524] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[63991.093073] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[63994.832540] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[63994.837500] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[63994.840852] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[86804.293077] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[86804.295301] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[86804.296811] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[86805.355154] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[86805.359850] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[86805.362544] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[89400.955558] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[89400.957719] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[89400.962193] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[89400.966911] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[89400.970285] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[109289.342203] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 0
[109293.086877] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[109293.091928] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[109293.096587] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[109978.888291] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[109978.890291] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[109978.890604] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[109982.626980] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[109982.631457] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[109982.635799] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[110285.404163] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[110285.405893] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[110285.409672] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[110285.415005] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[110285.418242] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[139716.781066] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[139720.518678] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[139720.523623] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[139720.527307] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[139787.762702] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[139787.764406] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[139787.767296] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[139787.772062] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[139787.775608] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[169224.263786] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[169228.002610] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[169228.008270] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[169228.013073] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[173848.021400] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[173848.023516] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[173848.026521] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[173848.031217] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[173848.035802] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[203281.941704] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[203285.692806] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:db:27
[203285.860430] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[203287.801195] mwifiex_sdio mmc0:0001:1: ASSOC_RESP: failed,	status code=1 err=0xfffc a_id=0x3fff
[203287.801218] mwifiex_sdio mmc0:0001:1: assoc failure: reason CONNECT_ERR_ASSOC_ERR_TIMEOUT
[203287.801226] mwifiex_sdio mmc0:0001:1: ASSOC_RESP: UNSPECIFIED failure
[203287.801270] mwifiex_sdio mmc0:0001:1: info: association to bssid 58:bf:ea:bb:db:27 failed
[203289.212557] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[203289.218369] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[203289.221134] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[203325.096830] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[203325.098495] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[203325.098906] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[203328.813166] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:db:27
[203328.820632] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[203328.829364] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:db:27 successfully
[203334.503834] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:db:27: reason code 15
[203335.480093] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[203335.485878] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[203335.490346] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[232770.277692] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[232774.027983] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[232774.032710] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[232774.036204] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[232809.876074] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[232809.877717] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[232809.880766] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[232809.885491] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[232809.888855] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[262236.716341] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[262240.467313] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[262240.472183] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[262240.477759] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[262380.194906] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[262380.197035] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[262380.204995] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[262380.210127] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[262380.214419] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[263828.326252] usb 1-1: USB disconnect, device number 2
[263828.326270] usb 1-1.4: USB disconnect, device number 3
[263828.495034] usb 2-1: USB disconnect, device number 2
[263828.825112] usb 1-1: new high-speed USB device number 4 using xhci-hcd
[263829.005589] usb 1-1: New USB device found, idVendor=0424, idProduct=2744, bcdDevice= 2.21
[263829.005607] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[263829.005614] usb 1-1: Product: USB2744
[263829.005619] usb 1-1: Manufacturer: Microchip Tech
[263829.043447] hub 1-1:1.0: USB hub found
[263829.043527] hub 1-1:1.0: 4 ports detected
[263829.170712] usb 2-1: new SuperSpeed USB device number 3 using xhci-hcd
[263829.195481] usb 2-1: New USB device found, idVendor=0424, idProduct=5744, bcdDevice= 2.21
[263829.195504] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[263829.195510] usb 2-1: Product: USB5744
[263829.195516] usb 2-1: Manufacturer: Microchip Tech
[263829.235015] hub 1-1:1.0: USB hub found
[263829.235015] hub 2-1:1.0: USB hub found
[263829.235080] hub 1-1:1.0: 4 ports detected
[263829.235569] hub 2-1:1.0: 3 ports detected
[263829.347020] hub 2-1:1.0: USB hub found
[263829.347108] hub 2-1:1.0: 3 ports detected
[263829.625029] usb 1-1.4: new high-speed USB device number 5 using xhci-hcd
[263829.755684] usb 1-1.4: New USB device found, idVendor=0424, idProduct=2740, bcdDevice= 2.00
[263829.755703] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[263829.755709] usb 1-1.4: Product: Hub Controller
[263829.755714] usb 1-1.4: Manufacturer: Microchip Tech
[291810.630250] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[291814.357459] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[291814.362528] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[291814.368448] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[291822.956668] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[291822.958394] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[291822.958695] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[291826.677775] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[291826.684352] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[291826.689755] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[291839.660493] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[291839.662220] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[291839.662524] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[291843.383613] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:db:27
[291845.508652] mwifiex_sdio mmc0:0001:1: ASSOC_RESP: failed,	status code=2 err=0xfffa a_id=0x3fff
[291845.508676] mwifiex_sdio mmc0:0001:1: assoc failure: reason Unknown connect failure
[291845.508724] mwifiex_sdio mmc0:0001:1: info: association to bssid 58:bf:ea:bb:db:27 failed
[291846.839969] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[291846.843145] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[291846.846715] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[291900.627778] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[291900.629949] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[291900.632371] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[291900.637008] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[291900.640511] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully
[321330.038999] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:40:19:47: reason code 1
[321333.785795] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:bb:d6:c7
[321333.790672] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[321333.794095] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:bb:d6:c7 successfully
[343276.277044] mwifiex_sdio mmc0:0001:1: mlan0: already connected
[343276.279214] mwifiex_sdio mmc0:0001:1: info: successfully disconnected from 58:bf:ea:bb:d6:c7: reason code 3
[343276.285063] mwifiex_sdio mmc0:0001:1: info: trying to associate to bssid 58:bf:ea:40:19:47
[343276.289854] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x95
[343276.293476] mwifiex_sdio mmc0:0001:1: info: associated to bssid 58:bf:ea:40:19:47 successfully

I also generated a NetworkManager log, but the file was large and I don’t have permission to upload files here on the forum.
“Sorry, new users can’t upload attachments.”

Thank you for providing the dmesg logs. Looking at the Wi-Fi driver output mwifiex_sdio mmc0:0001:1, the disconnections you are observing are reported with reason codes 1 and 3:

  • Reason code 1 (“Unspecified reason”): the access point ends the connection without giving a detailed cause. This usually happens due to transient RF conditions, channel changes, or internal AP decisions.
  • Reason code 3 (“Deauthenticated because sending station is leaving/has left the BSS”): most often AP-initiated, indicating the AP is actively telling the client to leave. This is common in environments with multiple access points, where the infrastructure forces clients to roam or load-balances them.

Both of these codes come from the network side, not the Wi-Fi firmware itself, which means the disconnections are being triggered by how the access points manage client associations rather than a malfunction of the Verdin module. So the issue you are having is related to network setup and the AP behaviour, not the drivers or how the devices are setup.

However, there are a few things that we could try to see if we can mitigate this issue:

  • Keep Wi-Fi power save disabled, as you already implemented;
  • Adjust roaming aggressiveness so the device does not roam too quickly between APs if it is stationary;
  • If possible, test with fewer or dedicated APs to confirm whether the instability is linked to the network’s roaming and load-balancing configuration;
  • Ask your company’s IT team to check the WLC configuration of the local network. Check for features like band steering, load balancing, or aggressive roaming policies (different networking hardware have different names), as these settings may cause the kind of disconnections you are experiencing.

I hope these details help you and your IT team move forward with the analysis. Please let us know the results after adjusting the network settings or if you need further assistance from our side.