From: Tejun Heo <tj@kernel.org>
To: Borislav Petkov <bp@alien8.de>,
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 10:10:45 -0700 [thread overview]
Message-ID: <20120920171045.GC28934@google.com> (raw)
In-Reply-To: <20120920125801.GA15045@x1.osrc.amd.com>
Hello, guys.
On Thu, Sep 20, 2012 at 02:58:01PM +0200, Borislav Petkov wrote:
> commit c5c473e29c641380aef4a9d1f9c39de49219980f
> Merge: 925a6f0bf8bd 6889125b8b4e
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Wed Sep 19 11:00:07 2012 -0700
>
> Merge branch 'for-3.6-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
>
> Pull workqueue / powernow-k8 fix from Tejun Heo:
> "This is the fix for the bug where cpufreq/powernow-k8 was tripping
> BUG_ON() in try_to_wake_up_local() by migrating workqueue worker to a
> different CPU.
>
> and this is exactly the same BUG_ON I'm hitting. and powernowk8_target
> is in the stack trace so it has to be the same issue.
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.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-09-20 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 9:12 kernel BUG at kernel/sched/core.c:1465! Borislav Petkov
2012-09-20 6:38 ` Michael Wang
2012-09-20 12:58 ` Borislav Petkov
2012-09-20 17:10 ` Tejun Heo [this message]
2012-09-20 18:12 ` Borislav Petkov
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=20120920171045.GC28934@google.com \
--to=tj@kernel.org \
--cc=akinobu.mita@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 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.