From: Borislav Petkov <bp@alien8.de>
To: Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
lkml <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: kernel BUG at kernel/sched/core.c:1465!
Date: Thu, 20 Sep 2012 14:58:01 +0200 [thread overview]
Message-ID: <20120920125801.GA15045@x1.osrc.amd.com> (raw)
In-Reply-To: <505AB9F7.6030605@linux.vnet.ibm.com>
On Thu, Sep 20, 2012 at 02:38:47PM +0800, Michael Wang wrote:
> Could you please try below patch and see whether the new WARNING
> appear or not?
>
> And cc Tejun Heo <tj@kernel.org> since wq_worker_sleeping() doesn't
> work as it's introduced...
Ok, now that you mentioned workqueues, I remember the powernow-k8
workaround from Tejun a couple of days ago and looking at Linus' tree
from today, he actually merged a fix for exactly that:
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.
I'll update my tree to latest Linus and retest.
Thanks for pointing this out.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-20 12:57 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 [this message]
2012-09-20 17:10 ` Tejun Heo
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=20120920125801.GA15045@x1.osrc.amd.com \
--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 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.