From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754575AbdJIP25 (ORCPT ); Mon, 9 Oct 2017 11:28:57 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:34604 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754195AbdJIP2z (ORCPT ); Mon, 9 Oct 2017 11:28:55 -0400 Date: Mon, 9 Oct 2017 17:28:47 +0200 From: Peter Zijlstra To: Fengguang Wu Cc: Josh Poimboeuf , Linus Torvalds , Byungchul Park , Ingo Molnar , Linux Kernel Mailing List , LKP Subject: Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2 Message-ID: <20171009152847.kwo5ifr4lftgm6va@hirez.programming.kicks-ass.net> References: <20171003140634.r2jzujgl62ox4uzh@wfg-t540p.sh.intel.com> <20171005130146.pmayo6owv362zfai@treble> <20171005145414.4bbcr3jornabes7c@treble> <20171009105055.7vfk2ncolyouzunb@hirez.programming.kicks-ass.net> <20171009122113.nj2tn22mt2oxptvr@wfg-t540p.sh.intel.com> <20171009125504.gpb3z4xtsstq756k@wfg-t540p.sh.intel.com> <20171009132605.6uosfs22qbg2bysj@treble> <20171009141706.5xbqsvgwer4a246s@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171009141706.5xbqsvgwer4a246s@wfg-t540p.sh.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 09, 2017 at 10:17:06PM +0800, Fengguang Wu wrote: > It works! I tried 500 boots and only find 1 occurrence of this error, > which looks irrelevant to the current issue. OK, I'll go write a Changelog for the lockdep patch. > > [ 187.855027] init: plymouth-splash main process (418) terminated with status 1 > [ 187.953296] init: networking main process (419) terminated with status 1 > [ 191.697721] ------------[ cut here ]------------ > [ 191.699318] WARNING: CPU: 0 PID: 424 at kernel/locking/lockdep.c:3928 check_flags+0x119/0x1b0 Would still like to get around sorting that one though. From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============0707899508100843920==" MIME-Version: 1.0 From: Peter Zijlstra To: lkp@lists.01.org Subject: Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2 Date: Mon, 09 Oct 2017 17:28:47 +0200 Message-ID: <20171009152847.kwo5ifr4lftgm6va@hirez.programming.kicks-ass.net> In-Reply-To: <20171009141706.5xbqsvgwer4a246s@wfg-t540p.sh.intel.com> List-Id: --===============0707899508100843920== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Mon, Oct 09, 2017 at 10:17:06PM +0800, Fengguang Wu wrote: > It works! I tried 500 boots and only find 1 occurrence of this error, > which looks irrelevant to the current issue. OK, I'll go write a Changelog for the lockdep patch. > = > [ 187.855027] init: plymouth-splash main process (418) terminated with s= tatus 1 > [ 187.953296] init: networking main process (419) terminated with status= 1 > [ 191.697721] ------------[ cut here ]------------ > [ 191.699318] WARNING: CPU: 0 PID: 424 at kernel/locking/lockdep.c:3928 = check_flags+0x119/0x1b0 Would still like to get around sorting that one though. --===============0707899508100843920==--