linux-kernel - Re: kernel BUG at kernel/sched/core.c:1465!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2012 20:12:58 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Tejun Heo <tj@...nel.org>
Cc:	Michael Wang <wangyun@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Akinobu Mita <akinobu.mita@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: kernel BUG at kernel/sched/core.c:1465!

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/