From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31500] stapio exited with irqs disabled
Date: Wed, 20 Mar 2024 14:19:24 +0000 [thread overview]
Message-ID: <bug-31500-6586-eD6aV0HiIr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31500-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31500
--- Comment #5 from William Cohen <wcohen at redhat dot com> ---
On the machine that observed the problem poll_map.exp is using -g to compile
poll_map.stp. poll_map.stp uses 'kernel.function("vfs_*").call' insert kprobes.
With -g mode one of the probe points it attempts to instrument is
'kernel.function("vfs_caches_init").call'. This is an initialization function
on a page that is freed up after initialization. This problem appears to occur
on one particular machine. I suspect that it might happening on other machines
for other for tests/functions. It might be helpful to look to see if anything
in /proc/kallsyms match up with the lower 24-bits of ffffffffa64a65c0 (4a65c0)
on the machine that the problem initially occurred on:
sudo cat /proc/kallsyms |grep 4a65c0
Then take a look to see if any of those functions have and __init in front of
the of them using the function lookup on
https://elixir.bootlin.com/linux/v6.8.1/source.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-03-20 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 13:03 [Bug runtime/31500] New: " mcermak at redhat dot com
2024-03-18 21:48 ` [Bug runtime/31500] " wcohen at redhat dot com
2024-03-19 8:10 ` mcermak at redhat dot com
2024-03-19 15:49 ` wcohen at redhat dot com
2024-03-19 20:57 ` wcohen at redhat dot com
2024-03-20 14:19 ` wcohen at redhat dot com [this message]
2024-03-20 15:25 ` wcohen at redhat dot com
2024-03-20 21:10 ` wcohen at redhat dot com
2024-03-21 14:31 ` wcohen at redhat dot com
2024-03-21 15:13 ` wcohen at redhat dot com
2024-03-22 14:40 ` 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-31500-6586-eD6aV0HiIr@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).