All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Jisheng Zhang <jszhang@marvell.com>,
	Steve Longerbeam <steve_longerbeam@mentor.com>,
	linux-pm@vger.kernel.org, Eugeniu Rosca <roscaeugeniu@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Eugeniu Rosca <erosca@de.adit-jv.com>,
	linux-arm-kernel@lists.infradead.org,
	Joshua Frkuska <joshua_frkuska@mentor.com>
Subject: Re: How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3...
Date: Fri, 25 Jan 2019 14:07:01 +0100	[thread overview]
Message-ID: <20190125130701.GA855@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <20181002170754.GA10240@vmlxhi-102.adit-jv.com>

Hi Sudeep,

On Tue, Oct 02, 2018 at 07:07:54PM +0200, Eugeniu Rosca wrote:
> Hello Sudeep,
> 
> I too experience the "cache: parent cpuN should not be sleeping" and
> confirm these are healed with your patch. Would it be possible to have
> the patch submitted for review?

Doing some s2ram testing on R-Car H3 Salvator-X using
v5.0-rc3-130-gd73aba1115cf, I am still able to reproduce these warnings.

Is there any chance you push the patch to the mailing list? If not, can
it be taken with a different authorship by mentioning this discussion
thread as source of inspiration?

> Thank you very much,
> Eugeniu.

WARNING: multiple messages have this Message-ID (diff)
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Jisheng Zhang <jszhang@marvell.com>,
	Steve Longerbeam <steve_longerbeam@mentor.com>,
	linux-pm@vger.kernel.org, Eugeniu Rosca <roscaeugeniu@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Eugeniu Rosca <erosca@de.adit-jv.com>,
	linux-arm-kernel@lists.infradead.org,
	Joshua Frkuska <joshua_frkuska@mentor.com>
Subject: Re: How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3...
Date: Fri, 25 Jan 2019 14:07:01 +0100	[thread overview]
Message-ID: <20190125130701.GA855@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <20181002170754.GA10240@vmlxhi-102.adit-jv.com>

Hi Sudeep,

On Tue, Oct 02, 2018 at 07:07:54PM +0200, Eugeniu Rosca wrote:
> Hello Sudeep,
> 
> I too experience the "cache: parent cpuN should not be sleeping" and
> confirm these are healed with your patch. Would it be possible to have
> the patch submitted for review?

Doing some s2ram testing on R-Car H3 Salvator-X using
v5.0-rc3-130-gd73aba1115cf, I am still able to reproduce these warnings.

Is there any chance you push the patch to the mailing list? If not, can
it be taken with a different authorship by mentioning this discussion
thread as source of inspiration?

> Thank you very much,
> Eugeniu.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-25 13:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 11:37 How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3 Jisheng Zhang
2016-12-21 11:37 ` Jisheng Zhang
2016-12-21 16:54 ` Sudeep Holla
2016-12-21 16:54   ` Sudeep Holla
2016-12-22  7:48   ` Jisheng Zhang
2016-12-22  7:48     ` Jisheng Zhang
2018-08-20 17:46   ` Steve Longerbeam
2018-08-20 17:46     ` Steve Longerbeam
2018-10-02 17:07   ` Eugeniu Rosca
2018-10-02 17:07     ` Eugeniu Rosca
2019-01-25 13:07     ` Eugeniu Rosca [this message]
2019-01-25 13:07       ` Eugeniu Rosca
2019-01-25 15:09       ` [RFC PATCH] drivers core: cpu: add hotplug callback to update cpu_dev state to resumed Sudeep Holla
2019-01-27 13:57         ` Eugeniu Rosca
2019-01-30 23:48         ` Rafael J. Wysocki
2019-01-31 16:05           ` Sudeep Holla
2019-02-04 15:37             ` Sudeep Holla
2019-02-04 15:44               ` Greg Kroah-Hartman
2019-02-04 15:52                 ` Sudeep Holla
2019-02-06 10:31               ` Rafael J. Wysocki
2019-02-06 13:59                 ` Sudeep Holla

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=20190125130701.GA855@vmlxhi-102.adit-jv.com \
    --to=erosca@de.adit-jv.com \
    --cc=joshua_frkuska@mentor.com \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=roscaeugeniu@gmail.com \
    --cc=steve_longerbeam@mentor.com \
    --cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.