mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* perf_callchain_user oops
@ 2017-03-23  2:58 Dave Jones
  2017-03-23  9:40 ` Peter Zijlstra
  0 siblings, 1 reply; 3+ messages in thread
From: Dave Jones @ 2017-03-23  2:58 UTC (permalink / raw)
  To: Linux Kernel; +Cc: Peter Zijlstra

Not seen this one before..

Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC
CPU: 1 PID: 24420 Comm: trinity-main Not tainted 4.11.0-rc3-think+ #3 
task: ffff8804f4c85440 task.stack: ffffc90001d38000
RIP: 0010:perf_callchain_user+0x11e/0x220
RSP: 0000:ffffc90001d3ba98 EFLAGS: 00010246
RAX: ffff88044c59c2a8 RBX: ffffc90001d3bae8 RCX: 0000562bce3f6e40
RDX: 0000562bce3f6e40 RSI: 00007fffffffeff0 RDI: 0000000000000000
RBP: ffffc90001d3bab8 R08: 00000000bffffff0 R09: 00000000ffffdff0
R10: 0000000000002faa R11: 0000000000002fab R12: ffff8804f4c85440
R13: ffffc90001d3bf58 R14: ffffc90001d3bf58 R15: 0000000000000000
FS:  00007f34b3969b40(0000) GS:ffff880507a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88044c5b4000 CR3: 000000044c584000 CR4: 00000000001406e0
DR0: 00007f34b382e000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
 get_perf_callchain+0x258/0x2b0
 perf_callchain+0x79/0x80
 perf_prepare_sample+0x27e/0x360
 perf_event_output_forward+0x75/0x160
 ? perf_prepare_sample+0x360/0x360
 ? sched_clock_cpu+0x13/0xe0
 __perf_event_overflow+0x54/0xf0
 perf_swevent_overflow+0x9a/0xc0
 perf_swevent_event+0x60/0x80
 ___perf_sw_event+0x152/0x290
 ? ___perf_sw_event+0x32/0x290
 ? debug_smp_processor_id+0x17/0x20
 ? get_lock_stats+0x19/0x50
 ? filemap_map_pages+0x2b7/0x550
 ? filemap_map_pages+0x5/0x550
 ? _raw_spin_unlock+0x31/0x50
 ? debug_smp_processor_id+0x17/0x20
 ? get_lock_stats+0x19/0x50
 __perf_sw_event+0x43/0x90
 __do_page_fault+0x322/0x4f0
 do_page_fault+0x20/0x70
 page_fault+0x1f/0x30
RIP: 0033:0x7f34b3232ca0
RSP: 002b:00007ffe946e1ae8 EFLAGS: 00010206
RAX: 0000562bce3431b0 RBX: 0000562bcdb73210 RCX: 000000000000001d
RDX: 000000000000001d RSI: 0000562bcdb73250 RDI: 0000562bce3431b0
RBP: 0000562bce3f6e40 R08: 00000000000000b1 R09: 00000000000000ff
R10: 00000000bcbf40b2 R11: 00000000834e0b5f R12: 0000562bcdb732b0
R13: 0000000000000003 R14: 0000000000002804 R15: 00007ffe946e1e80
Code: f8 48 8b 0a 85 c0 0f 85 e7 00 00 00 48 8b 52 08 85 c0 0f 85 db 00 00 00 80 7b 12 00 75 aa 48 8b 03 4c 8b 10 4d 8d 5a 01 4c 89 18 <4a> 89 54 d0 08 8b 43 0c 83 c0 01 89 43 0c eb 90 41 8b bd 88 00 
CR2: ffff88044c5b4000

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: perf_callchain_user oops
  2017-03-23  2:58 perf_callchain_user oops Dave Jones
@ 2017-03-23  9:40 ` Peter Zijlstra
  2017-03-23 13:57   ` Dave Jones
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Zijlstra @ 2017-03-23  9:40 UTC (permalink / raw)
  To: Dave Jones, Linux Kernel

On Wed, Mar 22, 2017 at 10:58:04PM -0400, Dave Jones wrote:
> Not seen this one before..
> 
> Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC

That's a write fault reaching no_context() afaict.

> CPU: 1 PID: 24420 Comm: trinity-main Not tainted 4.11.0-rc3-think+ #3 
> task: ffff8804f4c85440 task.stack: ffffc90001d38000
> RIP: 0010:perf_callchain_user+0x11e/0x220
> RSP: 0000:ffffc90001d3ba98 EFLAGS: 00010246
> RAX: ffff88044c59c2a8 RBX: ffffc90001d3bae8 RCX: 0000562bce3f6e40
> RDX: 0000562bce3f6e40 RSI: 00007fffffffeff0 RDI: 0000000000000000
> RBP: ffffc90001d3bab8 R08: 00000000bffffff0 R09: 00000000ffffdff0
> R10: 0000000000002faa R11: 0000000000002fab R12: ffff8804f4c85440
> R13: ffffc90001d3bf58 R14: ffffc90001d3bf58 R15: 0000000000000000
> FS:  00007f34b3969b40(0000) GS:ffff880507a00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff88044c5b4000 CR3: 000000044c584000 CR4: 00000000001406e0
> DR0: 00007f34b382e000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
> Call Trace:
>  get_perf_callchain+0x258/0x2b0
>  perf_callchain+0x79/0x80
>  perf_prepare_sample+0x27e/0x360
>  perf_event_output_forward+0x75/0x160

Any chance you could run scripts/faddr2line on this output?

I cannot seem to match the Code with a defconfig build of that function.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: perf_callchain_user oops
  2017-03-23  9:40 ` Peter Zijlstra
