From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/12645] New: exelib.exp failures (and hung stapio's) on s390x
Date: Wed, 06 Apr 2011 20:08:00 -0000 [thread overview]
Message-ID: <bug-12645-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=12645
Summary: exelib.exp failures (and hung stapio's) on s390x
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
kernel: 2.6.32-125.el6.s390x
On s390x, the exelib.exp testcase gets 72 passes and 124 unexpected failures.
Even though commit 273e7bf updated that test to kill stap when the test fails,
9 stapio processes get left behind:
# ps x | fgrep stapio
10937 ? Rl 8:23 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-debug-uprobeslibgcc-O3default-prelink-debug_exe -u
/tmp/stapz81ubu/stap_3124cb608964f80ab49b78d36c0d613e_10311.ko
11387 ? Rl 7:19 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-sep-debug-uprobeslibgcc-O3default-prelink-debug_exe -u
/tmp/stapbnXVPL/stap_e0453cf16865566fe0db1126fc5ba817_10371.ko
11851 ? Rl 6:25 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-pie-debug-uprobeslibgcc-O3default-prelink-debug_exe -u
/tmp/stapuhQmTJ/stap_2b7361788bf0f1ab00a7ef97d97882f7_10325.ko
12324 ? Rl 5:35 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-debug_exe
-u /tmp/stapsFzAmD/stap_632f491261ce1ffd759ac0b8972667fd_10385.ko
14581 ? Rl 4:08 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-debug-uprobeslibgcc-O3default-prelink-sep-debug-after_exe
-u /tmp/stapMqlmmN/stap_23d8e70dafb27f52d8aebd7623048c1d_10611.ko
15030 ? Rl 3:39 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug-after_exe
-u /tmp/stapz9fPix/stap_aaca3cde249673e0a0f3f3a5f00d5004_10671.ko
15480 ? Rl 3:07 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-pie-debug-uprobeslibgcc-O3default-prelink-sep-debug-after_exe
-u /tmp/stap1Hv065/stap_bda7ff911f65c3a752b4db9772267f9b_10625.ko
15931 ? Rl 2:41 /usr/local/libexec/systemtap/stapio -w -c
./uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug-after_exe
-u /tmp/stap53sDwo/stap_1753fc2af1aad9dd913c37c6957f6bf0_10685.ko
These stapio processes cannot be killed (even a 'kill -9' fails). The modules
left behind are all "in use", so they cannot be removed. The stapio processes
stay in the running state.
Even if this testcase (and related user-space probing) fail, stap should exit
cleanly and not leave behind these stuck stapio process and modules.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-06 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 20:08 dsmith at redhat dot com [this message]
2011-04-18 19:21 ` [Bug runtime/12645] " dsmith at redhat dot com
2011-04-18 21:22 ` dsmith at redhat dot com
2011-04-18 22:12 ` dsmith at redhat dot com
2011-04-18 22:32 ` dsmith at redhat dot com
2011-04-18 23:49 ` jistone at redhat dot com
2011-04-20 19:12 ` dsmith 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=bug-12645-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).