From: "Elliott, Robert (Servers)" <elliott@hpe.com>
To: Luigi Semenzato <semenzato@google.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"gpike@google.com" <gpike@google.com>
Subject: RE: [PATCH v2 2/2] pm: add more logging on hibernation failure
Date: Thu, 2 Jan 2020 20:39:27 +0000 [thread overview]
Message-ID: <TU4PR8401MB0927CC96419009A3D0B0FDDDAB200@TU4PR8401MB0927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20200102200052.51182-3-semenzato@google.com>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org <linux-kernel-
> owner@vger.kernel.org> On Behalf Of Luigi Semenzato
> Sent: Thursday, January 2, 2020 2:01 PM
> To: linux-pm@vger.kernel.org
...
> - pr_info("Preallocating image memory... ");
> + pr_info("Preallocating hibernation image memory\n");
...
> + pr_err("Cannot allocate original bitmap\n");
...
> + pr_err("Cannot allocate copy bitmap\n");
...
> + pr_err("Image allocation is %lu pages short\n",
> + alloc - pages_highmem);
...
> - pr_cont("done (allocated %lu pages)\n", pages);
> + pr_info("Allocated %lu pages for hibernation shapshot\n", pages);
> swsusp_show_speed(start, stop, pages, "Allocated");
Including the word "hibernation" or the phrase "hibernation image" in
each print would help in parsing the messages (e.g., with grep).
prev parent reply other threads:[~2020-01-02 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 20:00 [PATCH v2 0/2] clarify limitations of hibernation Luigi Semenzato
2020-01-02 20:00 ` [PATCH v2 1/2] Documentation: " Luigi Semenzato
2020-01-02 20:00 ` [PATCH v2 2/2] pm: add more logging on hibernation failure Luigi Semenzato
2020-01-02 20:39 ` Elliott, Robert (Servers) [this message]
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=TU4PR8401MB0927CC96419009A3D0B0FDDDAB200@TU4PR8401MB0927.NAMPRD84.PROD.OUTLOOK.COM \
--to=elliott@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=gpike@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=semenzato@google.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