[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180112013257.GB4059@atomide.com>
Date: Thu, 11 Jan 2018 17:32:57 -0800
From: Tony Lindgren <tony@...mide.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-omap@...r.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: PM regression in next
* Tony Lindgren <tony@...mide.com> [180111 17:20]:
> Well I tried to measure suspend power consumption and noticed
> that system suspend fails too hand hangs the network device:
>
> # echo mem > /sys/power/state
> [ 32.577850] PM: suspend entry (deep)
> [ 32.582031] PM: Syncing filesystems ... done.
> [ 32.598083] Freezing user space processes ... (elapsed 0.002 seconds) done.
> [ 32.608398] OOM killer disabled.
> [ 32.611846] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
> [ 32.622192] Suspending console(s) (use no_console_suspend to debug)
> [ 32.651123] dpm_run_callback(): mdio_bus_suspend+0x0/0x24 returns 4352
> [ 32.651428] PM: Device 2c000000.ethernet-ffffffff:01 failed to suspend: error 4352
> [ 32.653289] PM: Some devices failed to suspend, or early wake event detected
> [ 32.685455] OOM killer enabled.
> [ 32.688629] Restarting tasks ... done.
> [ 32.695983] PM: suspend exit
> ash: write error: Bad address
>
> That too works just fine at commit 70286688e5ad.
Suspend fails at commit e2d7fe89e8ae though, so looks like we
have two separate issues. I'll try to bisect that separately.
Regards,
Tony
Powered by blists - more mailing lists