[Bug]: Kernel panic encountered when calling modprobe sprdwl_ng.

[ZYQsteve]

What happened?

There is a uwe5621ds WiFi module on my rk3576 development board. I burned the system image of armsom-cm5-io. After booting, calling the modprobe sprdwl_ng command will encounter the following kernel pannic
[ 71.088504] Unable to handle kernel NULL pointer dereference at virtual address 00 000000000001d0 [ 71.089376] Mem abort info: [ 71.089655] ESR = 0x0000000096000004 [ 71.090002] EC = 0x25: DABT (current EL), IL = 32 bits [ 71.090490] SET = 0, FnV = 0 [ 71.090784] EA = 0, S1PTW = 0 [ 71.091069] FSC = 0x04: level 0 translation fault [ 71.091509] Data abort info: [ 71.091772] ISV = 0, ISS = 0x00000004 [ 71.092147] CM = 0, WnR = 0 [ 71.092432] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000102e2e000 [ 71.093018] [00000000000001d0] pgd=0000000000000000, p4d=0000000000000000 [ 71.093635] Internal error: Oops: 0000000096000004 [#1] SMP [ 71.094144] Modules linked in: sprdwl_ng(+) sprdbt_tty bnep rk805_pwrkey ufs_rockc hip nvmem_rockchip_otp rockchip_cpuinfo ufshcd_pltfrm joydev input_leds ufshcd_core u io_pdrv_genirq uio zram zsmalloc binfmt_misc sch_fq_codel fuse ip_tables ipv6 pwm_bl panel_simple panfrost drm_shmem_helper gpu_sched [ 71.096551] CPU: 5 PID: 2071 Comm: modprobe Not tainted 6.1.84-vendor-rk35xx #1 [ 71.097217] Hardware name: ArmSoM CM5 IO (DT) [ 71.097614] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 71.098246] pc : get_loopcheck_status+0x18/0x20 [ 71.098662] lr : start_marlin+0x7c/0xc4 [ 71.099023] sp : ffff80000e8137d0 [ 71.099330] x29: ffff80000e8137d0 x28: ffff80000a31a910 x27: 0000000000000000 [ 71.099976] x26: 0000000000000000 x25: ffff80000a44e000 x24: ffff80000a670310 [ 71.100621] x23: 0000000000000000 x22: ffff80000a575fa8 x21: 0000000000000002 [ 71.101265] x20: ffff0000c4671810 x19: ffff800009466f1f x18: 0000000000000000 [ 71.101910] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 71.102555] x14: 0000000000000000 x13: 5d494649575f4e49 x12: 4c52414d5b206e69 [ 71.103201] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800009205260 [ 71.103846] x8 : 00000817c200001f x7 : 696c72616d5f7472 x6 : 617473203a4e4357 [ 71.104492] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 71.105136] x2 : 0000000000000000 x1 : ffff0000c24aeac0 x0 : 0000000000000000 [ 71.105781] Call trace: [ 71.106011] get_loopcheck_status+0x18/0x20 [ 71.106397] sprdwl_probe+0x2c/0x330 [sprdwl_ng] [ 71.106881] platform_probe+0x70/0xc0 [ 71.107224] really_probe+0x1cc/0x390 [ 71.107570] __driver_probe_device+0x140/0x158 [ 71.107980] driver_probe_device+0x48/0xd0 [ 71.108356] __device_attach_driver+0x110/0x124 [ 71.108775] bus_for_each_drv+0xa4/0xd0 [ 71.109129] __device_attach+0xf0/0x174 [ 71.109482] device_initial_probe+0x1c/0x28 [ 71.109870] bus_probe_device+0x38/0x9c [ 71.110223] device_add+0x558/0x694 [ 71.110545] platform_device_add+0xe0/0x218 [ 71.110931] unisoc_wlan_init+0x54/0x1000 [sprdwl_ng] [ 71.111441] do_one_initcall+0x94/0x1e8 [ 71.111799] do_init_module+0x58/0x1dc [ 71.112152] load_module+0x1820/0x18d4 [ 71.112494] __do_sys_finit_module+0xfc/0x120 [ 71.112894] __arm64_sys_finit_module+0x24/0x30 [ 71.113315] invoke_syscall+0x8c/0x128 [ 71.113656] el0_svc_common.constprop.0+0xd8/0x124 [ 71.114097] do_el0_svc+0xa8/0xb8 [ 71.114406] el0_svc+0x2c/0x54 [ 71.114694] el0t_64_sync_handler+0xac/0x13c [ 71.115082] el0t_64_sync+0x19c/0x1a0 [ 71.115424] [ 71.115424] PC: 0xffff800008ac54c8:

How to reproduce?

This kernel panic occurs when modprobe sprdwl_ng is called for the first time after each boot.
armsom-cm5-io:~:% sudo modprobe sprdwl_ng [sudo] password for steve: [1] 2950 segmentation fault sudo modprobe sprdwl_ng armsom-cm5-io:~:%

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Jira ticket: AR-2570

[EvilOlaf]

This is not an issue with the build framework. For issues running Armbian please report to forums.