From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3911] New: Compilation of systemtap causes the system to crash on p570 system.
Date: Wed, 24 Jan 2007 09:50:00 -0000 [thread overview]
Message-ID: <20070124094941.3911.srinivasa@in.ibm.com> (raw)
My environment is systemtap(systemtap-20070120.tar.bz2),
elfutils(elfutils-0.124.tar.gz), kernel(2.6.18-1.2961.el5), p570 lpared system.
I was compiling latest systemtap source on rhel5(2.6.18-1.2961.el5) kernel and
system dropped to xmon.
Screen looks loke this
==================================
FAIL: probefunc:kernel.statement(0xc00000000005be34) compilation
FAIL: probefunc:kernel.function("scheduler_tick") compilation
FAIL: probefunc:kernel.inline("context_switch") compilation
Running
/home/systemtap/tmp/stap_testing_200701240903/src/testsuite/systemtap.base/simple.exp
...
Running
/home/systemtap/tmp/stap_testing_200701240903/src/testsuite/systemtap.base/timeofday.exp
...
FAIL: timeofday test compilation
Running
/home/systemtap/tmp/stap_testing_200701240903/src/testsuite/systemtap.base/timers.exp
...
Running
/home/systemtap/tmp/stap_testing_200701240903/src/testsuite/systemtap.base/tri.exp
...
Running
/home/systemtap/tmp/stap_testing_200701240903/src/testsuite/systemtap.maps/absentstats.exp
...
/////System crashed/////
=========================================
What xmon shows
=============================
Unable to handle kernel paging request for data at address 0x420000000007f
5:mon> e
cpu 0x5: Vector: 300 (Data Access) at [c000000028a6b310]
pc: c000000000349f40: ._spin_lock+0x20/0x88
lr: c0000000000d6640: .__cache_alloc_node+0x4c/0x174
sp: c000000028a6b590
msr: 8000000000001032
dar: 420000000007f
dsisr: 40000000
current = 0xc00000002ad74430
paca = 0xc000000000464d00
pid = 15804, comm = staprun
5:mon> t
[c000000028a6b610] c0000000000d6640 .__cache_alloc_node+0x4c/0x174
[c000000028a6b6b0] c0000000000d6cc8 .kmem_cache_alloc_node+0x104/0x12c
[c000000028a6b750] d000000000aa6f18 ._stp_map_init+0xa0/0x150
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6b800] d000000000aa70d4 ._stp_pmap_new+0x10c/0x1f0
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6b8c0] d000000000aa7328 ._stp_pmap_new_ix+0x170/0x28c
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6b970] d000000000aa757c .systemtap_module_init+0x138/0x254
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6ba20] d000000000aa76a8 .probe_start+0x10/0x2c
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6baa0] d000000000aa7734 ._stp_handle_start+0x70/0x10c
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6bbb0] d000000000aa79b8 ._stp_proc_write_cmd+0x1e8/0x9b0
[stap_a0def33066a20a930648d1bcbf25f718_896]
[c000000028a6bcf0] c0000000000e026c .vfs_write+0x118/0x200
[c000000028a6bd90] c0000000000e09dc .sys_write+0x4c/0x8c
[c000000028a6be30] c00000000000869c syscall_exit+0x0/0x40
--- Exception: c00 (System Call) at 0000008072e9461c
SP (ffff86eee90) is in userspace
5:mon> di c000000000349f40 (PC value)
c000000000349f40 7d20f828 lwarx r9,r0,r31
c000000000349f44 2c090000 cmpwi r9,0
c000000000349f48 40820010 bne c000000000349f58 #
._spin_lock+0x38/0x88
c000000000349f4c 7c00f92d stwcx. r0,r0,r31
c000000000349f50 40a2fff0 bne c000000000349f40 #
._spin_lock+0x20/0x88
5:mon> r
R00 = 0000000080000005 R16 = 0000000010005b18
R01 = c000000028a6b590 R17 = 0000000010005b10
R02 = c000000000578f80 R18 = 00000ffff86ef390
R03 = 000420000000007f R19 = 0000000010005b38
R04 = 00000000000012d0 R20 = 0000008072d50698
R05 = 0000000000000010 R21 = 0000000010005c28
R06 = 0000000000000030 R22 = 00000000100170c8
R07 = 0000000000000220 R23 = 0000000000000002
R08 = 0000000000000010 R24 = 0000000000000010
R09 = c00000002dfe2980 R25 = 0000000000000800
R10 = c000000000605448 R26 = 0000000000000010
R11 = 0000000000000000 R27 = c00000002dfe2900
R12 = d000000000aaa3f0 R28 = 8000000000009032
R13 = c000000000464d00 R29 = 00000000000012d0
R14 = 00000000100170c0 R30 = c0000000004a59b8
R15 = 0000000010005638 R31 = 000420000000007f
pc = c000000000349f40 ._spin_lock+0x20/0x88
lr = c0000000000d6640 .__cache_alloc_node+0x4c/0x174
msr = 8000000000001032 cr = 24000444
ctr = c0000000000d6cf0 xer = 0000000020000000 trap = 300
dar = 000420000000007f dsisr = 40000000
======================================
Thanks
Srinivasa Ds
--
Summary: Compilation of systemtap causes the system to crash on
p570 system.
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: srinivasa at in dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=3911
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-01-24 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 9:50 srinivasa at in dot ibm dot com [this message]
2007-01-24 15:13 ` [Bug runtime/3911] " mmlnx at us dot ibm dot com
2007-01-25 20:27 ` fche at redhat dot com
2007-01-29 8:31 ` srinivasa at in dot ibm dot com
2007-01-30 7:17 ` srinivasa at in dot ibm dot com
2007-01-30 12:16 ` fche at redhat dot com
2007-01-30 14:37 ` hunt at redhat dot com
2007-01-30 14:38 ` hunt at redhat dot com
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=20070124094941.3911.srinivasa@in.ibm.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).