Driver causes Kernel Panic

[mmader87]

The following kernel panic was observed while shutting down Linux. This kernel panic occurs intermittently. Running v15.5 of the WILC1000 firmware/kernel driver.

[ 190.921835] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 190.930624] Mem abort info:
[ 190.933414] ESR = 0x96000004
[ 190.936465] EC = 0x25: DABT (current EL), IL = 32 bits
[ 190.941772] SET = 0, FnV = 0
[ 190.944822] EA = 0, S1PTW = 0
[ 190.947959] Data abort info:
[ 190.950835] ISV = 0, ISS = 0x00000004
[ 190.954666] CM = 0, WnR = 0
[ 190.957631] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000052363000
[ 190.964067] [0000000000000000] pgd=0000000000000000
[ 190.968944] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 190.974513] Modules linked in: usb_f_eem g_ether usb_f_rndis u_ether libcomposite ci_hdrc_imx ci_hdrc usbmisc_imx ulpi roles udc_core imx219 spi_imx imx_sdma phy_generic hx280enc hantrodec_845s wilc_spi crc_itu_t crc7 ti_ads7950 industrialio_triggered_buffer kfifo_buf rtc_ds1307 galcore(O) drs bq27xxx_battery_i2c bq27xxx_battery bq25896_charger ipv6 nf_defrag_ipv6
[ 191.006774] CPU: 0 PID: 481 Comm: K_TXQ_TASK Tainted: G O 5.4.3-imx8mm+g8649ed67a58b #1
[ 191.016075] Hardware name: Variscite VAR-SOM-MX8MM (DT)
[ 191.021297] pstate: a0000085 (NzCv daIf -PAN -UAO)
[ 191.026110] pc : wilc_wlan_txq_remove_from_head+0x6c/0xd0 [wilc_spi]
[ 191.032467] lr : wilc_wlan_txq_remove_from_head+0x24/0xd0 [wilc_spi]
[ 191.038816] sp : ffff8000117dbb60
[ 191.042126] x29: ffff8000117dbb60 x28: 0000000000000001
[ 191.047435] x27: ffff00001226ae00 x26: 00000000000000e4
[ 191.052744] x25: ffff8000117dbdac x24: ffff8000117dbd94
[ 191.058052] x23: ffff8000117dbc90 x22: ffff000013bacfe8
[ 191.063361] x21: 0000000000000000 x20: ffff000013bac7c0
[ 191.068669] x19: ffff000013bb1620 x18: 0000000000000000
[ 191.073978] x17: 0000000000000000 x16: 0000000000000000
[ 191.079286] x15: 0000000000000000 x14: 0000000000000000
[ 191.084594] x13: 008b20f22653787e x12: 0000000000000001
[ 191.089903] x11: 0000000000000000 x10: 0000000000000002
[ 191.095211] x9 : ffff000017da86d0 x8 : ffff000017da7d00
[ 191.100520] x7 : ffff0000165fa940 x6 : ffff000015f691e0
[ 191.105828] x5 : 0000000000000001 x4 : dead000000000100
[ 191.111136] x3 : dead000000000122 x2 : 0000000000005d90
[ 191.116445] x1 : 0000000000000000 x0 : 00000000000000e4
[ 191.121753] Call trace:
[ 191.124205] wilc_wlan_txq_remove_from_head+0x6c/0xd0 [wilc_spi]
[ 191.130215] wilc_wlan_handle_txq+0x87c/0xd50 [wilc_spi]
[ 191.135531] wilc_txq_task+0xc0/0x288 [wilc_spi]
[ 191.140152] kthread+0xf0/0x120
[ 191.143295] ret_from_fork+0x10/0x18
[ 191.146871] Code: d37ef673 cb000273 8b130e93 f9479a75 (a94002a2)
[ 191.152962] ---[ end trace 9ea645e4cc8174c3 ]---

[ajaykathat]

Hi @mmader87,

We have recently added a fix for a similar issue in the latest WILCv15.6 driver

In case you are still observing this issue, please try with the latest fix.