Kernel Panic at Shutdown

[ryanclem]

Not sure if anyone has seen this before, but when using the OSD335x-CSip I’m seeing a kernel panic at shutdown and power is never removed by the pmic. My design is based primarily around the OSD3358-CSip-RED platform schematic. The same exact uboot, device tree and disk image seem to work fine on a BeagleBoneBlack. The I know very little about the linux shutdown / powerdown process, but I was hoping someone else has run into this issue and that maybe it has something to do with how the PMIC is integrated / controlled from the software side? The I2C bus in general seems to be working correctly because uboot is able to read/write the EEPROM. I see the following issue if I attempt to shutdown by single pressing the power button or by running the shutdown -h command. Any help or suggestions would be much appreciated!

On my CSIP device I see the following on the console before the device remains powered and hangs:
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped target Swap.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Power-Off…
[ 3395.119440] reboot: Power down
[ 3396.616354] Kernel panic – not syncing: Attempted to kill init! exitcode=0x00000000
[ 3396.616354]
[ 3396.625584] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 4.19.94-ti-r36 #1bionic
[ 3396.633296] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 3396.639514] [<c0114468>] (unwind_backtrace) from [<c010e5a4>] (show_stack+0x20/0x24)
[ 3396.647339] [<c010e5a4>] (show_stack) from [<c0d6d380>] (dump_stack+0x8c/0xa0)
[ 3396.654642] [<c0d6d380>] (dump_stack) from [<c013d258>] (panic+0x10c/0x290)
[ 3396.661686] [<c013d258>] (panic) from [<c0142f80>] (do_exit+0x8f0/0xc1c)
[ 3396.668473] [<c0142f80>] (do_exit) from [<c0164e80>] (sys_reboot+0x16c/0x22c)
[ 3396.675686] [<c0164e80>] (sys_reboot) from [<c0101000>] (ret_fast_syscall+0x0/0x54)
[ 3396.683400] Exception stack(0xdc149fa8 to 0xdc149ff0)
[ 3396.688510] 9fa0: 00431440 ffffffff fee1dead 28121969 4321fedc 0ccf4700
[ 3396.696762] 9fc0: 00431440 ffffffff 02032038 00000058 fffff000 020305f8 00000000 fffff000
[ 3396.705004] 9fe0: 00000058 beaab9dc b6f21e25 b6ea5206
[ 3396.710150] —[ end Kernel panic – not syncing: Attempted to kill init! exitcode=0x00000000
[ 3396.710150] ]—
(At this point the device remains powered and must be physically reset)
====

On the beagle bone black I see the following and the device turns off:

[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped target Swap.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Power-Off…
[ 84.166880] reboot: Power down
(At this point the PMIC removes power and can be turned back on by pressing the power button)

[Neeraj Dantu]

ryanclem,

 

Please take a look at this thread for the exact issue: https://octavosystems.com/forums/topic/kernel-panic-on-shutdown/

 

Best,

Neeraj

 

[ryanclem]

Thank you!! I must not have searched the -SM specific forum before posting this. That thread was very helpful in diagnosing my problem.

To help anyone else in the future –
My issue was that the RTC oscillator (OSC1) was not starting up properly. I had not noticed that on the OSD3358-C-Sip-RED schematic that R24 (1M resistor in parallel with 32k crystal Y1) was DNI. Apparently the RTC has an internal resistor that is used by default in most images and the R24 is not needed and will inhibit the oscillator from functioning properly. (https://e2e.ti.com/support/processors/f/791/t/316906?AM335X-External-RTC-crystal-doesn-t-oscillate-)

[Author]

Posts