From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751126AbdAaHpx (ORCPT ); Tue, 31 Jan 2017 02:45:53 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34659 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750726AbdAaHpp (ORCPT ); Tue, 31 Jan 2017 02:45:45 -0500 Date: Tue, 31 Jan 2017 08:45:41 +0100 From: Ingo Molnar To: Mike Galbraith Cc: Matt Fleming , lkml , Peter Zijlstra , Ingo Molnar , Borislav Petkov Subject: Re: WARNING: CPU: 1 PID: 15 at kernel/sched/sched.h:804 assert_clock_updated.isra.62.part.63+0x25/0x27 Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485848151.4423.10.camel@gmx.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Mike Galbraith wrote: > On Tue, 2017-01-31 at 08:28 +0100, Ingo Molnar wrote: > > * Mike Galbraith 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? Thanks, Ingo