[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160114132527.575e0f20@lxorguk.ukuu.org.uk>
Date: Thu, 14 Jan 2016 13:25:27 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Ingo Molnar <mingo@...nel.org>
Cc: Keerthy <a0393675@...com>, Keerthy <j-keerthy@...com>,
linux-kernel@...r.kernel.org, edubezval@...il.com,
grygorii.strashko@...com, nm@...com, linux-pm@...r.kernel.org,
linux-omap@...r.kernel.org, joel@....id.au,
akpm@...ux-foundation.org, linux-arm-kernel@...ts.infradead.org,
peterz@...radead.org, dyoung@...hat.com, josh@...htriplett.org,
mpe@...erman.id.au, Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH v2] reboot: Backup orderly_poweroff
>
> 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.
Alan
Powered by blists - more mailing lists