Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] loglevel: <<UNKNOWN>>
Date: Wed, 20 Nov 2013 21:04:43 +0000	[thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267A2E4E@VAL-E-01.valcartier.drdc-rddc.gc.ca> (raw)

   Something strange is going on in one of my virtual machines.  I was fooling around with defining events, creating and deleting sessions, etc., and now the list of kernel tracepoints (lttng list -k) contains several entries where the loglevel reads a corrupt value.  Specifically:

      skb_consume (loglevel: <<UNKNOWN>> (577)) (type:tracepoint)
      skb_copy_datagram_iovec (loglevel: <<UNKNOWN>> (1140980544)) (type:tracepoint)
      sched_switch (loglevel: <<UNKNOWN>> (6647407)) (type:tracepoint)
      sched_migrate_task (loglevel: <<UNKNOWN>> (1140883008)) (type:tracepoint)
      sched_process_free (loglevel: <<UNKNOWN>> (51088)) (type:tracepoint)
      regulator_enable (loglevel: <<UNKNOWN>> (1140998064)) (type:tracepoint)
      regulator_enable_delay (loglevel: <<UNKNOWN>> (1140998080)) (type:tracepoint)
      power_machine_suspend (loglevel: <<UNKNOWN>> (52)) (type:tracepoint)

   None of these events were the subject of kprobe or kretprobe events, except maybe sched_switch.

   This weirdness went away after a restart of lttng-sessiond.  I've saved the VM with this corrupt system in case anyone wants to investigate.

Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC? G3J 1X5
CANADA
Vox?: (418) 844-4000 x4245
Fax?: (418) 844-4538
NAC?: 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada?| Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>



                 reply	other threads:[~2013-11-20 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48CF5AC71E61DB46B70D0F388054EFFD267A2E4E@VAL-E-01.valcartier.drdc-rddc.gc.ca \
    --to=daniel.thibault@drdc-rddc.gc.ca \
    /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