From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3...
Date: Wed, 21 Dec 2016 19:37:03 +0800 [thread overview]
Message-ID: <20161221193703.6eac880c@xhacker> (raw)
Hi all,
I'm not sure this is a bug, when wake up from s2ram, I could get something
like:
[ 313.271464] Enabling non-boot CPUs ...
[ 313.271551] CPU1: Booted secondary processor
[ 313.271556] Detected VIPT I-cache on CPU1
[ 313.301378] cache: parent cpu1 should not be sleeping
[ 313.301504] CPU1 is up
[ 313.301582] CPU2: Booted secondary processor
[ 313.301585] Detected VIPT I-cache on CPU2
[ 313.331485] cache: parent cpu2 should not be sleeping
[ 313.331605] CPU2 is up
[ 313.331683] CPU3: Booted secondary processor
[ 313.331686] Detected VIPT I-cache on CPU3
[ 313.361599] cache: parent cpu3 should not be sleeping
[ 313.361719] CPU3 is up
This is because we call cpu_device_create() when secondary cpu is brought
online, the cpu_cache device's parent device: cpu device isn't already
resumed, all device resume will resume after secondary cores are brought
up.
What's the elegant solution to remove this warning msg?
Thanks in advance,
Jisheng
next reply other threads:[~2016-12-21 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 11:37 Jisheng Zhang [this message]
2016-12-21 16:54 ` How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3 Sudeep Holla
2016-12-22 7:48 ` Jisheng Zhang
2018-08-20 17:46 ` Steve Longerbeam
2018-10-02 17:07 ` Eugeniu Rosca
2019-01-25 13:07 ` Eugeniu Rosca
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=20161221193703.6eac880c@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).