From: Borislav Petkov <bp@alien8.de>
To: Tejun Heo <tj@kernel.org>
Cc: Michael Wang <wangyun@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at kernel/sched/core.c:1465!
Date: Thu, 20 Sep 2012 20:12:58 +0200 [thread overview]
Message-ID: <20120920181258.GA17181@liondog.tnic> (raw)
In-Reply-To: <20120920171045.GC28934@google.com>
On Thu, Sep 20, 2012 at 10:10:45AM -0700, Tejun Heo wrote:
> Yeah, it's powernow-k8 migrating kworker to a different CPU. It's
> really curious that there are multiple reports of this in this cycle.
> Nothing on workqueue side has changed and powernow-k8 has been
> broken for very long time. The only way this can get triggered is by
> contending on fidvid_mutex in powernow-k8. I suppose something changed
> in such way that this happens with some regularity. Have no specific
> idea what. Anyways, mainline should be okay now.
Yep, it is. I'm running with it for a couple of hours already and no
issues.
Btw, we'd normally investigate why powernow-k8 b0rkage appears now
but after the next merge window, that functionality is moving to
acpi-cpufreq so powernow-k8 should really be only for K8s then.
We'll see how that whole thing pans out as late as 3.7-rc cycle.
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-20 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 9:12 Borislav Petkov
2012-09-20 6:38 ` Michael Wang
2012-09-20 12:58 ` Borislav Petkov
2012-09-20 17:10 ` Tejun Heo
2012-09-20 18:12 ` Borislav Petkov [this message]
2012-09-21 1:45 ` Michael Wang
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=20120920181258.GA17181@liondog.tnic \
--to=bp@alien8.de \
--cc=akinobu.mita@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=wangyun@linux.vnet.ibm.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®