From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31472] systemtap.base/tracepoints.stp causes reboot with RHEL9 linux 5.14.0-428.el9.x86_64
Date: Tue, 12 Mar 2024 18:16:55 +0000 [thread overview]
Message-ID: <bug-31472-6586-fL8ohsRaNk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31472-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31472
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15400
--> https://sourceware.org/bugzilla/attachment.cgi?id=15400&action=edit
smaller reproducer using just mmap_lock:* tracepoints for the reboot
Took a look at the difference between the RHEL9 427 and 428 kernel tracepoints.
Suspected there was a set of tracepoints that were triggering the reboot in
the RHEL9 428 kernel. With a pared down tracepoints.stp check which wildcard
tracepoints were causing the problem. The following three tracepoints are
causing the reboot on RHEL9 428 kernel:
kernel.trace("mmap_lock:mmap_lock_acquire_returned")
kernel.trace("mmap_lock:mmap_lock_released")
kernel.trace("mmap_lock:mmap_lock_start_locking")
Check f39 and fedora rawhide and they both have those tracepoints. Attempted to
fedora 39 kernel-6.7.9-200.fc39.x86_64 and the reproducer ran with out issue.
The reproduce also ran without issue on rawhide with
kernel-6.8.0-0.rc7.20240308git3aaa8ce7a335.60.fc41.x86_64
Looks like the next step is to compare the difference between RHEL9 and
f39/rawhide.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-03-12 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 13:54 [Bug runtime/31472] New: " wcohen at redhat dot com
2024-03-11 13:57 ` [Bug runtime/31472] " fche at redhat dot com
2024-03-12 16:13 ` wcohen at redhat dot com
2024-03-12 18:16 ` wcohen at redhat dot com [this message]
2024-03-12 18:29 ` wcohen at redhat dot com
2024-03-14 18:51 ` wcohen at redhat dot com
2024-03-18 21:06 ` wcohen 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-31472-6586-fL8ohsRaNk@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).