From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27465] ERROR: Couldn't insert module&Invalid module format
Date: Tue, 02 Mar 2021 20:14:33 +0000 [thread overview]
Message-ID: <bug-27465-6586-0SDqgcwmwa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27465-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27465
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-03-02
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
dmesg might give further information about why the kernel rejected loading the
systemtap module. Can you try it again, and report what the kernel says?
Also, increasing the pass-5 verbosity to a higher level may give us more tips.
# stap --vp 00004 ....
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-03-02 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 2:13 [Bug runtime/27465] New: " lyeeer at outlook dot com
2021-03-02 20:14 ` fche at redhat dot com [this message]
2022-02-04 18:21 ` [Bug runtime/27465] " v.mayatskih at gmail dot com
2022-02-04 18:23 ` fche at redhat dot com
2022-02-04 18:53 ` v.mayatskih at gmail dot com
2022-02-04 19:22 ` v.mayatskih at gmail dot com
2022-02-04 19:30 ` v.mayatskih at gmail dot com
2022-02-04 19:40 ` v.mayatskih at gmail dot com
2022-02-09 23:57 ` fche at redhat dot com
2024-02-21 13:07 ` 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-27465-6586-0SDqgcwmwa@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).