From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753044Ab2ITM5z (ORCPT ); Thu, 20 Sep 2012 08:57:55 -0400 Received: from mail.skyhub.de ([78.46.96.112]:43609 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392Ab2ITM5x (ORCPT ); Thu, 20 Sep 2012 08:57:53 -0400 Date: Thu, 20 Sep 2012 14:58:01 +0200 From: Borislav Petkov To: Michael Wang Cc: Peter Zijlstra , Akinobu Mita , lkml , Tejun Heo Subject: Re: kernel BUG at kernel/sched/core.c:1465! Message-ID: <20120920125801.GA15045@x1.osrc.amd.com> Mail-Followup-To: Borislav Petkov , Michael Wang , Peter Zijlstra , Akinobu Mita , lkml , Tejun Heo References: <20120919091230.GA25576@liondog.tnic> <505AB9F7.6030605@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <505AB9F7.6030605@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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 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.