From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 3snOJjxxmWZt7yoAWB0awg (envelope-from ) for ; Thu, 18 Jul 2024 15:47:08 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=lists.lttng.org header.i=@lists.lttng.org header.a=rsa-sha256 header.s=default header.b=KQ1odLbH; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 88C061E0C3; Thu, 18 Jul 2024 15:47:08 -0400 (EDT) Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id D6E661E097 for ; Thu, 18 Jul 2024 15:47:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1721332025; bh=UxpCzIt0WqH6PZ+nyrBzebBCruUE2M3UaEe97nY/QlQ=; h=References:In-Reply-To:Date:To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=KQ1odLbHgZrkH6wy0xKgY9aOj4SjfX2ZL0cBikr0yYS/EnUXj16rTmt8GncUCpfRz TKe5qPp/TGOk43+o9GGZxz64oidKwEGeTMDAd43gesvh/YzsHZQjmBP0ofkQ9eI+oH bxcPiRTgpT9fggTd5ziJ8+Uvqp6TxX9KVmvg4M2anV47rJ8e/AweJjiKKilLbTmkyY FV46NnbjsYjMOi6xhV0R5y0DDsnuAdh7+PO5QorRR9EBqaUiAsVCO6F/0OREzxb/02 +7i73sL7rnjBVHW5nZepWIW5kTr2ZtxVv2X3yZuhRzKeyUAqEohVH9Psvl+pNOf/rR buBRYDXdBoG7g== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4WQ3Gx2T5Wz12kD; Thu, 18 Jul 2024 15:47:05 -0400 (EDT) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) by lists.lttng.org (Postfix) with ESMTPS id 4WQ3Gv5hcyz12w0 for ; Thu, 18 Jul 2024 15:47:03 -0400 (EDT) Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1fb3b7d0d56so8312745ad.1 for ; Thu, 18 Jul 2024 12:47:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721332022; x=1721936822; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ehE+VtJdF+F6epnkOx0A/KG3TT4z2/Eq7DkeBjZgnp0=; b=VKmWXywlkZO3ASp6hjaHH7tQFQMEkx2k/qJzPEVHWL4EHc/P/2Yo6CyWQx8nlhJbTB FPtc2VNNJvTzLYi6/RGy3ZZ9r0ppUXZ4xzCIQsR+m39xeMOSpVUcBQaWWZIFrPzJiBgf L3pcGs9FC6WF/WW/gxDKza1VOwThNfvu8j73Lco+KWCYqVORU13A4UDbbAOB0na3rIwo NIiR34VPO+Eaf43jVI0A4iCc2BvlnHcVtLk/B4f1s2rW4mZAVyA53E6T9l0j2jaSMc0n M4LQ1iRUF9g709UWdElpOosUjpcXk36i5IQg9H0j5ApfeJ32d+cIeoHkoZG2nXamjK6T PV/w== X-Gm-Message-State: AOJu0YwwSZrI6D/WK4tsZaC2y910HvF5K2+/hJ/oIL0Fu0yHF371PZWs 4TXgvca2SOFeT6nJcvwt8WE2PwBy0BYRbz0OIH4EK0gR8CCaGGBA084UjsJ87Cn4NqgBATbmuRW NLwdIdCYqg/PMTZWGc4QfVy/xbVU= X-Google-Smtp-Source: AGHT+IHEScc0Fk9hqGm+mXatclucQKkuotKB3lbp7L3DTN0B9kVjwOeaDIWht9+AfQSM7BdVIePhZ6Bv8FyGD7KDYPE= X-Received: by 2002:a17:902:d2d2:b0:1fb:8a3b:ee9a with SMTP id d9443c01a7336-1fc4e6894c9mr60020925ad.61.1721332021963; Thu, 18 Jul 2024 12:47:01 -0700 (PDT) MIME-Version: 1.0 References: <6deffa1d-4d46-4445-a510-a3aac271cc80@efficios.com> <211e6d9f-834d-4511-b315-7844a5c04824@efficios.com> <5b7fc307-a52a-4e54-84df-294600454686@efficios.com> <02547951-d7df-4006-853a-521b057e9b3f@efficios.com> <4cedc4f3-6f8b-48b7-84f5-c6627c7786ee@efficios.com> In-Reply-To: <4cedc4f3-6f8b-48b7-84f5-c6627c7786ee@efficios.com> Date: Thu, 18 Jul 2024 15:46:50 -0400 Message-ID: To: Kienan Stewart Cc: lttng-dev@lists.lttng.org Subject: Re: [lttng-dev] loading modules with modprobe X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: =?utf-8?q?Fran=C3=A7ois_Belias_via_lttng-dev?= Reply-To: =?UTF-8?Q?Fran=C3=A7ois_Belias?= Content-Type: multipart/mixed; boundary="===============9101353945920727453==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============9101353945920727453== Content-Type: multipart/alternative; boundary="000000000000b5bc0c061d8ad7a5" --000000000000b5bc0c061d8ad7a5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Kienan, my issue has been fixed. thanks for your help Le jeu. 18 juill. 2024, =C3=A0 10 h 58, Kienan Stewart a =C3=A9crit : > A couple of addendums inline below > > On 7/18/24 10:47 AM, Kienan Stewart via lttng-dev wrote: > > Hi Fran=C3=A7ois, > > > > The dmesg excerpts are spaced by a number of minutes each, are they fro= m > > different attempts to build and load the modules? > > > > On 7/17/24 8:44 PM, Fran=C3=A7ois Belias wrote: > >> Hello Kienan, > >> > >> Thanks to your advice, I managed to load some modules. However, I > >> encountered errors like these when running `dmesg | grep lttng`: > >> > >> ``` > >> [ 218.043672] module lttng_kretprobes: .gnu.linkonce.this_module > >> section size must match the kernel's built struct module size at run > time > > > > This sounds like the version of the module is built against the wrong > > kernel headers or source. > > Also, are you using lttng-modules master or did you swap back to > stable-2.13? > > If you're still on master and have the most recent changes > lttng_kretprobes isn't required anymore. You will also need lttng-tools > from master with the corresponding changes so that it doesn't try to > load lttng_kretprobes. > > > > >> [ 650.560883] lttng_kretprobes: module verification failed: signature > >> and/or required key missing - tainting kernel > > > > Is your system running with secure boot enabled? If so, you either need > > to disable secure boot or sign the built modules with a MOK key that is > > correctly enrolled. > > > > See the following documentation: > > > > - https://lttng.org/docs/v2.13/#doc-linux-kernel-sig > > - https://www.kernel.org/doc/html/latest/admin-guide/module-signing.htm= l > > - https://github.com/dell/dkms > > - > > > https://gitlab.com/linux-kernel/stable/-/blob/master/kernel/module/main.c= #L2064 > > > > Whatever you did for this test is pretty closed to working. The previou= s > > errors with the section size check happen earlier in the module load > > process. This check seems to be one of the last, c.f. > > https://elixir.bootlin.com/linux/v6.10/source/kernel/module/main.c#L290= 8 > > > >> [ 1468.329988] module lttng_ring_buffer_client_discard: > >> .gnu.linkonce.this_module section size must match the kernel's built > >> struct module size at run time > >> ``` > >> > >> I'm unsure of their meaning. After loading my module, how can I be > >> certain that my tracepoints are active? I read online that people use > >> `sudo lttng list -k` for this purpose, but when I tried it, I got the > >> error: "Error: Unable to list kernel events: Kernel tracer not > >> available". Is there another way? > > > > If you're still getting "kernel tracer not available" then either > > required kernel modules haven't been loaded or you started lttng-sessio= n > > with `--no-kernel` option. `lttng-sessiond -vvv`, dmesg, and/or > > journalctl should have information on which modules failed to load. > > > > I know you're doing `sudo lttng list -k`, but the basic checks still appl= y: > > - is the lttng-sessiond running as the root user > - (when running without sudo) does the tracing group exist, and is your > user a member of that group > > > kienan > > > >> > >> Thank you for your assistance. > >> > >> Le mer. 17 juill. 2024, =C3=A0 12 h 08, Kienan Stewart > >> > a =C3=A9crit : > >> > >> Hi Fran=C3=A7ois, > >> > >> On 7/17/24 11:47 AM, Fran=C3=A7ois Belias wrote: > >> > Hello, Kienan > >> > > >> > > >> > *Right. Which kernel are you actually running at this time? You > >> can check > >> > using: `uname -a`* > >> > Linux philippe 6.5.0-41-generic #41~22.04.2-Ubuntu SMP > >> PREEMPT_DYNAMIC > >> > Mon Jun 3 11:32:55 UTC 2 x86_64 x86_64 x86_64 GNU/Linux > >> > > >> > *Since you've got a few different images and headers installed, > >> it is > >> > possible to check that same info the linux-source package: > >> `dpkg -l | > >> > grep linux-source`.* > >> > ii linux-source 5.15.0.116.1= 16 > >> > all Linux kernel source > >> with > >> > Ubuntu patches > >> > ii linux-source-5.15.0 5.15.0-116.126 > >> > all Linux kernel source for > >> version > >> > 5.15.0 with Ubuntu patches > >> > ii linux-source-6.5.0 6.5.0-44.44~22.04.1 > >> > all Linux kernel source for > >> version > >> > >> Your currently running `6.5.0-41-generic #41~22.04.2-Ubuntu` > >> > >> You have source installed for `6.5.0-44.44~22.04.1`. From your > >> previous > >> e-mail, there is also a linux image installed: > >> > >> ``` > >> linux-image-6.5.0-44-generic 6.5.0-44.44~22.04.1 > >> ``` > >> > >> Assuming you are using grub, could you verify that one of the > options > >> for booting in `/boot/grub/grub.cfg` is linux 6.5.0-44.44. Look > >> for the > >> lines similar to the following inside a menu entry block: > >> > >> (Note my example is 5.15.0-116, but you will be lookng for > >> 6.5.0-44 or > >> 6.5.0-44.44) > >> > >> ``` > >> linux /boot/vmlinuz-5.15.0-116-generic root=3D.... > >> initrd /boot/initrd.img-5.15.0-116-generic > >> ``` > >> > >> If you have a grub entry for linux 6.5.0-44.44, could you reboot > >> to run > >> on the linux 6.5.0-44.44. > >> > >> After rebooting verify with `uname -a` that your kernel version is > >> 6.5.0-44.44. > >> > >> Make sure you have unpacked the linux sources: > >> > >> ``` > >> # Approximating the version numbers, since I don't have 6.5.0 > >> installed > >> cd /usr/src/linux-source-6.5.0 > >> bunzip2 linux-source-6.5.0.tar.bz2 > >> tar -xf linux-source-6.5.0.tar > >> ``` > >> > >> Then retry the build with > >> `KERNELDIR=3D/usr/src/linux-source-6.5.0/linux-source-6.5.0/` > >> > >> I haven't personally tried the full steps on an Ubuntu > >> installation so > >> you may still need to tweak a couple of things, but I think this > >> should > >> get you on the right path. > >> > >> Really the important thing is to make sure that the kernel source > >> code > >> matches the kernel you are running. > >> > >> > 6.5.0 with Ubuntu patches > >> > *Could you run either `apt-cache policy` or `apt policy` and > >> `apt-mark > >> > showhold` in order to know which sources you have configured.* > >> > For this part, /*apt-mark showhold*/ gave me nothing I don't kn= ow > >> what > >> > is means. > >> > >> `apt-mark showhold` will show any packages that are on hold - it i= s > a > >> way of marking packages that shouldn't be updated. > >> > >> As you have the linux-source for 6.5.0-44.44~22.04.1, I don't > >> think it > >> will be necessary to have the output of `apt-cache policy`. > >> > >> thanks, > >> kienan > >> > >> > > >> > I am looking at the links, but nothing seems to match my kernel > >> version. > >> > > >> > Thanks for your assistance. > >> > > >> > Le mer. 17 juill. 2024, =C3=A0 11 h 46, Fran=C3=A7ois Belias > >> > > >> >> a > >> =C3=A9crit : > >> > > >> > Hello, Kienan > >> > > >> > > >> > *Right. Which kernel are you actually running at this time? > >> You can > >> > check > >> > using: `uname -a`* > >> > Linux philippe 6.5.0-41-generic #41~22.04.2-Ubuntu SMP > >> > PREEMPT_DYNAMIC Mon Jun 3 11:32:55 UTC 2 x86_64 x86_64 > >> x86_64 GNU/Linux > >> > > >> > *Since you've got a few different images and headers > >> installed, it is > >> > possible to check that same info the linux-source package: > >> `dpkg -l | > >> > grep linux-source`.* > >> > ii linux-source 5.15.0.116.116 > >> > all Linux kernel > >> source > >> > with Ubuntu patches > >> > ii linux-source-5.15.0 5.15.0-116.12= 6 > >> > all Linux kernel > >> source for > >> > version 5.15.0 with Ubuntu patches > >> > ii linux-source-6.5.0 > >> 6.5.0-44.44~22.04.1 > >> > all Linux kernel source > >> for > >> > version 6.5.0 with Ubuntu patches > >> > *Could you run either `apt-cache policy` or `apt policy` an= d > >> `apt-mark > >> > showhold` in order to know which sources you have > configured.* > >> > For this part, /*apt-mark showhold*/ gave me nothing I > >> don't know > >> > what is means. > >> > > >> > I am looking at the links, but nothing seems to match my > >> kernel > >> > version. > >> > > >> > Thanks for your assistance. > >> > > >> > Le mer. 17 juill. 2024, =C3=A0 10 h 55, Kienan Stewart > >> > > >> >> a > >> =C3=A9crit : > >> > > >> > Hi Fran=C3=A7ois, > >> > > >> > On 7/16/24 4:34 PM, Fran=C3=A7ois Belias wrote: > >> > > Hello Kienan, > >> > > > >> > > When I proceed with the following steps: > >> > > > >> > > ``` > >> > > # Warning: this removes all untracked content from t= he > >> > lttng-modules > >> > > directory > >> > > cd /path/to/lttng-modules-source > >> > > git clean -dxf > >> > > > >> > > make > >> > > sudo make modules_install > >> > > sudo depmod -a > >> > > ``` > >> > > > >> > > I encounter a warning in > >> > > `/home/philippe/lttng-modules/src/probes/Kbuild:79` > >> stating > >> > "File > >> > > ./arch/x86/kvm/lapic.h not found. Probe 'kvm' > >> x86-specific is > >> > disabled. > >> > > Use full kernel source tree to enable it." Although > >> > everything compiles > >> > > fine and I'm able to load modules, when I execute > >> `sudo lttng > >> > list -k`, > >> > > I don't see the tracepoints `kvm_entry` and > >> `kvm_exit`, which > >> > I believe > >> > > should be available. Could this be due to not using = my > >> full > >> > kernel tree > >> > > during compilation? > >> > > >> > > >> > Exactly. Those probes depend on having the full kernel > >> source as > >> > they > >> > require private headers which aren't shipped as part of > >> the > >> > `linux-headers` package. > >> > > >> > > > >> > > Here are the answers to your questions: > >> > > > >> > > - *Where did `/usr/src/linux-source-6.5.0` come from= ?* > >> > > I initially attempted `sudo apt-get update && sud= o > >> apt-get > >> > install > >> > > linux-source`, but it gave me this answer > >> */linux-source is > >> > already the > >> > > newest version (5.15.0.116.116)/*`, which doesn't > >> match my > >> > current > >> > > kernel version. So, I downloaded it directly from > >> kernel.org > >> > > > >> > > > >> >> using this command: > >> > `wget > >> > > > >> > https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz` > > >> > >> > > >> >> > > >> > > > >> > > >> > >> > >> > > >> >> >>. > >> > > > >> > > >> > Right. Which kernel are you actually running at this > >> time? You > >> > can check > >> > using: `uname -a` > >> > > >> > In any case, Linux upstream 6.5 is not the same as > >> Ubuntus's 6.5. > >> > > >> > > - *Which Linux distribution and version are you > using?* > >> > > Running `lsb_release -a` gives me: > >> > > ``` > >> > > No LSB modules are available. > >> > > Distributor ID: Ubuntu > >> > > Description: Ubuntu 22.04.4 LTS > >> > > Release: 22.04 > >> > > Codename: jammy > >> > > ``` > >> > > > >> > > - *Assuming your distribution has kernel packages, > >> which do > >> > you have > >> > > installed, and do you have the corresponding kernel > >> headers > >> > package > >> > > installed?* > >> > > > >> > > Running `dpkg -l | grep linux-image` shows these > >> installed > >> > packages: > >> > > ``` > >> > > ii linux-image-5.15.0-116-generic > >> 5.15.0-116.126 > >> > > amd64 Signed kernel image generic > >> > > ii linux-image-6.5.0-28-generic > >> > 6.5.0-28.29~22.04.1 > >> > > amd64 Signed kernel image generic > >> > > ii linux-image-6.5.0-41-generic > >> > 6.5.0-41.41~22.04.2 > >> > > amd64 Signed kernel image generic > >> > > ii linux-image-6.5.0-44-generic > >> > 6.5.0-44.44~22.04.1 > >> > > amd64 Signed kernel image generic > >> > > ii linux-image-generic 5.15.0.116.116 > >> > > amd64 Generic Linux kernel image > >> > > ii linux-image-generic-hwe-22.04 > >> > 6.5.0.44.44~22.04.1 > >> > > amd64 Generic Linux kernel image > >> > > ``` > >> > > > >> > > And `dpkg -l | grep linux-headers` shows these > >> installed > >> > header packages: > >> > > ``` > >> > > ii linux-headers-5.15.0-116 > >> > 5.15.0-116.126 all > >> > > Header files related to Linux kernel version > >> 5.15.0 > >> > > ii linux-headers-5.15.0-116-generic > >> 5.15.0-116.126 > >> > > amd64 Linux kernel headers for version 5.15.0 on > >> 64 bit > >> > x86 SMP > >> > > ii linux-headers-6.5.0-28-generic > >> > 6.5.0-28.29~22.04.1 > >> > > amd64 Linux kernel headers for version 6.5.0 on > >> 64 bit > >> > x86 SMP > >> > > ii linux-headers-6.5.0-41-generic > >> > 6.5.0-41.41~22.04.2 > >> > > amd64 Linux kernel headers for version 6.5.0 on > >> 64 bit > >> > x86 SMP > >> > > ii linux-headers-6.5.0-44-generic > >> > 6.5.0-44.44~22.04.1 > >> > > amd64 Linux kernel headers for version 6.5.0 on > >> 64 bit > >> > x86 SMP > >> > > ii linux-headers-generic 5.15.0.116.116 > >> > > amd64 Generic Linux kernel headers > >> > > ii linux-headers-generic-hwe-22.04 > >> > 6.5.0.44.44~22.04.1 > >> > > amd64 Generic Linux kernel headers > >> > > ``` > >> > > > >> > > >> > Since you've got a few different images and headers > >> installed, > >> > it is > >> > possible to check that same info the linux-source > >> package: `dpkg > >> > -l | > >> > grep linux-source`. > >> > > >> > Maybe one thing tripping this process up is that you > >> don't have > >> > an apt > >> > source that provides linux-source that matches the > >> kernel you > >> > are using. > >> > Could you run either `apt-cache policy` or `apt policy` > >> and > >> > `apt-mark > >> > showhold` in order to know which sources you have > >> configured. > >> > > >> > There are also alternative sources for the full source > >> tree: > >> > > >> > - You could download the specific package from > >> > packages.ubuntu.com > >> >. See > >> > https://packages.ubuntu.com > >> > and > >> > use `apt install ./downloaded_package.deb` > >> > > >> > - You could clone the kernel source for Ubuntu and > >> checkout the > >> > appropriate tag. See > >> > > >> > >> > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/= refs/tags > < > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/= refs/tags> > < > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/= refs/tags > < > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/= refs/tags > >> > >> > > >> > thanks, > >> > kienan > >> > > >> > > _______________________________________________ > > lttng-dev mailing list > > lttng-dev@lists.lttng.org > > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev > --000000000000b5bc0c061d8ad7a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello=C2=A0Kienan,=C2=A0=C2=A0

