From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751140AbdAaILk (ORCPT <rfc822;w@1wt.eu>);
        Tue, 31 Jan 2017 03:11:40 -0500
Received: from mout.gmx.net ([212.227.15.18]:62124 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750726AbdAaIKH (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 31 Jan 2017 03:10:07 -0500
Message-ID: <1485850069.4434.1.camel@gmx.de>
Subject: Re: WARNING: CPU: 1 PID: 15 at kernel/sched/sched.h:804
 assert_clock_updated.isra.62.part.63+0x25/0x27
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
        lkml <linux-kernel@vger.kernel.org>,
        Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@elte.hu>,
        Borislav Petkov <bp@alien8.de>
Date: Tue, 31 Jan 2017 09:07:49 +0100
In-Reply-To: <20170131074541.GB17636@gmail.com>
References: <1485588065.4181.7.camel@gmx.de>
         <20170130115942.GK31613@codeblueprint.co.uk>
         <1485843569.4423.8.camel@gmx.de> <20170131072839.GA10834@gmail.com>
         <1485848151.4423.10.camel@gmx.de> <20170131074541.GB17636@gmail.com>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Evolution 3.16.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:EICsRBDwOISvPLF7qPGNTKakpw00pBFXmdYF38FPTCfy7HW3mVn
 5eQJu2L35OydbJ0w+CNJ1sMbHN4rFFS6mi9FWPnItQm4fvITrtXMuneauq6xffLyyp7MCBf
 FVfJRGII5r6EX9GlQJ408HmOt4i2zpGN/aY9u+3S1n5SHcuy9+h/g3OzLfz6Pr5y2YwEwVd
 +84E8+ozhGV8W8MRcJ09g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:9FHWVZUVLHk=:ecs56hyJwDJnRiJ63BhHfy
 RI8+PwvgaASqznFHtfmnX35qYtqNNFek13C4aKzW82iDPRZ1z6QO6oWiMul8oyOerV/aU/Ny1
 wyJkTJpF35aImPX5/e2wzY/dwNBHsbBmW6q0pewkF5Ux2rXxigVHo2fEDp6/z04fgdg7rzFuV
 vLhz3LUU3167URu+CNVwhaHLbQp+6RtUFkt3DBGp7H2raiGXU15Cq8kn0D70NFlM9zodKqMiM
 wjYQmAayi7yDTCrpNRsXfGg3nxtHFvh0LXShLOEXYmt1xO/gt+IVNNQrg1ZBKxt8OmhlBgwl/
 E3IlWD5vfYwiP+236Octvw6vOmcBqSIbi8sXbwwY7ToDxBKYEupZ6OYCQzztSCsBS4JWhVKKT
 JvROMe2xB/2ZUlUWawaaMgSdpr4g2NKX/16rGt402UIh7WqPGS0D+mOPn1giatR1pr3AB70B9
 y8gK9Vi5JFxhwdl2+uaO5F1g2o1v4rrjHDPbsFW48to3x4fRZgbP7B6eIuZ1DRz7mzXGhuxGf
 btcH9MA3dx5fu7phtk0pgUA+4sQoQv2tOTHb5fol8/yDeiLq7WUz5kwFFX2aIUKppsNcjGkY6
 yaUorYSsFoHdZNCb4pJyfF4qwR97rNvHnJwWNTIgeWwUAngXIYsIRS6PlBXNGh5lu+A7tqQlc
 SuO6thJLXB3LUVmedlyLGfqhlpXGlKJub+/CEnjG7L0bPivonFOzbyClf95oZXveLulE05alF
 IwC1iFqqyxs/YxqZHw8awpr0DlGok4bM6N9O8A3pvgoyapQZsSzNnJYGmkEa4+sNOuZpW1ulp
 OCiGDxZ
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 2017-01-31 at 08:45 +0100, Ingo Molnar wrote:
> * Mike Galbraith <efault@gmx.de> wrote:
> 
> > On Tue, 2017-01-31 at 08:28 +0100, Ingo Molnar wrote:
> > > * Mike Galbraith <efault@gmx.de> wrote:
> > 
> > > > Weeell, I'll have to take your word for it, as tip g35669bb7fd46 grew
> > > > an early boot brick problem.
> > > 
> > > That's bad - could you perhaps try to bisect it? All recently queued up patches 
> > > that could cause such problems should be readily bisectable.
> > 
> > Yeah, I'll give it a go as soon as I get some other stuff done.
> 
> Please double check whether -tip f18a8a0143b1 works for you (latestest -tip 
> freshly pushed out), it might be that my bogus conflict resolution of a 
> x86/microcode conflict is what caused your boot problems?

Oh darn, it's a nogo.  Back to plan A.

	-Mike