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 01:32:20 +0000 [thread overview]
Message-ID: <bug-31006-6586-ex1wI1DnMO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31006-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31006
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
Did some digging around and found that this has been fixed in the
kernel-4.18.0-520.el8.ppc64le kernel. With that kernel the test just fails
rather than causing the system to reboot:
unning /usr/share/systemtap/testsuite/systemtap.context/context.exp ...
FAIL: backtrace - could not build modules
FAIL: args - could not build modules
FAIL: pid - could not build modules
FAIL: num_args - could not build modules
FAIL: symfileline - could not build modules
=== systemtap Summary ===
# of unexpected failures 5
Looking through the red hat issue looks like there might also be some RHEL9
kernels version that get similar oops (RHELPLAN-142467) and appears to be fixed
in RHEL9.2.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-10-30 1:32 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 ` [Bug runtime/31006] " wcohen at redhat dot com
2023-10-30 1:32 ` wcohen at redhat dot com [this message]
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-ex1wI1DnMO@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).