=C2=A0my= issue has been fixed. thanks for your help

Le jeu. 18 juill. 2024, = =C3=A0 10 h 58, Kienan Stewart <kstewart@efficios.com> a =C3=A9crit=C2=A0:
A couple of addendums inline below

On 7/18/24 10:47 AM, Kienan Stewart via lttng-dev wrote:
> Hi Fran=C3=A7ois,
>
> The dmesg excerpts are spaced by a number of minutes each, are they fr= om
> different attempts to build and load the modules?
>
> On 7/17/24 8:44 PM, Fran=C3=A7ois Belias wrote:
>> Hello Kienan,
>>
>> Thanks to your advice, I managed to load some modules. However, I =
>> encountered errors like these when running `dmesg | grep lttng`: >>
>> ```
>> [ =C2=A0218.043672] module lttng_kretprobes: .gnu.linkonce.this_mo= dule
>> section size must match the kernel's built struct module size = at run time
>
> This sounds like the version of the module is built against the wrong =
> kernel headers or source.

Also, are you using lttng-modules master or did you swap back to
stable-2.13?

If you're still on master and have the most recent changes
lttng_kretprobes isn't required anymore. You will also need lttng-tools=
from master with the corresponding changes so that it doesn't try to load lttng_kretprobes.

>
>> [ =C2=A0650.560883] lttng_kretprobes: module verification failed: = signature
>> and/or required key missing - tainting kernel
>
> Is your system running with secure boot enabled? If so, you either nee= d
> to disable secure boot or sign the built modules with a MOK key that i= s
> correctly enrolled.
>
> See the following documentation:
>
> - https://lttng.org/docs/v2.13/#doc-linux-k= ernel-sig
> - https://www.kernel.org/= doc/html/latest/admin-guide/module-signing.html
> - https://github.com/dell/dkms
> -
> https://gitlab.c= om/linux-kernel/stable/-/blob/master/kernel/module/main.c#L2064
>
> Whatever you did for this test is pretty closed to working. The previo= us
> errors with the section size check happen earlier in the module load <= br> > process. This check seems to be one of the last, c.f.
> https://elixir.bootlin.= com/linux/v6.10/source/kernel/module/main.c#L2908
>
>> [ 1468.329988] module lttng_ring_buffer_client_discard:
>> .gnu.linkonce.this_module section size must match the kernel's= built
>> struct module size at run time
>> ```
>>
>> I'm unsure of their meaning. After loading my module, how can = I be
>> certain that my tracepoints are active? I read online that people = use
>> `sudo lttng list -k` for this purpose, but when I tried it, I got = the
>> error: "Error: Unable to list kernel events: Kernel tracer no= t
>> available". Is there another way?
>
> If you're still getting "kernel tracer not available" th= en either
> required kernel modules haven't been loaded or you started lttng-s= ession
> with `--no-kernel` option. `lttng-sessiond -vvv`, dmesg, and/or
> journalctl should have information on which modules failed to load. >

