From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/19241] New: systemtap fails to start when CPU0 is offline
Date: Fri, 13 Nov 2015 15:20:00 -0000 [thread overview]
Message-ID: <bug-19241-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19241
Bug ID: 19241
Summary: systemtap fails to start when CPU0 is offline
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
Created attachment 8780
--> https://sourceware.org/bugzilla/attachment.cgi?id=8780&action=edit
proposed patch
Per rhbz1280321, stap fails to start when CPU0 is offline:
========
# echo 1 > /sys/devices/system/cpu/cpu0/online
# cat /sys/devices/system/cpu/cpu*/online
1
1
1
1
# stap -e 'probe oneshot {log("hey!")}'
hey!
# echo 0 > /sys/devices/system/cpu/cpu0/online
# cat /sys/devices/system/cpu/cpu*/online
0
1
1
1
# stap -e 'probe oneshot {log("hey!")}'
stapio:init_relayfs:282: ERROR: couldn't open
/sys/kernel/debug/systemtap/stap_2e0ffa1415135b7d8d3684541d2a4c8_26577/trace0.
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run failed. [man error::pass5]
#
========
In bulk mode, staprun fails when any CPU except the last one are offline.
Attached patch fixes the issue for me.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-11-13 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 15:20 mcermak at redhat dot com [this message]
2015-11-13 15:25 ` [Bug runtime/19241] " mcermak at redhat dot com
2015-11-19 12:25 ` mcermak at redhat dot com
2015-11-19 12:25 ` mcermak at redhat dot com
2015-11-20 11:41 ` mcermak at redhat dot com
2015-11-27 21:56 ` fche 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-19241-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).