From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: PM regression in next
Date: Fri, 12 Jan 2018 13:23:54 +0100 [thread overview]
Message-ID: <4913146.sVL6sFxzC8@aspire.rjw.lan> (raw)
In-Reply-To: <20180112013257.GB4059@atomide.com>
On Friday, January 12, 2018 2:32:57 AM CET Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.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
This looks totally bogus.
First, "error" should be a negative number and we print it as int.
Second, error codes are not in this range anyway.
> > [ 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.
BTW, can you please CC PM bug reports to linux-pm? That may help sometimes.
Thanks,
Rafael
next prev parent reply other threads:[~2018-01-12 12:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:01 Tony Lindgren
2018-01-12 0:18 ` Andrew Morton
2018-01-12 0:23 ` Tony Lindgren
2018-01-12 0:45 ` Andrew Morton
2018-01-12 1:20 ` Tony Lindgren
2018-01-12 1:32 ` Tony Lindgren
2018-01-12 12:23 ` Rafael J. Wysocki [this message]
2018-01-12 12:30 ` Rafael J. Wysocki
2018-01-12 13:01 ` Lars-Peter Clausen
2018-01-12 13:16 ` Andrew Lunn
2018-01-12 13:52 ` Tony Lindgren
2018-01-12 13:55 ` Andrew Lunn
2018-01-12 14:14 ` Tony Lindgren
2018-01-12 19:00 ` Tony Lindgren
2018-01-12 19:12 ` Mark Brown
2018-01-12 21:07 ` Tony Lindgren
2018-01-12 21:15 ` Mark Brown
2018-01-12 21:50 ` Tony Lindgren
2018-01-12 22:11 ` Mark Brown
2018-01-12 22:49 ` Tony Lindgren
2018-01-12 22:59 ` Mark Brown
2018-01-15 1:45 ` Kuninori Morimoto
2018-01-15 16:50 ` Tony Lindgren
2018-01-15 17:19 ` Mark Brown
2018-01-15 17:52 ` Tony Lindgren
2018-01-15 17:56 ` Mark Brown
2018-01-15 18:06 ` Tony Lindgren
2018-01-15 18:13 ` Mark Brown
2018-01-15 18:55 ` Tony Lindgren
2018-01-16 0:38 ` Kuninori Morimoto
2018-01-17 9:47 ` Peter Ujfalusi
[not found] ` <871siqbte4.wl%kuninori.morimoto.gx@renesas.com>
2018-01-16 0:36 ` Tony Lindgren
2018-01-12 21:38 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4913146.sVL6sFxzC8@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®