All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang\, Ying" <ying.huang@intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>, <lkp@01.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62
Date: Fri, 20 Nov 2015 08:38:24 +0800	[thread overview]
Message-ID: <87oaepo67z.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20151119191803.GB8802@tassilo.jf.intel.com> (Andi Kleen's message of "Thu, 19 Nov 2015 11:18:03 -0800")

Hi, Andi,

Andi Kleen <ak@linux.intel.com> writes:

> On Wed, Nov 18, 2015 at 05:27:42PM +0100, Peter Zijlstra wrote:
>> 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.
>
> Ok. I assume it's not caused by my patch.  Let me know if that is wrong.

Sorry about false positive.

> I also pushed the patch before to my tree (which is 0day tested) and there
> was no such report (but of course trinity is somewhat random).
>
> BTW if you're going to test trinity for perf it may be better to use
> Vince Weaver's version here
>
> https://github.com/deater/perf_event_tests
>
> which has more coverage for perf than normal trinity.

Thanks for your information.  We will integrate it into 0day tests.

Best Regards,
Huang, Ying

WARNING: multiple messages have this Message-ID (diff)
From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62
Date: Fri, 20 Nov 2015 08:38:24 +0800	[thread overview]
Message-ID: <87oaepo67z.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20151119191803.GB8802@tassilo.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

Hi, Andi,

Andi Kleen <ak@linux.intel.com> writes:

> On Wed, Nov 18, 2015 at 05:27:42PM +0100, Peter Zijlstra wrote:
>> 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.
>
> Ok. I assume it's not caused by my patch.  Let me know if that is wrong.

Sorry about false positive.

> I also pushed the patch before to my tree (which is 0day tested) and there
> was no such report (but of course trinity is somewhat random).
>
> BTW if you're going to test trinity for perf it may be better to use
> Vince Weaver's version here
>
> https://github.com/deater/perf_event_tests
>
> which has more coverage for perf than normal trinity.

Thanks for your information.  We will integrate it into 0day tests.

Best Regards,
Huang, Ying

  reply	other threads:[~2015-11-20  0:38 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 ` [lkp] " Peter Zijlstra
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     ` Huang, Ying [this message]
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=87oaepo67z.fsf@yhuang-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=ak@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=peterz@infradead.org \
    /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: link
Be 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.