From: Peter Zijlstra <peterz@infradead.org> To: kernel test robot <ying.huang@linux.intel.com> Cc: Andi Kleen <ak@linux.intel.com>, lkp@01.org, LKML <linux-kernel@vger.kernel.org> Subject: Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Date: Wed, 18 Nov 2015 17:27:42 +0100 [thread overview] Message-ID: <20151118162742.GH3816@twins.programming.kicks-ass.net> (raw) In-Reply-To: <87fv03u89v.fsf@yhuang-dev.intel.com> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org> To: lkp@lists.01.org Subject: Re: [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Date: Wed, 18 Nov 2015 17:27:42 +0100 [thread overview] Message-ID: <20151118162742.GH3816@twins.programming.kicks-ass.net> (raw) In-Reply-To: <87fv03u89v.fsf@yhuang-dev.intel.com> [-- Attachment #1: Type: text/plain, Size: 1012 bytes --] 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.
next prev parent reply other threads:[~2015-11-18 16:27 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-18 6:33 [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 kernel test robot 2015-11-18 6:33 ` kernel test robot 2015-11-18 16:27 ` Peter Zijlstra [this message] 2015-11-18 16:27 ` Peter Zijlstra 2015-11-19 0:38 ` [lkp] " Huang, Ying 2015-11-19 0:38 ` Huang, Ying 2015-11-19 11:14 ` [lkp] " Peter Zijlstra 2015-11-19 11:14 ` Peter Zijlstra 2015-11-20 0:45 ` [lkp] " Huang, Ying 2015-11-20 0:45 ` Huang, Ying 2015-11-19 19:18 ` [lkp] " Andi Kleen 2015-11-19 19:18 ` Andi Kleen 2015-11-20 0:38 ` [LKP] [lkp] " Huang, Ying 2015-11-20 0:38 ` Huang, Ying
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20151118162742.GH3816@twins.programming.kicks-ass.net \ --to=peterz@infradead.org \ --cc=ak@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@01.org \ --cc=ying.huang@linux.intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.