8devices / qcacld-2.0

Drivers for BLUE bean and RED bean modules
8 stars 13 forks source link

Error when loading wlan-sdio.ko #12

Closed aigFsch closed 3 years ago

aigFsch commented 4 years ago

This is a followup to my question here: https://github.com/8devices/qcacld-2.0/issues/11

When I try to insmod my sdio driver it fails with the following message:

insmod /lib/modules/4.9.88-F\+S/wlan-sdio.ko
wlan_sdio: loading out-of-tree module taints kernel.
wlan_sdio: loading driver v4.5.24.4
hifDeviceInserted: Dumping clocks (50000000,198000000)
HIFDumpCCCR 0(43)
1(3) 2(0)
3(0) 4(0)
5(0) 6(0)
7(6) 8(17)
9(0) A(10)
B(0) C(0)
D(0) E(0)
F(0) 10(0)
11(0) 12(1)
13(3) 14(7)
15(37) 16(1)

AR6000: Set async interrupt delay clock as 2.
R0: wlan: [310:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: wlan: [310:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
mmc1: Timeout waiting for hardware interrupt.
mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
mmc1: sdhci: Sys addr:  0x18d90000 | Version:  0x00000002
mmc1: sdhci: Blk size:  0x00000004 | Blk cnt:  0x00000001
mmc1: sdhci: Argument:  0x1410a004 | Trn mode: 0x00000013
mmc1: sdhci: Present:   0x01f8820e | Host ctl: 0x00000013
mmc1: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
mmc1: sdhci: Wake-up:   0x00000008 | Clock:    0x0000003f
mmc1: sdhci: Timeout:   0x0000008f | Int stat: 0x00000000
mmc1: sdhci: Int enab:  0x107f100b | Sig enab: 0x107f100b
mmc1: sdhci: AC12 err:  0x00000000 | Slot int: 0x00000103
mmc1: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000a007
mmc1: sdhci: Cmd:       0x0000353a | Max curr: 0x00ffffff
mmc1: sdhci: Resp[0]:   0x00001000 | Resp[1]:  0x00000000
mmc1: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
mmc1: sdhci: Host ctl2: 0x00000000
mmc1: sdhci: ADMA Err:  0x00000003 | ADMA Ptr: 0x1c05d204
mmc1: sdhci: ============================================
AR6000: SDIO bus operation failed! MMC stack returned : -110
__HIFReadWrite, addr:0X000850, len:00000004, Read , Sync
Unable to decrement the command credit count register
Unable to write to the device.
R0: wlan: [310:F :HIF]  hdd_wlan_startup failed
AR6000: SDIO bus operation failed! MMC stack returned : -84
__HIFReadWrite, addr:0X000868, len:00000004, Write, Sync
ar6k_wlan: probe of mmc1:0001:1 failed with error -1
ath_hif_sdio: HIF (Atheros/multi-bss)
R0: wlan: [310:E :HDD] hdd_hif_register_driver: 17769: hdd_wlan_startup failed status:-11 jiffies_left:14000
R0: wlan: [310:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
AR6000: Unregistering with the bus driver
AR6000: Unregistered!wlan_sdio: loading driver v4.5.24.4
hifDeviceInserted: Dumping clocks (50000000,198000000)
HIFDumpCCCR 0(43)
1(3) 2(0)
3(0) 4(0)
5(0) 6(0)
7(6) 8(17)
9(0) A(10)
B(0) C(0)
D(0) E(0)
F(0) 10(0)
11(0) 12(1)
13(3) 14(7)
15(37) 16(3)

AR6000: Set async interrupt delay clock as 2.
R0: wlan: [310:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: wlan: [310:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
AR6000: SDIO bus operation failed! MMC stack returned : -110
__HIFReadWrite, addr:0X000850, len:00000004, Read , Sync
Unable to decrement the command credit count register
Unable to write to the device.
R0: wlan: [310:F :HIF]  hdd_wlan_startup failed
AR6000: SDIO bus operation failed! MMC stack returned : -110
__HIFReadWrite, addr:0X000868, len:00000004, Write, Sync
ar6k_wlan: probe of mmc1:0001:1 failed with error -1
ath_hif_sdio: HIF (Atheros/multi-bss)
R0: wlan: [310:E :HDD] hdd_hif_register_driver: 17769: hdd_wlan_startup failed status:-11 jiffies_left:14000
R0: wlan: [310:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
AR6000: Unregistering with the bus driver
AR6000: Unregistered!insmod: can't insert '/lib/modules/4.9.88-F+S/wlan-sdio.ko': No such device

Do you have any idea what might lead to this error?

valinskas commented 3 years ago

Driver running on Host fails to communicate with SDIO device over SDIO bus. MMC/SDIO stack returns errors:

#define ETIMEDOUT       110     /* Connection timed out */
#define EILSEQ          84      /* Illegal byte sequence */

It can be many things from a hardware compatibility (SD Host and SD device), powering (V1.8 vs V3 mismatch) and etc. No activity over the year, closed issue.