• State
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 45 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

AM62A7: Linux VTM thermal shutdown status

Fadong XUE Fadong XUE
Prodigy 10 points
Part Number: AM62A7

Tool/software:

Hello team:

We referred to this document and configured the hot shutdown

https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/09_02_00/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/VTM.html

root@am62axx-evm:~# [ 1479.579005] thermal thermal_zone0: main0-thermal: critical temperature reached, shutting down
[ 1479.587695] reboot: HARDWARE PROTECTION shutdown (Temperature too high)
[  OK  ] Removed slice Slice /system/modprobe.
[  OK  ] Stopped target Graphical Interface.
[  OK  ] Stopped target Multi-User System.
[  OK  ] Stopped target Login Prompts.
[  OK  ] Stopped target RPC Port Mapper.
[  OK  ] Stopped target System Time Set.
[  OK  ] Stopped target Timer Units.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
[  OK  ] Stopped target Hardware activated USB gadget.
[  OK  ] Closed Process Core Dump Socket.
[  OK  ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Stopping containerd container runtime...
[  OK  ] Stopped DEMO.
         Stopping Getty on tty1...
         Stopping irqbalance daemon...
         Stopping Reboot and dump vmcore via kexec...
         Stopping Netperf Benchmark Server...
         Stopping NFS status monitor for NFSv2/3 locking....
[  OK  ] Stopped Expand the rootfs partition to full size of the boot dev         Stopping Serial Getty on ttyS2...
         Stopping Simple Network Ma…ent Protocol (SNMP) Daemon....
         Stopping strongSwan IPsec …Ev2 daemon using ipsec.conf...
         Stopping Load/Save Random Seed...
         Stopping TEE Supplicant...
         Stopping Telnet Server...
[  OK  ] Stopped irqbalance daemon.
[  OK  ] Stopped strongSwan IPsec I…IKEv2 daemon using ipsec.conf.
[  OK  ] Stopped TEE Supplicant.
[  OK  ] Stopped Netperf Benchmark Server.
[  OK  ] Stopped NFS status monitor for NFSv2/3 locking..
[  OK  ] Stopped Simple Network Man…ement Protocol (SNMP) Daemon..
[  OK  ] Stopped containerd container runtime.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped Serial Getty on ttyS2.
[  OK  ] Stopped Reboot and dump vmcore via kexec.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Telnet Server.
[  OK  ] Removed slice Slice /system/getty.
[  OK  ] Removed slice Slice /system/serial-getty.
[  OK  ] Stopped target Host and Network Name Lookups.
         Stopping Permit User Sessions...
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped target Network.
[  OK  ] Stopped target Remote File Systems.
         Stopping Network Configuration...
[  OK  ] Stopped Network Configuration.
[  OK  ] Stopped target Preparation for Network.
[  OK  ] Stopped IPv6 Packet Filtering Framework.
[  OK  ] Stopped IPv4 Packet Filtering Framework.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Path Units.
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.
[  OK  ] Stopped target Slice Units.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Socket Units.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed Docker Socket for the API.
[  OK  ] Closed dropbear.socket.
[  OK  ] Closed PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Closed Network Service Netlink Socket.
[  OK  ] Closed Weston socket.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
         Stopping Record System Boot/Shutdown in UTMP...
[  OK  ] Stopped Record System Boot/Shutdown in UTMP.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
         Unmounting /media/ram...
         Unmounting Temporary Directory /tmp...
         Unmounting /var/volatile...
[  OK  ] Unmounted /media/ram.
[  OK  ] Unmounted Temporary Directory /tmp.
[  OK  ] Unmounted /var/volatile.
[  OK  ] Stopped target Preparation for Local File Systems.
[  OK  ] Stopped target Swaps.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Reached target System Shutdown.
[  OK  ] Reached target Late Shutdown Services.
[  OK  ] Finished System Power Off.
[  OK  ] Reached target System Power Off.
[ 1481.807260] kauditd_printk_skb: 13 callbacks suppressed
[ 1481.807304] audit: type=1334 audit(1487.532:25): prog-id=18 op=UNLOAD
[ 1481.819315] audit: type=1334 audit(1487.532:26): prog-id=17 op=UNLOAD
[ 1481.867763] audit: type=1334 audit(1487.592:27): prog-id=6 op=UNLOAD
[ 1481.874356] audit: type=1334 audit(1487.592:28): prog-id=5 op=UNLOAD
[ 1481.880870] audit: type=1334 audit(1487.592:29): prog-id=4 op=UNLOAD
[ 1481.887394] audit: type=1334 audit(1487.596:30): prog-id=3 op=UNLOAD
[ 1481.937503] audit: type=1334 audit(1487.660:31): prog-id=16 op=UNLOAD
[ 1481.944167] audit: type=1334 audit(1487.660:32): prog-id=15 op=UNLOAD
[ 1482.101975] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 1482.124174] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 1482.184808] systemd-journald[163]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 1482.202175] audit: type=1335 audit(1487.924:33): pid=163 uid=0 auid=4294967295 tty=(none) ses=4294967295 comm="systemd-journal" exe="/lib/systemd/systemd-journald" nl-mcgrp=1 op=disconnect res=1
[ 1482.222119] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 1482.272601] systemd-shutdown[1]: Unmounting file systems.
[ 1482.291187] [769]: Remounting '/' read-only with options 'n/a'.
[ 1482.336668] EXT4-fs (mmcblk0p1): re-mounted. Quota mode: none.
[ 1482.376873] systemd-shutdown[1]: All filesystems unmounted.
[ 1482.382665] systemd-shutdown[1]: Deactivating swaps.
[ 1482.388286] systemd-shutdown[1]: All swaps deactivated.
[ 1482.393634] systemd-shutdown[1]: Detaching loop devices.
[ 1482.417163] systemd-shutdown[1]: All loop devices detached.
[ 1482.422978] systemd-shutdown[1]: Stopping MD devices.
[ 1482.429662] systemd-shutdown[1]: All MD devices stopped.
[ 1482.435110] systemd-shutdown[1]: Detaching DM devices.
[ 1482.441610] systemd-shutdown[1]: All DM devices detached.
[ 1482.447160] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[ 1482.472233] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 1482.479208] systemd-shutdown[1]: Powering off.
[ 1482.516749] reboot: Power down

When reaching the set temperature limit, a thermal shutdown occurred. We would like to know:

1. What is the state of thermal shutdown and is there a way to wake up SOC again after the temperature drops?

2. Is it normal that there is not much difference in power consumption between the thermal shutdown state and the normal operation of the system (low load), and the temperature does not drop quickly?

  • 0
    TI__Genius 9286 points

    Hello,

    Fadong XUE Fadong XUE said:
    1. What is the state of thermal shutdown and is there a way to wake up SOC again after the temperature dro

    The VTM module typically resets the SoC when the critical temperature threshold is detected. The resets would continue till the temperature drops to a safe level. You can ta je a look at the screenshot below.

    Fadong XUE Fadong XUE said:
    2. Is it normal that there is not much difference in power consumption between the thermal shutdown state and the normal operation of the system (low load), and the temperature does not drop quickly?

    I am not sure about this, let me check this internally and get back to you.

    Regards,

    Nihar Potturu. 

  • 0 in reply to Nihar Potturu
    Prodigy 10 points

    Hello
      Thank you very much for your answer. I would like to know how to configure the temperature threshold for resetting the SoC with the VTM module.
    Our current verification method is to modify the temperature attribute in DTS and set it to 60000.

    The final phenomenon is system shutdown, but the SOC cannot be restarted and remains stuck in "reboot: power down"