[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140326005115.GW7528@n2100.arm.linux.org.uk>
Date: Wed, 26 Mar 2014 00:51:15 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
Cc: Sebastian Capella <sebastian.capella@...aro.org>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linaro-kernel@...ts.linaro.org, Len Brown <len.brown@...el.com>,
Pavel Machek <pavel@....cz>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: machine_power_off should not return
On Tue, Mar 25, 2014 at 07:45:55PM -0300, Ezequiel Garcia wrote:
> Let's Cc: LAKML, and To: Russell.
>
> Russell, any comments on this?
>
> Without this patch we got the heartbeat's reboot_notifier called twice while
> testing the recent hibernation patches, which was unexpected and produced a
> kernel panic: https://lkml.org/lkml/2014/3/19/363
I don't see why we should make this change. kernel/reboot.c handles
this function returning, so other places should do too.
Even on x86, this function can return:
void machine_power_off(void)
{
machine_ops.power_off();
}
.power_off = native_machine_power_off,
static void native_machine_power_off(void)
{
if (pm_power_off) {
if (!reboot_force)
machine_shutdown();
pm_power_off();
}
/* A fallback in case there is no PM info available */
tboot_shutdown(TB_SHUTDOWN_HALT);
}
void tboot_shutdown(u32 shutdown_type)
{
void (*shutdown)(void);
if (!tboot_enabled())
return;
Therefore, I'd say... it's a bug in the hibernation code - or we probably
have many buggy architectures. I'd suggest fixing the hibernation code
rather than stuffing some workaround like an endless loop into every
architecture.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists