From: Sachin Sant <sachinp@in.ibm.com>
To: rostedt@goodmis.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FTRACE] Enabling function_graph causes OOPS
Date: Wed, 09 Sep 2009 11:57:46 +0530 [thread overview]
Message-ID: <4AA74AE2.5090001@in.ibm.com> (raw)
In-Reply-To: <1252458303.20985.10.camel@gandalf.stny.rr.com>
Steven Rostedt wrote:
> I'm going through old email, and I found this. Do you still see this
> error. I don't recall seeing it myself.
>
I can still recreate this with 31-rc9. When i enable tracing
with function_graph i notice the following oops. This happens
only once. Later if i try to enable/disable tracing i don't
get this oops message. This behavior is observed only with
function_graph. Other tracers work fine.
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=1024 NUMA pSeries
Modules linked in: ipv6 fuse loop dm_mod sr_mod ehea ibmveth sg cdrom sd_mod crc_t10dif ibmvscsic scsi_transport_srp scsi_tgt scsi_mod
NIP: c000000000008f30 LR: c000000000008f04 CTR: 80000000000f6d68
REGS: c00000003e98f560 TRAP: 0300 Not tainted (2.6.31-rc9)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 24000422 XER: 00000020
DAR: 0000000000000008, DSISR: 0000000040000000
TASK = c00000003e953b20[2483] 'irqbalance' THREAD: c00000003e98c000 CPU: 1
GPR00: c000000000008f04 c00000003e98f7e0 d00000000117ed38 0000000000000000
GPR04: 0000000000000000 0000000066000000 00000000000010bf 0000000000000000
GPR08: 0000000000000000 800000010021bb40 00000000000000ff 800000010021bb60
GPR12: 0000000000000002 c000000001032800 0000000000000000 ffffffffeffdff68
GPR16: 00000fffa39fd6a0 00000fffa39e6c38 c00000003ebe9c38 fffffffffffff000
GPR20: c00000002a6cf980 c00000003e98fdf8 c00000003e98fba8 00000fffa1740000
GPR24: fffffffffffff000 8001000003000000 ffe0000000000000 0000000000000009
GPR28: c00000003db40000 0000000000020000 d00000000117da78 c00000003e98f850
NIP [c000000000008f30] .mod_return_to_handler+0x2c/0x64
LR [c000000000008f04] .mod_return_to_handler+0x0/0x64
Call Trace:
[c00000003e98f7e0] [c00000002a6cf980] 0xc00000002a6cf980 (unreliable)
[c00000003e98f850] [c000000000008f04] .mod_return_to_handler+0x0/0x64
[c00000003e98f900] [c000000000008f04] .mod_return_to_handler+0x0/0x64
[c00000003e98f9a0] [c000000000008f04] .mod_return_to_handler+0x0/0x64
[c00000003e98fa30] [c000000000008ed0] .return_to_handler+0x0/0x34 (.bad_page_fault+0xc8/0xe8)
[c00000003e98fb30] [c000000000008ed0] .return_to_handler+0x0/0x34 (handle_page_fault+0x3c/0x5c)
[c00000003e98fc20] [c000000000008ed0] .return_to_handler+0x0/0x34 (.ehea_h_query_ehea_port+0x74/0x9c [ehea])
[c00000003e98fcd0] [c000000000008ed0] .return_to_handler+0x0/0x34 (.ehea_get_stats+0xa0/0x1d0 [ehea])
[c00000003e98fd80] [c000000000008ed0] .return_to_handler+0x0/0x34 (.dev_get_stats+0x50/0xec)
[c00000003e98fe30] [c000000000008ed0] .return_to_handler+0x0/0x34 (.dev_seq_show+0x5c/0x140)
Instruction dump:
4e800020 f881ffe0 f861ffe8 f841fff0 fbe1fff8 7c3f0b78 f821ff91 3c800000
60840000 788407c6 64840000 60840000 <e8440008> 48126375 60000000 7c6803a6
---[ end trace bb43efc994aed790 ]---
function_graph traces are recorded and can be retrieved using
/sys/kernel/debug/tracing/trace.
1) 3.936 us | }
1) | .release_console_sem() {
1) 0.594 us | ._spin_lock_irqsave();
1) 0.560 us | ._call_console_drivers();
1) 0.580 us | ._call_console_drivers();
1) 0.582 us | ._spin_lock_irqsave();
1) | .up() {
1) 0.592 us | ._spin_lock_irqsave();
1) 0.556 us | ._spin_unlock_irqrestore();
1) 2.842 us | }
1) 0.588 us | ._spin_unlock_irqrestore();
1) 9.750 us | }
1) + 75.274 us | }
1) | .die() {
1) | .oops_enter() {
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-09-09 6:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 10:26 [FTRACE] Enabling function_graph causes OOPS Sachin Sant
2009-07-14 22:45 ` Steven Rostedt
2009-08-03 10:40 ` Sachin Sant
2009-09-09 1:05 ` Steven Rostedt
2009-09-09 6:27 ` Sachin Sant [this message]
2009-09-09 19:42 ` Steven Rostedt
2009-09-10 5:32 ` Sachin Sant
2009-09-11 3:05 ` Steven Rostedt
2009-09-11 4:26 ` Sachin Sant
2009-09-11 18:05 ` Steven Rostedt
2009-09-13 4:07 ` Steven Rostedt
2009-09-13 4:37 ` Benjamin Herrenschmidt
2009-09-13 13:21 ` Steven Rostedt
2009-09-13 20:25 ` Benjamin Herrenschmidt
2009-09-14 8:00 ` Benjamin Herrenschmidt
2009-10-05 13:25 ` Steven Rostedt
2009-10-05 20:20 ` Benjamin Herrenschmidt
2009-10-05 20:37 ` Steven Rostedt
2009-10-07 8:56 ` Sachin Sant
2009-10-07 9:10 ` Benjamin Herrenschmidt
2009-10-08 14:51 ` [PATCH] Ftrace : fix function_graph tracer OOPS Sachin Sant
2009-10-14 3:01 ` Steven Rostedt
2009-10-14 6:13 ` Sachin Sant
2009-10-14 6:15 ` Benjamin Herrenschmidt
2009-10-14 12:12 ` Steven Rostedt
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=4AA74AE2.5090001@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).