I know you're doing `sudo lttng list -k`, but the basic checks still ap= ply:

- is the lttng-sessiond running as the root user
- (when running without sudo) does the tracing group exist, and is your user a member of that group

> kienan
>
>>
>> Thank you for your assistance.
>>
>> Le mer. 17 juill. 2024, =C3=A0 12 h 08, Kienan Stewart
>> <kst= ewart@efficios.com <mailto:kstewart@efficios.com>> a =C3=A9crit=C2=A0:
>>
>> =C2=A0=C2=A0=C2=A0 Hi Fran=C3=A7ois,
>>
>> =C2=A0=C2=A0=C2=A0 On 7/17/24 11:47 AM, Fran=C3=A7ois Belias wrote= :
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Hello, Kienan
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 > *Right. Which kernel are you actuall= y running at this time? You
>> =C2=A0=C2=A0=C2=A0 can check
>> =C2=A0=C2=A0=C2=A0=C2=A0 > using: `uname -a`*
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Linux philippe 6.5.0-41-generic #41~= 22.04.2-Ubuntu SMP
>> =C2=A0=C2=A0=C2=A0 PREEMPT_DYNAMIC
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Mon Jun =C2=A03 11:32:55 UTC 2 x86_6= 4 x86_64 x86_64 GNU/Linux
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 > *Since you've got a few differen= t images and headers installed,
>> it is
>> =C2=A0=C2=A0=C2=A0=C2=A0 > possible to check that same info the= linux-source package:
>> `dpkg -l |
>> =C2=A0=C2=A0=C2=A0=C2=A0 > grep linux-source`.*
>> =C2=A0=C2=A0=C2=A0=C2=A0 > ii =C2=A0linux-source=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A05.15.0.116.116
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0all =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Linux kernel source
>> with
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Ubuntu patches
>> =C2=A0=C2=A0=C2=A0=C2=A0 > ii =C2=A0linux-source-5.15.0=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A05.15.0-116.126
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0all =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Linux kernel source for
>> version
>> =C2=A0=C2=A0=C2=A0=C2=A0 > 5.15.0 with Ubuntu patches
>> =C2=A0=C2=A0=C2=A0=C2=A0 > ii =C2=A0linux-source-6.5.0=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 6.5.0= -44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 all =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0Linux kernel source for
>> version
>>
>> =C2=A0=C2=A0=C2=A0 Your currently running `6.5.0-41-generic #41~22= .04.2-Ubuntu`
>>
>> =C2=A0=C2=A0=C2=A0 You have source installed for `6.5.0-44.44~22.0= 4.1`. From your
>> previous
>> =C2=A0=C2=A0=C2=A0 e-mail, there is also a linux image installed:<= br> >>
>> =C2=A0=C2=A0=C2=A0 ```
>> =C2=A0=C2=A0=C2=A0 linux-image-6.5.0-44-generic 6.5.0-44.44~22.04.= 1
>> =C2=A0=C2=A0=C2=A0 ```
>>
>> =C2=A0=C2=A0=C2=A0 Assuming you are using grub, could you verify t= hat one of the options
>> =C2=A0=C2=A0=C2=A0 for booting in `/boot/grub/grub.cfg` is linux 6= .5.0-44.44. Look
>> for the
>> =C2=A0=C2=A0=C2=A0 lines similar to the following inside a menu en= try block:
>>
>> =C2=A0=C2=A0=C2=A0 (Note my example is 5.15.0-116, but you will be= lookng for
>> 6.5.0-44 or
>> =C2=A0=C2=A0=C2=A0 6.5.0-44.44)
>>
>> =C2=A0=C2=A0=C2=A0 ```
>> =C2=A0=C2=A0=C2=A0 linux=C2=A0 =C2=A0/boot/vmlinuz-5.15.0-116-gene= ric root=3D....
>> =C2=A0=C2=A0=C2=A0 initrd=C2=A0 /boot/initrd.img-5.15.0-116-generi= c
>> =C2=A0=C2=A0=C2=A0 ```
>>
>> =C2=A0=C2=A0=C2=A0 If you have a grub entry for linux 6.5.0-44.44,= could you reboot
>> to run
>> =C2=A0=C2=A0=C2=A0 on the linux 6.5.0-44.44.
>>
>> =C2=A0=C2=A0=C2=A0 After rebooting verify with `uname -a` that you= r kernel version is
>> =C2=A0=C2=A0=C2=A0 6.5.0-44.44.
>>
>> =C2=A0=C2=A0=C2=A0 Make sure you have unpacked the linux sources:<= br> >>
>> =C2=A0=C2=A0=C2=A0 ```
>> =C2=A0=C2=A0=C2=A0 # Approximating the version numbers, since I do= n't have 6.5.0
>> installed
>> =C2=A0=C2=A0=C2=A0 cd /usr/src/linux-source-6.5.0
>> =C2=A0=C2=A0=C2=A0 bunzip2 linux-source-6.5.0.tar.bz2
>> =C2=A0=C2=A0=C2=A0 tar -xf linux-source-6.5.0.tar
>> =C2=A0=C2=A0=C2=A0 ```
>>
>> =C2=A0=C2=A0=C2=A0 Then retry the build with
>> =C2=A0=C2=A0=C2=A0 `KERNELDIR=3D/usr/src/linux-source-6.5.0/linux-= source-6.5.0/`
>>
>> =C2=A0=C2=A0=C2=A0 I haven't personally tried the full steps o= n an Ubuntu
>> installation so
>> =C2=A0=C2=A0=C2=A0 you may still need to tweak a couple of things,= but I think this
>> should
>> =C2=A0=C2=A0=C2=A0 get you on the right path.
>>
>> =C2=A0=C2=A0=C2=A0 Really the important thing is to make sure that= the kernel source
>> code
>> =C2=A0=C2=A0=C2=A0 matches the kernel you are running.
>>
>> =C2=A0=C2=A0=C2=A0=C2=A0 > 6.5.0 with Ubuntu patches
>> =C2=A0=C2=A0=C2=A0=C2=A0 > *Could you run either `apt-cache pol= icy` or `apt policy` and
>> =C2=A0=C2=A0=C2=A0 `apt-mark
>> =C2=A0=C2=A0=C2=A0=C2=A0 > showhold` in order to know which sou= rces you have configured.*
>> =C2=A0=C2=A0=C2=A0=C2=A0 > For this part, /*apt-mark showhold*/= =C2=A0gave me nothing I don't know
>> =C2=A0=C2=A0=C2=A0 what
>> =C2=A0=C2=A0=C2=A0=C2=A0 > is means.
>>
>> =C2=A0=C2=A0=C2=A0 `apt-mark showhold` will show any packages that= are on hold - it is a
>> =C2=A0=C2=A0=C2=A0 way of marking packages that shouldn't be u= pdated.
>>
>> =C2=A0=C2=A0=C2=A0 As you have the linux-source for 6.5.0-44.44~22= .04.1, I don't
>> think it
>> =C2=A0=C2=A0=C2=A0 will be necessary to have the output of `apt-ca= che policy`.
>>
>> =C2=A0=C2=A0=C2=A0 thanks,
>> =C2=A0=C2=A0=C2=A0 kienan
>>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 > I am looking at the links, but nothi= ng seems to match my kernel
>> =C2=A0=C2=A0=C2=A0 version.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Thanks for your assistance.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 > Le mer. 17 juill. 2024, =C3=A0 11 h = 46, Fran=C3=A7ois Belias
>> =C2=A0=C2=A0=C2=A0=C2=A0 > <beliasossim@gmail.com <mailto:beliasossim@gmail.com&g= t;
>> =C2=A0=C2=A0=C2=A0 <mailto:beliasossim@gmail.com <mailto:beliasossim@gmail.com>&g= t;> a
>> =C3=A9crit=C2=A0:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0Hello, Kienan
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0*Right. Which ker= nel are you actually running at this time?
>> =C2=A0=C2=A0=C2=A0 You can
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0check
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0using: `uname -a`= *
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0Linux philippe 6.= 5.0-41-generic #41~22.04.2-Ubuntu SMP
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0PREEMPT_DYNAMIC M= on Jun =C2=A03 11:32:55 UTC 2 x86_64 x86_64
>> =C2=A0=C2=A0=C2=A0 x86_64 GNU/Linux
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0*Since you've= got a few different images and headers
>> =C2=A0=C2=A0=C2=A0 installed, it is
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0possible to check= that same info the linux-source package:
>> =C2=A0=C2=A0=C2=A0 `dpkg -l |
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0grep linux-source= `.*
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0ii =C2=A0linux-so= urce =C2=A0=C2=A0=C2=A0=C2=A0 =C2=A05.15.0.116.116
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0all =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Linux = kernel
>> =C2=A0=C2=A0=C2=A0 source
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0with Ubuntu patch= es
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0ii =C2=A0linux-so= urce-5.15.0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A05.15.0-116.126
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0all =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Linux kernel
>> source for
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0version 5.15.0 wi= th Ubuntu patches
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0ii =C2=A0linux-so= urce-6.5.0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0
>> 6.5.0-44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 all =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Linux kernel source
>> for
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0version 6.5.0 wit= h Ubuntu patches
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0*Could you run ei= ther `apt-cache policy` or `apt policy` and
>> =C2=A0=C2=A0=C2=A0 `apt-mark
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0showhold` in orde= r to know which sources you have configured.*
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0For this part, /*= apt-mark showhold*/ gave me nothing I
>> don't know
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0what is means. >> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0I am looking at t= he links, but nothing seems to match my
>> kernel
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0version.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0Thanks for your a= ssistance.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0Le mer. 17 juill.= 2024, =C3=A0 10 h 55, Kienan Stewart
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0<kstewart@efficios.com <= ;mailto:kstewart= @efficios.com>
>> =C2=A0=C2=A0=C2=A0 <mailto:kstewart@efficios.com <mailto:kstewart@efficios.com>&g= t;> a
>> =C3=A9crit=C2=A0:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hi = Fran=C3=A7ois,
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On = 7/16/24 4:34 PM, Fran=C3=A7ois Belias wrote:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; Hello Kienan,
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; When I proceed with the following steps:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; # Warning: this removes all untracked content from the
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ltt= ng-modules
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; directory
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; cd /path/to/lttng-modules-source
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; git clean -dxf
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; make
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; sudo make modules_install
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; sudo depmod -a
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; I encounter a warning in
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; `/home/philippe/lttng-modules/src/probes/Kbuild:79`
>> =C2=A0=C2=A0=C2=A0 stating
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&qu= ot;File
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; ./arch/x86/kvm/lapic.h not found. Probe 'kvm'
>> =C2=A0=C2=A0=C2=A0 x86-specific is
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0dis= abled.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; Use full kernel source tree to enable it." Although
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eve= rything compiles
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; fine and I'm able to load modules, when I execute
>> =C2=A0=C2=A0=C2=A0 `sudo lttng
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0lis= t -k`,
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; I don't see the tracepoints `kvm_entry` and
>> =C2=A0=C2=A0=C2=A0 `kvm_exit`, which
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I b= elieve
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; should be available. Could this be due to not using my
>> =C2=A0=C2=A0=C2=A0 full
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ker= nel tree
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; during compilation?
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Exa= ctly. Those probes depend on having the full kernel
>> =C2=A0=C2=A0=C2=A0 source as
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the= y
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0req= uire private headers which aren't shipped as part of
>> the
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0`li= nux-headers` package.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; Here are the answers to your questions:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; - *Where did `/usr/src/linux-source-6.5.0` come from?*
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 I initially attempted `sudo apt-get update && sudo<= br> >> =C2=A0=C2=A0=C2=A0 apt-get
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ins= tall
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; linux-source`, but it gave me this answer
>> =C2=A0=C2=A0=C2=A0 */linux-source is
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alr= eady the
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; newest version (5.15.0.116.116)/*`, which doesn't
>> match my
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cur= rent
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; kernel version. So, I downloaded it directly from
>> =C2=A0=C2=A0=C2=A0 kernel.org <http://kernel.org>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<= ;http://= kernel.org <http://kernel.org>>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; <h= ttp://kernel.org <http://kernel.org>
>> =C2=A0=C2=A0=C2=A0 <http://kernel.org <http://kernel.org>>>= using this command:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0`wg= et
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 > = https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz`
>> =C2=A0=C2=A0=C2=A0 <https:/= /cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0
>> =C2=A0<https://cdn.kernel.o= rg/pub/linux/kernel/v6.x/linux-6.5.tar.xz
>> =C2=A0=C2=A0=C2=A0 <https:/= /cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz>>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0
>> =C2=A0<https://cdn.kernel.o= rg/pub/linux/kernel/v6.x/linux-6.5.tar.xz`
>> =C2=A0=C2=A0=C2=A0 <https:/= /cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0
>> =C2=A0<https://cdn.kernel.o= rg/pub/linux/kernel/v6.x/linux-6.5.tar.xz
>> =C2=A0=C2=A0=C2=A0 <https:/= /cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.5.tar.xz>>>.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Rig= ht. Which kernel are you actually running at this
>> =C2=A0=C2=A0=C2=A0 time? You
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0can= check
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0usi= ng: `uname -a`
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0In = any case, Linux upstream 6.5 is not the same as
>> =C2=A0=C2=A0=C2=A0 Ubuntus's 6.5.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; - *Which Linux distribution and version are you using?*
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Running `lsb_release -a` gives me:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 No LSB modules are available.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Distributor ID: Ubuntu
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Description: =C2=A0 =C2=A0Ubuntu 22.04.4 LTS
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Release: =C2=A0 =C2=A0 =C2=A0 =C2=A022.04
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Codename: =C2=A0 =C2=A0 =C2=A0 jammy
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; - *Assuming your distribution has kernel packages,
>> =C2=A0=C2=A0=C2=A0 which do
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0you= have
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; installed, and do you have the corresponding kernel
>> =C2=A0=C2=A0=C2=A0 headers
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pac= kage
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t; installed?*
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 Running `dpkg -l | grep linux-image` shows these
>> =C2=A0=C2=A0=C2=A0 installed
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pac= kages:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-5.15.0-116-generic=C2=A0 =C2=A0 =C2=A0=
>> 5.15.0-116.126
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Signed kernel image generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-6.5.0-28-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-28.29~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Signed kernel image generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-6.5.0-41-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-41.41~22.04.2
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Signed kernel image generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-6.5.0-44-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Signed kernel image generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-generic =C2=A0=C2=A0=C2=A0=C2=A0 =C2= =A05.15.0.116.116
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Generic Linux kernel image
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-image-generic-hwe-22.04
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A06.5.0.44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Generic Linux kernel image
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 And `dpkg -l | grep linux-headers` shows these
>> =C2=A0=C2=A0=C2=A0 installed
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0hea= der packages:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-5.15.0-116
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A05.1= 5.0-116.126 =C2=A0 =C2=A0 =C2=A0all
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 =C2=A0 Header files related to Linux kernel version
>> 5.15.0
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-5.15.0-116-generic=C2=A0 =C2=A0 =C2= =A0
>> 5.15.0-116.126
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Linux kernel headers for version 5.15.0 on
>> =C2=A0=C2=A0=C2=A0 64 bit
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0x86= SMP
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-6.5.0-28-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-28.29~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Linux kernel headers for version 6.5.0 on
>> 64 bit
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0x86= SMP
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-6.5.0-41-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-41.41~22.04.2
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Linux kernel headers for version 6.5.0 on
>> 64 bit
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0x86= SMP
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-6.5.0-44-generic
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06.5= .0-44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Linux kernel headers for version 6.5.0 on
>> 64 bit
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0x86= SMP
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-generic =C2=A0=C2=A0=C2=A0=C2=A0 =C2= =A05.15.0.116.116
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Generic Linux kernel headers
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ii =C2=A0linux-headers-generic-hwe-22.04
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A06.5.0.44.44~22.04.1
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0amd64 =C2=A0 Generic Linux kernel headers
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;=C2=A0 =C2=A0 ```
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &g= t;
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sin= ce you've got a few different images and headers
>> =C2=A0=C2=A0=C2=A0 installed,
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0it = is
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pos= sible to check that same info the linux-source
>> =C2=A0=C2=A0=C2=A0 package: `dpkg
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-l = |
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0gre= p linux-source`.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0May= be one thing tripping this process up is that you
>> =C2=A0=C2=A0=C2=A0 don't have
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0an = apt
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sou= rce that provides linux-source that matches the
>> kernel you
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0are= using.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Cou= ld you run either `apt-cache policy` or `apt policy`
>> and
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0`ap= t-mark
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sho= whold` in order to know which sources you have
>> configured.
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The= re are also alternative sources for the full source
>> tree:
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Y= ou could download the specific package from
>> =C2=A0=C2=A0=C2=A0=C2=A0 > packages.ubuntu.com <http:/= /packages.ubuntu.com>
>> =C2=A0=C2=A0=C2=A0 <http://packages.ubuntu.com <http:= //packages.ubuntu.com>>. See
>> =C2=A0=C2=A0=C2=A0=C2=A0 > https://packages.ubuntu.com &l= t;https://packages.ubuntu.com>
>> =C2=A0=C2=A0=C2=A0 <https://packages.ubuntu.com <htt= ps://packages.ubuntu.com>> and
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0use= `apt install ./downloaded_package.deb`
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Y= ou could clone the kernel source for Ubuntu and
>> =C2=A0=C2=A0=C2=A0 checkout the
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0app= ropriate tag. See
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>>=C2=A0 =C2=A0 =C2=A0
>> https://g= it.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/refs/tags <https://git= .launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/refs/tags= > <https://g= it.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/refs/tags <https://git= .launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/refs/tags= >>
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0tha= nks,
>> =C2=A0=C2=A0=C2=A0=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0kie= nan
>> =C2=A0=C2=A0=C2=A0=C2=A0 >
>>
> _______________________________________________
> lttng-dev mailing list
> lttng-d= ev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailm= an/listinfo/lttng-dev
--000000000000b5bc0c061d8ad7a5-- --===============9101353945920727453== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============9101353945920727453==--