Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756398AbbKRQ1s (ORCPT ); Wed, 18 Nov 2015 11:27:48 -0500 Received: from casper.infradead.org ([85.118.1.10]:40045 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756194AbbKRQ1r (ORCPT ); Wed, 18 Nov 2015 11:27:47 -0500 Date: Wed, 18 Nov 2015 17:27:42 +0100 From: Peter Zijlstra To: kernel test robot Cc: Andi Kleen , lkp@01.org, LKML Subject: Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Message-ID: <20151118162742.GH3816@twins.programming.kicks-ass.net> References: <87fv03u89v.fsf@yhuang-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87fv03u89v.fsf@yhuang-dev.intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1238 Lines: 24 On Wed, Nov 18, 2015 at 02:33:00PM +0800, kernel test robot wrote: > FYI, we noticed the below changes on > > https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core > commit 7aba70e47ca4e961acb5af96d5127e3fad651c7c ("x86, perf: Optimize stack walk user accesses") Of course, that commit no longer exists. I re-create the tree every time I push it, this means that if you report something a few days later, its highly likely its against non-existant commits :/ > [ 21.984049] BUG: unable to handle kernel paging request at 696d2f62 > [ 21.986759] IP: [<4110c023>] perf_prepare_sample+0xcc/0x51d > [ 21.987859] *pdpt = 0000000001a93001 *pde = 0000000000000000 > [ 21.988015] Oops: 0000 [#1] PREEMPT > [ 21.988015] Modules linked in: > [ 21.988015] CPU: 0 PID: 496 Comm: trinity-main Not tainted 4.3.0-01147-g7aba70e #1 That doesn't actually look like something the fingered patch touches. And seeing how its trinity triggering it, I suspect bisection fail. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/