lttng-dev Archive mirror
 help / color / mirror / Atom feed
From: Pennese Marco via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] LTTng on RHEL 7.9 with real time kernel patch
Date: Fri, 15 Jul 2022 13:19:04 +0000	[thread overview]
Message-ID: <e1e5a7797fa044e6a9010c494a451be7@leonardo.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2505 bytes --]

Hi,

I’m trying to use LTTng on a Red Hat Enterprise Linux 7.9 (with the real time kernel patch).
I installed LTTng on the machine following the EfficiOS guide linked by lttng official website.

In my configuration, lttng manages to record user space events.
I’d like to record also kernel space events, so I’m following the quickstart guide on the website.

As soon as I run “lttng list –-kernel”, I obtain the error:



Error: Unable to list kernel events: Kernel tracer not available

Error: Command error

If I repeat the procedure on a machine without the real time kernel patch, it works as it should.
The real time kernel I’m using is the following
3.10.0-1160.62.1.rt56.1203.el7.x86_64

Do you think the error is due to the real time patch? Can LTTng work with a real time kernel?
Do I need to follow a different procedure for installing LTTng on a RHEL 7.9 real time machine?

Thank you,
Marco

Il presente messaggio e-mail e ogni suo allegato devono intendersi indirizzati esclusivamente al destinatario indicato e considerarsi dal contenuto strettamente riservato e confidenziale. Se non siete l'effettivo destinatario o avete ricevuto il messaggio e-mail per errore, siete pregati di avvertire immediatamente il mittente e di cancellare il suddetto messaggio e ogni suo allegato dal vostro sistema informatico. Qualsiasi utilizzo, diffusione, copia o archiviazione del presente messaggio da parte di chi non ne è il destinatario è strettamente proibito e può dar luogo a responsabilità di carattere civile e penale punibili ai sensi di legge.
Questa e-mail ha valore legale solo se firmata digitalmente ai sensi della normativa vigente.
________________________________
The contents of this email message and any attachments are intended solely for the addressee(s) and contain confidential and/or privileged information.
If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately notify the sender and then delete this message and any attachments from your system. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Unauthorized disclosure and/or use of information contained in this email message may result in civil and criminal liability. “
This e-mail has legal value according to the applicable laws only if it is digitally signed by the sender

[-- Attachment #1.2: Type: text/html, Size: 6878 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2022-07-15 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 13:19 Pennese Marco via lttng-dev [this message]
2022-07-18 15:58 ` [lttng-dev] LTTng on RHEL 7.9 with real time kernel patch Mathieu Desnoyers 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=e1e5a7797fa044e6a9010c494a451be7@leonardo.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=marco.pennese@leonardo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).