From mboxrd@z Thu Jan 1 00:00:00 1970 From: mingo@kernel.org (Ingo Molnar) Date: Fri, 15 Jan 2016 11:14:59 +0100 Subject: [PATCH v2] reboot: Backup orderly_poweroff In-Reply-To: <20160114132527.575e0f20@lxorguk.ukuu.org.uk> References: <1452688405-15087-1-git-send-email-j-keerthy@ti.com> <20160114090520.GA4351@gmail.com> <569767EC.2010704@ti.com> <20160114100913.GB15857@gmail.com> <56977BA7.702@ti.com> <20160114112354.GA17869@gmail.com> <20160114132527.575e0f20@lxorguk.ukuu.org.uk> Message-ID: <20160115101459.GB23349@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * One Thousand Gnomes wrote: > > If kernel_power_off() is called then the system should power off. No ifs and > > whens. > > Even if it doesn't the watchdog should kill it. > > That is broken on some platforms on the watchdog side as the > watchdog shuts down during our power off callbacks - because the system > firmware is too stupid to reset the watchdog as it powers back up (so > keeps rebooting). > > If you watchdog and firmware function properly you shouldn't even have to > care if you crash during the kernel power off. That's a good point as well - if the system is 'stuck' for some notion of stuck, then watchdog drivers can help. Here it's unclear whether user-space even called the sys_reboot() system call. Thanks, Ingo