From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: juri.lelli@arm.com, mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, len.brown@intel.com,
andrey.semin@intel.com
Subject: Re: Regression: turbostat stops working after suspend/resume cycle
Date: Mon, 18 May 2015 09:12:29 +0200 [thread overview]
Message-ID: <2225640.WJJBySMURY@xps13> (raw)
In-Reply-To: <20150518064552.GA12869@gmail.com>
On Monday 18 May 2015 08:45:52 Ingo Molnar wrote:
>
> * Gabriele Mazzotta <gabriele.mzt@gmail.com> wrote:
>
> > Hi,
> >
> > I've recently noticed that if I suspend and resume my laptop, I can no
> > longer execute turbostat. This is what I get when I try to start it:
> > # turbostat
> > Could not migrate to CPU 1
> > turbostat: re-initialized with num_cpus 4
> > Could not migrate to CPU 1
> >
> > Since everything works as expected with v4.0, I ran a bisection and
> > found that commit 3c18d447b3b36a8d ("sched/core: Check for available
> > DL bandwidth in cpuset_cpu_inactive()") is the cause of the regression.
> >
> > I don't know if there's something else affected by that change, but
> > I can consistently reproduce the bug with turbostat.
> >
> > I can provide more info if needed.
>
> Does this commit:
>
> 533445c6e533 sched/core: Fix regression in cpuset_cpu_inactive() for suspend
>
> which is already in Linus's tree, and which should be part of -rc4,
> fix it? Also attached below.
Yes, this fixes the problem, thanks. Sorry for not noticing it.
Gabriele
next prev parent reply other threads:[~2015-05-18 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 15:48 Regression: turbostat stops working after suspend/resume cycle Gabriele Mazzotta
2015-05-18 6:45 ` Ingo Molnar
2015-05-18 7:12 ` Gabriele Mazzotta [this message]
2015-05-18 6:48 ` Regression: turbostat stops working after suspend/resume cycle\ Peter Zijlstra
2015-05-18 7:19 ` Gabriele Mazzotta
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=2225640.WJJBySMURY@xps13 \
--to=gabriele.mzt@gmail.com \
--cc=andrey.semin@intel.com \
--cc=juri.lelli@arm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@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