From: Vince Weaver <vincent.weaver@maine.edu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [perf] more perf_fuzzer memory corruption
Date: Mon, 5 May 2014 15:51:42 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1405051546290.31072@vincent-weaver-1.umelst.maine.edu> (raw)
In-Reply-To: <20140505193629.GB11096@twins.programming.kicks-ass.net>
On Mon, 5 May 2014, Peter Zijlstra wrote:
> > It looks like it is stuck repeating this forever:
> > perf_fuzzer-5256 [000] 275.943049: kmalloc: (T.1262+0xe) call_site=ffffffff810d022f ptr=0xffff8800cb028400 bytes_req=216 bytes_alloc=256 gfp_flags=GFP_KERNEL|GFP_ZERO
> > perf_fuzzer-5256 [000] 275.943057: function: perf_lock_task_context
> > perf_fuzzer-5256 [000] 275.943057: function: alloc_perf_context
> > and memory is slowly leaking away.
>
> Oh, usually when my WSM gets funny like this and I enable the tracer it
> just stops being a computer and starts being a brick.
I'd give you more details from the tracer but that's all lost in the
middle of a dreaded
CPU:1 [87702 EVENTS DROPPED]
incident.
Though I can try again to see if I can get a better trace.
Also possibly related, the following was
generated at least one of the times things got wedged (according to my
notes this same warning has also been triggered previously by Dave Jones
and trinity but I don't know if it's the same problem or not):
[ 804.036004] WARNING: CPU: 1 PID: 26033 at kernel/events/core.c:2398 task_ctx_sched_out+0x49/0x6e()
[ 804.036004] Modules linked in: cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative f71882fg mcs7830 usbnet evdev video wmi acpi_cpufreq ohci_pci pcspkr psmouse button processor thermal_sys coretemp serio_raw ohci_hcd i2c_nforce2 sg ehci_pci ehci_hcd sd_mod usbcore usb_common
[ 804.036004] CPU: 1 PID: 26033 Comm: perf_fuzzer Tainted: G D 3.15.0-rc4+ #44
[ 804.036004] Hardware name: AOpen DE7000/nMCP7ALPx-DE R1.06 Oct.19.2012, BIOS 080015 10/19/2012
[ 804.036004] 000000000000095e ffff880039ac3c08 ffffffff81539016 000000000000095e
[ 804.036004] 0000000000000000 ffff880039ac3c48 ffffffff8103fcb9 0000000000000000
[ 804.036004] ffffffff810ca939 ffff88011fc95b08 ffff8800cbb6a010 0000000000000000
[ 804.036004] Call Trace:
[ 804.036004] [<ffffffff81539016>] dump_stack+0x49/0x5b
[ 804.036004] [<ffffffff8103fcb9>] warn_slowpath_common+0x81/0x9b
[ 804.036004] [<ffffffff810ca939>] ? task_ctx_sched_out+0x49/0x6e
[ 804.036004] [<ffffffff8103fced>] warn_slowpath_null+0x1a/0x1c
[ 804.036004] [<ffffffff810ca939>] task_ctx_sched_out+0x49/0x6e
[ 804.036004] [<ffffffff810d0111>] perf_event_exit_task+0xee/0x1fe
[ 804.036004] [<ffffffff8105e91c>] ? switch_task_namespaces+0x1d/0x51
[ 804.036004] [<ffffffff81041bb6>] do_exit+0x400/0x942
[ 804.036004] [<ffffffff810f3d50>] ? do_read_fault+0x169/0x263
[ 804.036004] [<ffffffff810d3b51>] ? unlock_page+0x27/0x2c
[ 804.036004] [<ffffffff81042170>] do_group_exit+0x78/0xa0
[ 804.036004] [<ffffffff8104f378>] get_signal_to_deliver+0x46d/0x48a
[ 804.036004] [<ffffffff810bc037>] ? function_trace_call+0xc8/0xf2
[ 804.036004] [<ffffffff81002526>] do_signal+0x46/0x5e8
[ 804.036004] [<ffffffff810b8279>] ? __trace_buffer_unlock_commit+0x3c/0x44
[ 804.036004] [<ffffffff8100c176>] ? ftrace_raw_event_sys_exit+0x4a/0x72
[ 804.036004] [<ffffffff81002af4>] do_notify_resume+0x2c/0x64
[ 804.036004] [<ffffffff8153c235>] retint_signal+0x3d/0x78
[ 804.036004] ---[ end trace 6cadd738b5f7eb96 ]---
next prev parent reply other threads:[~2014-05-05 19:48 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 21:37 [perf] more perf_fuzzer memory corruption Vince Weaver
2014-04-15 21:49 ` Thomas Gleixner
2014-04-16 3:21 ` Vince Weaver
2014-04-16 4:18 ` Vince Weaver
2014-04-16 14:15 ` Peter Zijlstra
2014-04-16 17:30 ` Vince Weaver
2014-04-16 17:43 ` Vince Weaver
2014-04-16 17:47 ` Peter Zijlstra
2014-04-17 9:48 ` Ingo Molnar
2014-04-17 11:45 ` Peter Zijlstra
2014-04-17 14:22 ` Ingo Molnar
2014-04-17 14:42 ` Vince Weaver
2014-04-17 14:54 ` Peter Zijlstra
2014-04-17 15:35 ` Vince Weaver
2014-04-18 14:45 ` Vince Weaver
2014-04-18 14:51 ` Vince Weaver
2014-04-18 15:23 ` Peter Zijlstra
2014-04-18 16:59 ` Peter Zijlstra
2014-04-18 17:15 ` Peter Zijlstra
2014-04-23 20:58 ` Vince Weaver
2014-04-25 2:51 ` Vince Weaver
2014-04-28 14:21 ` Vince Weaver
2014-04-28 19:38 ` Vince Weaver
2014-04-29 9:46 ` Peter Zijlstra
2014-04-29 18:21 ` Vince Weaver
2014-04-29 19:01 ` Peter Zijlstra
2014-04-29 20:59 ` Vince Weaver
2014-04-30 18:44 ` Peter Zijlstra
2014-04-30 21:08 ` Vince Weaver
2014-04-30 22:51 ` Thomas Gleixner
2014-05-01 10:26 ` Peter Zijlstra
2014-05-01 11:50 ` Peter Zijlstra
2014-05-01 12:35 ` Thomas Gleixner
2014-05-01 13:12 ` Peter Zijlstra
2014-05-01 13:29 ` Thomas Gleixner
2014-05-01 13:22 ` Vince Weaver
2014-05-01 14:07 ` Vince Weaver
2014-05-01 14:27 ` Vince Weaver
2014-05-01 15:09 ` Peter Zijlstra
2014-05-01 15:50 ` Vince Weaver
2014-05-01 16:31 ` Thomas Gleixner
2014-05-01 17:18 ` Vince Weaver
2014-05-01 18:49 ` Vince Weaver
2014-05-01 21:32 ` Vince Weaver
2014-05-02 11:15 ` Peter Zijlstra
2014-05-02 15:42 ` Peter Zijlstra
2014-05-02 16:22 ` Vince Weaver
2014-05-02 16:22 ` Peter Zijlstra
2014-05-02 16:43 ` Vince Weaver
2014-05-02 17:27 ` Peter Zijlstra
2014-05-02 17:46 ` Vince Weaver
2014-05-02 19:12 ` Thomas Gleixner
2014-05-02 20:15 ` Vince Weaver
2014-05-02 20:45 ` Thomas Gleixner
2014-05-03 2:32 ` Vince Weaver
2014-05-03 3:02 ` Vince Weaver
2014-05-03 7:33 ` Peter Zijlstra
2014-05-05 9:31 ` Peter Zijlstra
2014-05-05 16:00 ` Vince Weaver
2014-05-05 17:10 ` Vince Weaver
2014-05-05 17:14 ` Peter Zijlstra
2014-05-05 18:47 ` Vince Weaver
2014-05-05 19:36 ` Peter Zijlstra
2014-05-05 19:51 ` Vince Weaver [this message]
2014-05-06 1:06 ` Vince Weaver
2014-05-06 16:57 ` Vince Weaver
2014-05-07 16:45 ` Peter Zijlstra
2014-05-08 10:40 ` [tip:perf/core] perf: Fix perf_event_init_context() tip-bot for Peter Zijlstra
2014-05-05 17:29 ` [perf] more perf_fuzzer memory corruption Ingo Molnar
2014-05-06 4:51 ` Vince Weaver
2014-05-06 17:06 ` Vince Weaver
2014-05-07 19:12 ` Ingo Molnar
2014-05-07 19:11 ` Ingo Molnar
2014-05-08 10:40 ` [tip:perf/core] perf: Fix race in removing an event tip-bot for Peter Zijlstra
2014-05-02 17:06 ` [perf] more perf_fuzzer memory corruption Vince Weaver
2014-05-02 17:04 ` Peter Zijlstra
2014-04-29 19:26 ` Steven Rostedt
2014-04-29 8:52 ` Peter Zijlstra
2014-04-29 18:11 ` Vince Weaver
2014-04-29 19:21 ` Steven Rostedt
2014-04-28 17:48 ` Thomas Gleixner
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=alpine.DEB.2.10.1405051546290.31072@vincent-weaver-1.umelst.maine.edu \
--to=vincent.weaver@maine.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.