From: Ajay.Kathat@xxxxxxxxxxxxx [mailto:Ajay.Kathat@xxxxxxxxxxxxx] Sent: Wednesday, February 9, 2022 3:37 PM > On 08/02/22 21:56, Christoph Niedermaier wrote: >> >> Hello, >> >> I tested the wireless chip wilc1000 with the 5.16.5 Kernel and the firmware v15.4.1 >> (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/atmel/wilc1000_wifi_firmware-1.bin) >> on an i.MX6 QUAD with iperf3: >> >> # iperf3 -c IP_ADDR -P 16 -t 0 >> >> After a while the test gets stuck and I got the following kernel messages: >> mmc0: Timeout waiting for hardware interrupt. >> mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== >> mmc0: sdhci: Sys addr: 0x138f0200 | Version: 0x00000002 >> mmc0: sdhci: Blk size: 0x00000158 | Blk cnt: 0x00000001 >> mmc0: sdhci: Argument: 0x14000158 | Trn mode: 0x00000013 >> mmc0: sdhci: Present: 0x01d88a0a | Host ctl: 0x00000013 >> mmc0: sdhci: Power: 0x00000002 | Blk gap: 0x00000080 >> mmc0: sdhci: Wake-up: 0x00000008 | Clock: 0x0000009f >> mmc0: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000 >> mmc0: sdhci: Int enab: 0x107f100b | Sig enab: 0x107f100b >> mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000003 >> mmc0: sdhci: Caps: 0x07eb0000 | Caps_1: 0x0000a000 >> mmc0: sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff >> mmc0: sdhci: Resp[0]: 0x00001000 | Resp[1]: 0x00000000 >> mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 >> mmc0: sdhci: Host ctl2: 0x00000000 >> mmc0: sdhci: ADMA Err: 0x00000007 | ADMA Ptr: 0x4c041200 >> mmc0: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP ========= >> mmc0: sdhci-esdhc-imx: cmd debug status: 0x2100 >> mmc0: sdhci-esdhc-imx: data debug status: 0x2200 >> mmc0: sdhci-esdhc-imx: trans debug status: 0x2300 >> mmc0: sdhci-esdhc-imx: dma debug status: 0x2402 >> mmc0: sdhci-esdhc-imx: adma debug status: 0x25b4 >> mmc0: sdhci-esdhc-imx: fifo debug status: 0x2610 >> mmc0: sdhci-esdhc-imx: async fifo debug status: 0x2751 >> mmc0: sdhci: ============================================ >> wilc1000_sdio mmc0:0001:1: wilc_sdio_cmd53..failed, err(-110) >> wilc1000_sdio mmc0:0001:1: Failed cmd53 [0], bytes read... >> >> I tried to reduce the clock speed to 20MHz in the devicetree with >> max-frequency = <20000000>; >> but the problem then also occurs. >> >> Is this a possible bug? >> >> > Hi Ajay, Thanks for the answer. > The bus error seems to be specific to the host during the SDIO transfer. > How long does it take to reproduce it? Does the issue also happen > without "-P 16" iPerf3 option? It takes about 10s (something a bit longer) till I got this kernel error messages and it doesn't matter if I use it with "-P 16" or without. > It might be worth trying with power-save mode disabled. The PS mode can > be disabled either by setting WID_POWER_MANAGEMENT WID to > 0(WILC_FW_NO_POWERSAVE) in "wilc_set_power_mgmt()" or compile the kernel > with CFG80211_DEFAULT_PS disabled. I built a the kernel with CFG80211_DEFAULT_PS disabled, but the kernel error messages still appear. Regards Christoph
