This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: cannot shut down

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

Executing shutdown or poweroff command to shut down the system and finds that the generation process is normal, but stops after the kernel calls Power down, the shutdown is not complete, and finds the corresponding exception log source code at linux-sdk/board-support/trusted-firmware-a-2.5/plat/ti/k3/common/k3_psci.c.

And the following error is reported:

[ 71.008122] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 71.031793] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 71.046232] android_work: did not send uevent (0 0 0000000000000000)
[ 71.047156] systemd-journald[165]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 71.053752] android_work: did not send uevent (0 0 0000000000000000)
[ 71.071894] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 71.083956] systemd-shutdown[1]: Unmounting file systems.
[ 71.090741] [1379]: Remounting '/' read-only in with options '(null)'.
[ 71.129460] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
[ 71.137262] systemd-shutdown[1]: All filesystems unmounted.
[ 71.142876] systemd-shutdown[1]: Deactivating swaps.
[ 71.147934] systemd-shutdown[1]: All swaps deactivated.
[ 71.153156] systemd-shutdown[1]: Detaching loop devices.
[ 71.160090] systemd-shutdown[1]: All loop devices detached.
[ 71.165667] systemd-shutdown[1]: Detaching DM devices.
[ 71.170896] systemd-shutdown[1]: All DM devices detached.
[ 71.176288] systemd-shutdown[1]: All filesystems, swaps, loop devices and DM devices detached.
[ 71.191262] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 71.197953] systemd-shutdown[1]: Powering off.
[ 71.202745] pci_generic_config_write32: 44 callbacks suppressed
[ 71.202752] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0xdc may corrupt adjacent RW1C bits
[ 71.218410] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 71.228129] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x9c may corrupt adjacent RW1C bits
[ 71.237896] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 71.247620] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 71.257310] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 71.266970] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0xdc may corrupt adjacent RW1C bits
[ 71.276702] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 71.286420] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x9c may corrupt adjacent RW1C bits
[ 71.296167] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 71.323369] reboot: Power down
ERROR: System Off: operation not handled.

This problem occurs when emmc boot mode is started, TF card boot can enable reboot, power off is also not available. Could you help check this case? Thanks.

Best Regards,

Cherry