From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "François Belias" <beliasossim@gmail.com>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] loading modules with modprobe
Date: Tue, 16 Jul 2024 09:05:13 -0400 [thread overview]
Message-ID: <6deffa1d-4d46-4445-a510-a3aac271cc80@efficios.com> (raw)
In-Reply-To: <CAHD10UjoaOjqZUH4j55Ra7zJ2HVRLOyk7xnjv+BjnJxs6rN6Aw@mail.gmail.com>
Hi François,
On 7/15/24 6:10 PM, François Belias via lttng-dev wrote:
> Hello,
>
> I'm currently running Linux kernel version 6.5.0-41-generic and
> attempting to install LTTng from source. Here are the steps I followed:
>
> - I cloned the LTTng git repository to my computer from
> [https://github.com/lttng/lttng-modules.git](https://github.com/lttng/lttng-modules.git) <https://github.com/lttng/lttng-modules.git](https://github.com/lttng/lttng-modules.git)>.
> - Downloaded the kernel source tree corresponding to my kernel version
> to enable compilation.
> - Executed `make KERNELDIR=/path/to/my/linux/source`, which was
> completed successfully.
> - Ran `make KERNELDIR=/path/to/my/linux/source modules_install`, also
> without any issues.
> - Finally, I executed `sudo depmod -a`, which was completed successfully.
>
> However, when I attempt to load a module with commands like `sudo
> modprobe lttng-ketprobes` or "sudo modprobe lttng-tracer", I encounter
> the following errors:
>
> - For `lttng-ketprobes`: `modprobe: FATAL: Module lttng-ketprobes not
> found in directory /lib/modules/6.5.0-41-generic`.
> - For `lttng-tracer`: `modprobe: ERROR: could not insert 'lttng_tracer':
> Exec format error`.
If you rebuilt modules on the master branch as of yesterday you may need
to clean the LTTng modules install directory, rebuild, and reinstall.
This is due to kprobes, kretprobes, and uprobes modules being included
in the tracer core module. C.f.
https://github.com/lttng/lttng-modules/commit/0c2c6606eb66cb5222ab7a2a4f8329fd5dfdef70
You may want to stick with running lttng-modules 2.13.x which will not
have breaking changes merged in.
The exec format error also could be due to modules that are installed
but built against a different version of the Linux kernel.
A few things to check
- If your kernel has been upgraded recently, ensure the new kernel is
the one actually running
- If the modules haven't been rebuilt since the upgrade, they should be
rebuilt and reinstalled
- As I recall, you are playing around with some addon modules - do any
of those modules define dependencies on the kprobes, kretprobes, or
uprobes modules which now are no longer produced by builds of the master
branch
Is there further information in dmesg or journalctl regarding the module
loading?
hope this helps.
thanks,
kienan
>
> I've confirmed that the modules exist but can't load them. I'm unsure
> how to resolve these issues. Could someone please assist me?
>
> Thank you.
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-07-16 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 22:10 François Belias via lttng-dev
2024-07-16 13:05 ` Kienan Stewart via lttng-dev [this message]
2024-07-16 19:01 ` François Belias via lttng-dev
2024-07-16 19:41 ` Kienan Stewart via lttng-dev
2024-07-16 20:34 ` François Belias via lttng-dev
2024-07-17 14:55 ` Kienan Stewart via lttng-dev
[not found] ` <CAHD10UgTthGz7gcgcga6W4xxjiKHfuZgM9uCjEkViKsVUnDF8A@mail.gmail.com>
2024-07-17 15:47 ` François Belias via lttng-dev
2024-07-17 16:08 ` Kienan Stewart via lttng-dev
2024-07-18 0:44 ` François Belias via lttng-dev
2024-07-18 14:47 ` Kienan Stewart via lttng-dev
2024-07-18 14:58 ` Kienan Stewart via lttng-dev
2024-07-18 19:46 ` François Belias via lttng-dev
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=6deffa1d-4d46-4445-a510-a3aac271cc80@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=beliasossim@gmail.com \
--cc=kstewart@efficios.com \
/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