Debugging kernel panic traces during the kernel boot on the wp76xx

IoT Modules WP Series
1

Hi,

We are currently backporting some wl18xx drivers into a custom board based on the wp76xx but a change to use the vmmc-supply property in the device tree has stopped the kernel from booting. The console only gives us this information:
[ 1.161110] BUG: spinlock already unlocked on CPU#0, kworker/u2:0/6
[ 1.166345] lock: 0xcd8dc5b0, .magic: dead4ead, .owner: /-1, .owner_cpu: -1
[ 1.174073] Causing a watchdog bite!

It looks like the loglevel is set fairly low, is there a way of altering the bootargs= kernel cmdline parameter so we can see the full console output? Or is there something else from stopping the complete kernel panic trace from appearing.

Any help is greatly appreciated,
Martin.

2

Hi Martin,
Welcome to the forum!

Are you able to flash Yocto image on this unit?
If yes, please try flash the official Sierra image then send below AT command to disable “quiet” option and see does it print enough log to debug.

AT!ENTERCND="A710"
AT!CUSTOM="BOOTQUIETDISABLE",1
AT!RESET

Hope it helps.
Thx