Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1272350 > unrolled thread
| Started by | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| First post | 2015-11-18 17:30 +0100 |
| Last post | 2015-11-20 01:40 +0100 |
| Articles | 6 — 4 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Peter Zijlstra <peterz@infradead.org> - 2015-11-18 17:30 +0100
Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 "Huang\, Ying" <ying.huang@linux.intel.com> - 2015-11-19 01:40 +0100
Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Peter Zijlstra <peterz@infradead.org> - 2015-11-19 12:20 +0100
Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 "Huang\, Ying" <ying.huang@linux.intel.com> - 2015-11-20 01:50 +0100
Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Andi Kleen <ak@linux.intel.com> - 2015-11-19 20:20 +0100
Re: [LKP] [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 "Huang\, Ying" <ying.huang@intel.com> - 2015-11-20 01:40 +0100
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2015-11-18 17:30 +0100 |
| Subject | Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 |
| Message-ID | <qwdMm-5n6-9@gated-at.bofh.it> |
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/
[toc] | [next] | [standalone]
| From | "Huang\, Ying" <ying.huang@linux.intel.com> |
|---|---|
| Date | 2015-11-19 01:40 +0100 |
| Subject | Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 |
| Message-ID | <qwlqy-23w-15@gated-at.bofh.it> |
| In reply to | #1272350 |
Hi, Peter,
Peter Zijlstra <peterz@infradead.org> writes:
> 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 :/
I am sorry about this. We will try our best to reach real 0day
reporting.
>> [ 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.
Thanks for reminding, we will check the bisection process.
Best Regards,
Huang, Ying
--
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/
[toc] | [prev] | [next] | [standalone]
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2015-11-19 12:20 +0100 |
| Message-ID | <qwvpT-7U-1@gated-at.bofh.it> |
| In reply to | #1272716 |
On Thu, Nov 19, 2015 at 08:38:58AM +0800, Huang, Ying wrote:
> Hi, Peter,
>
> Peter Zijlstra <peterz@infradead.org> writes:
>
> > 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 :/
>
> I am sorry about this. We will try our best to reach real 0day
> reporting.
Is there any way I can monitor the progress of a given tree through the
whole 0-day testing farm? I know the various compile tests are complete
because those send email. But after that it goes off into magic land
without further feedback, unless something bad happens as per this
report.
It would be useful for me to know how far along a given tree is before I
zap it.
--
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/
[toc] | [prev] | [next] | [standalone]
| From | "Huang\, Ying" <ying.huang@linux.intel.com> |
|---|---|
| Date | 2015-11-20 01:50 +0100 |
| Subject | Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 |
| Message-ID | <qwI3M-8m5-17@gated-at.bofh.it> |
| In reply to | #1273040 |
Hi, Peter,
Peter Zijlstra <peterz@infradead.org> writes:
> On Thu, Nov 19, 2015 at 08:38:58AM +0800, Huang, Ying wrote:
>> Hi, Peter,
>>
>> Peter Zijlstra <peterz@infradead.org> writes:
>>
>> > 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 :/
>>
>> I am sorry about this. We will try our best to reach real 0day
>> reporting.
>
> Is there any way I can monitor the progress of a given tree through the
> whole 0-day testing farm? I know the various compile tests are complete
> because those send email. But after that it goes off into magic land
> without further feedback, unless something bad happens as per this
> report.
>
> It would be useful for me to know how far along a given tree is before I
> zap it.
So far, we have no such features like 'boot/functionality/performance
test complete' or progress report email. But I think that could be a
useful features for many people. We will add it to the TODO of 0day.
Best Regards,
Huang, Ying
--
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/
[toc] | [prev] | [next] | [standalone]
| From | Andi Kleen <ak@linux.intel.com> |
|---|---|
| Date | 2015-11-19 20:20 +0100 |
| Message-ID | <qwCUq-57G-23@gated-at.bofh.it> |
| In reply to | #1272350 |
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.
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.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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/
[toc] | [prev] | [next] | [standalone]
| From | "Huang\, Ying" <ying.huang@intel.com> |
|---|---|
| Date | 2015-11-20 01:40 +0100 |
| Subject | Re: [LKP] [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 |
| Message-ID | <qwHU6-8iz-9@gated-at.bofh.it> |
| In reply to | #1273427 |
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
--
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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web