@ 2017-03-23 13:57   ` Dave Jones
  0 siblings, 0 replies; 3+ messages in thread
From: Dave Jones @ 2017-03-23 13:57 UTC (permalink / raw)
  To: Peter Zijlstra; +Cc: Linux Kernel

On Thu, Mar 23, 2017 at 10:40:22AM +0100, Peter Zijlstra wrote:
 > On Wed, Mar 22, 2017 at 10:58:04PM -0400, Dave Jones wrote:
 > > Not seen this one before..
 > > 
 > > Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC
 > 
 > That's a write fault reaching no_context() afaict.
 > 
 > > CPU: 1 PID: 24420 Comm: trinity-main Not tainted 4.11.0-rc3-think+ #3 
 > > task: ffff8804f4c85440 task.stack: ffffc90001d38000
 > > RIP: 0010:perf_callchain_user+0x11e/0x220
 > > RSP: 0000:ffffc90001d3ba98 EFLAGS: 00010246
 > > RAX: ffff88044c59c2a8 RBX: ffffc90001d3bae8 RCX: 0000562bce3f6e40
 > > RDX: 0000562bce3f6e40 RSI: 00007fffffffeff0 RDI: 0000000000000000
 > > RBP: ffffc90001d3bab8 R08: 00000000bffffff0 R09: 00000000ffffdff0
 > > R10: 0000000000002faa R11: 0000000000002fab R12: ffff8804f4c85440
 > > R13: ffffc90001d3bf58 R14: ffffc90001d3bf58 R15: 0000000000000000
 > > FS:  00007f34b3969b40(0000) GS:ffff880507a00000(0000) knlGS:0000000000000000
 > > CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 > > CR2: ffff88044c5b4000 CR3: 000000044c584000 CR4: 00000000001406e0
 > > DR0: 00007f34b382e000 DR1: 0000000000000000 DR2: 0000000000000000
 > > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
 > > Call Trace:
 > >  get_perf_callchain+0x258/0x2b0
 > >  perf_callchain+0x79/0x80
 > >  perf_prepare_sample+0x27e/0x360
 > >  perf_event_output_forward+0x75/0x160
 > 
 > Any chance you could run scripts/faddr2line on this output?
 > 
 > I cannot seem to match the Code with a defconfig build of that function.

$ scripts/faddr2line arch/x86/events/core.o  perf_callchain_user+0x11e 
perf_callchain_user+0x11e/0x220:
perf_callchain_store at include/linux/perf_event.h:1148
 (inlined by) perf_callchain_user at arch/x86/events/core.c:2444

$ scripts/faddr2line kernel/events/callchain.o get_perf_callchain+0x258/0x2b0 perf_callchain+0x79/0x80 
get_perf_callchain+0x258/0x2b0:
get_perf_callchain at kernel/events/callchain.c:237

perf_callchain+0x79/0x80:
perf_callchain at kernel/events/callchain.c:194

$ scripts/faddr2line kernel/events/core.o perf_prepare_sample+0x27e/0x360
perf_prepare_sample+0x27e/0x360:
perf_prepare_sample at kernel/events/core.c:5991

$ scripts/faddr2line kernel/events/core.o perf_event_output_forward+0x75/0x160
perf_event_output_forward+0x75/0x160:
__perf_event_output at kernel/events/core.c:6104
 (inlined by) perf_event_output_forward at kernel/events/core.c:6120

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-23 13:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-23  2:58 perf_callchain_user oops Dave Jones
2017-03-23  9:40 ` Peter Zijlstra
2017-03-23 13:57   ` Dave Jones

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®