From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31006] systemtap.contex/context.exp test causes reboot on RHEL8 ppc64le
Date: Mon, 30 Oct 2023 00:37:21 +0000 [thread overview]
Message-ID: <bug-31006-6586-lAiRqHnt2z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31006-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31006
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
Looking at the /sys/kernel/debug/tracing/trace I see why now it didn' trigger
the problem as the probe was put on yyy_int+0x4 rather than yyy_int+0x0 as
systemtap is doing:
echo 'p:myprobe systemtap_test_module2:yyy_int $comm' >
/sys/kernel/debug/tracing/kprobe_events
echo 1 > /sys/kernel/debug/tracing/events/kprobes/myprobe/enable
echo 1 > /proc/stap_test_cmd
echo 1 > /proc/stap_test_cmd
# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
bash-1976 [006] .... 1525.064248: myprobe: (yyy_int+0x4/0x20
[systemtap_test_module2]) arg1="bash"
bash-1976 [006] .... 1617.000845: myprobe: (yyy_int+0x4/0x20
[systemtap_test_module2]) arg1="bash"
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-10-30 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 0:13 [Bug runtime/31006] New: " wcohen at redhat dot com
2023-10-30 0:37 ` wcohen at redhat dot com [this message]
2023-10-30 1:32 ` [Bug runtime/31006] " wcohen at redhat dot com
2023-10-30 1:33 ` wcohen at redhat dot com
2023-10-30 7:37 ` 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-31006-6586-lAiRqHnt2z@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).