From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>,
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: Fri, 21 Sep 2012 09:45:46 +0800 [thread overview]
Message-ID: <505BC6CA.4060602@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120920125801.GA15045@x1.osrc.amd.com>
On 09/20/2012 08:58 PM, Borislav Petkov wrote:
> 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.
Happen to see the problem solved.
Regards,
Michael Wang
>
> Thanks for pointing this out.
>
prev parent reply other threads:[~2012-09-21 1:45 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
2012-09-20 18:12 ` Borislav Petkov
2012-09-21 1:45 ` Michael Wang [this message]
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=505BC6CA.4060602@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=akinobu.mita@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.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