<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Poweroff command is Fail on M5CoreMP135.]]></title><description><![CDATA[<p dir="auto">On M5 CoreMP135, the "poweroff" command does not shutdown properly. After some time, a reboot occurs.</p>
<p dir="auto">The "reboot" command works correctly.</p>
<p dir="auto">There is no difference between buildroot and Debian, and the same phenomenon occurs in the latest commit of buildroot on github.</p>
<p dir="auto"><img src="/assets/uploads/files/1718723521252-4a8e6984-5962-440d-9696-b1c9ba99126d-image.png" alt="4a8e6984-5962-440d-9696-b1c9ba99126d-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Linux Log(USB serial connected to CoreMP135 Port.C, Log in root)</p>
<pre><code>$ poweroff
Stopping /etc/rc.localOK
Stopping dropbear sshd: OK
Stopping dhcpcd...
stopped /sbin/dhcpcd (pid 177)
Stopping network: OK
Stopping tee-supplicant: FAIL
Seeding 256 bits and crediting
Saving 256 bits of creditable seed for next boot
Stopping mdev... stopped process in pidfile '/var/run/mdev.pid' (pid 138)
OK
Stopping modules: rmmod: can't unload module 'soundcore': Resource temporarily unavailable
rmmod: can't unload module 'snd': Resource temporarily unavailable
rmmod: can't unload module 'snd_timer': Resource temporarily unavailable
rmmod: can't unload module 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload module 'snd_pcm_dmaengine': Resource temporarily unavailable
rmmod: can't unload module 'snd_soc_core': Resource temporarily unavailable
rmmod: can't unload module 'snd_soc_simple_card_utils': Resource temporarily unavailable
rmmod: can't unload module 'libcomposite': Resource temporarily unavailable
OK
Stopping klogd: OK
Stopping syslogd: OK
umount: devtmpfs busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system poweroff
[  235.243319] reboot: Power down
E/TC:0   Panic at core/arch/arm/plat-stm32mp1/pm/low_power.c:405 &lt;stm32_enter_cstop_shutdown&gt;
E/TC:0   TEE load address @ 0xde200000
E/TC:0   Call stack:
E/TC:0    0xde203f29
E/TC:0    0xde21c0f9
E/TC:0    0xde20a5bb
E/TC:0    0xde20af21
E/TC:0    0xde23e791
E/TC:0    0xde20b233
E/TC:0    0xde20b0dc


[    0.004017] /cpus/cpu@0 missing clock-frequency property
[    0.435184] stm32-cpufreq stm32-cpufreq: OPP-v2 not supported
Starting syslogd: OK
Starting klogd: OK
Starting modules: soundcore success, snd success, snd_timer success, snd_pcm success, snd_pcm_dmaengine success, snd_soc_core success, snd_soc_simple_card_utils success, snd_soc_audio_graph_card success, snd-soc-simple-card success, snd_soc_stm32_sai success, snd_soc_stm32_sai_sub success, cdc-acm success, libcomposite success, g_serial success, OK
Running sysctl: OK
Starting mdev... OK
Seeding 256 bits and crediting
Saving 256 bits of creditable seed for next boot
Starting tee-supplicant: Using device /dev/teepriv0.
OK
Starting network: OK
Starting dhcpcd...
dhcpcd-9.4.1 starting
DUID 00:01:00:01:2d:fa:18:62:ca:7e:a7:e6:2f:fb
forked to background, child pid 1[    5.408396] m_can_platform 4400e000.can can0: bit-timing not yet defined
77
[    5.421874] m_can_platform 4400e000.can can0: failed to open can device
[    5.436986] m_can_platform 4400f000.can can1: bit-timing not yet defined
[    5.454812] m_can_platform 4400f000.can can1: failed to open can device
Starting dropbear sshd: OK
Stopping /etc/rc.localOK

#     #  #######   #####   #######     #      #####   #    #
##   ##  #        #     #     #       # #    #     #  #   #
# # # #  #        #           #      #   #   #        #  #
#  #  #  ######    #####      #     #     #  #        ###
#     #        #        #     #     #######  #        #  #
#     #  #     #  #     #     #     #     #  #     #  #   #
#     #   #####    #####      #     #     #   #####   #    #
Welcome to CoreMP135, Powered by M5Stack.
CoreMP135 login:
</code></pre>
]]></description><link>https://community.m5stack.com/topic/6562/poweroff-command-is-fail-on-m5coremp135</link><generator>RSS for Node</generator><lastBuildDate>Thu, 12 Mar 2026 19:25:27 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/6562.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 18 Jun 2024 15:13:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Poweroff command is Fail on M5CoreMP135. on Sat, 29 Jun 2024 10:32:52 GMT]]></title><description><![CDATA[<p dir="auto">This issue has been resolved in the latest version, see issue.</p>
]]></description><link>https://community.m5stack.com/post/25704</link><guid isPermaLink="true">https://community.m5stack.com/post/25704</guid><dc:creator><![CDATA[nnn]]></dc:creator><pubDate>Sat, 29 Jun 2024 10:32:52 GMT</pubDate></item><item><title><![CDATA[Reply to Poweroff command is Fail on M5CoreMP135. on Sun, 23 Jun 2024 13:45:06 GMT]]></title><description><![CDATA[<p dir="auto">This discussion will be continued below<br />
<a href="https://github.com/m5stack/CoreMP135_buildroot-external-st/issues/3" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/m5stack/CoreMP135_buildroot-external-st/issues/3</a></p>
]]></description><link>https://community.m5stack.com/post/25659</link><guid isPermaLink="true">https://community.m5stack.com/post/25659</guid><dc:creator><![CDATA[nnn]]></dc:creator><pubDate>Sun, 23 Jun 2024 13:45:06 GMT</pubDate></item><item><title><![CDATA[Reply to Poweroff command is Fail on M5CoreMP135. on Tue, 18 Jun 2024 16:05:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/324">@nnn</a> thanks, I wondered what the issue was as the Plymouth service was failing</p>
]]></description><link>https://community.m5stack.com/post/25599</link><guid isPermaLink="true">https://community.m5stack.com/post/25599</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Tue, 18 Jun 2024 16:05:35 GMT</pubDate></item></channel></rss>