From: Awais Belal via lttng-dev <lttng-dev@lists.lttng.org>
To: <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] lttng-modules: block: invalid/unknown value for rwbs field
Date: Tue, 9 Mar 2021 18:10:07 +0500 [thread overview]
Message-ID: <f02c9dd6-b95c-19be-a7b0-cca3efda149c@mentor.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2393 bytes --]
Hi,
I am using lttng-modules 2.12.5 with a 5.4.93 kernel on an aarch64
target. After creating a session I run
*lttng enable-event -k block**
to enable all the block_ kernel events but when I run babeltrace on the
generated traces I get a handful of
*[warning] Unknown value 33 in enum.
...
...
*
with different values in place of 33. This does not happen with any
other kernel event type
*BabelTrace Trace Viewer and Converter 1.5.8*
Also if I try to do a 'lttng view' on this session I can identify that
this has something to do with the rwbs field as I get
*[14:03:42.649719750] (+0.000005750) imx8qxpmek block_bio_remap: {
cpu_id = 3 }, { dev = 187695200, sector = 2460080, nr_sector = 8, rwbs =
( <unknown> : container = 33 ), old_dev = 187695203, old_sector = 2105776 }
[14:03:42.649722125] (+0.000002375) imx8qxpmek block_bio_queue: { cpu_id
= 3 }, { dev = 187695200, sector = 2460080, nr_sector = 8, rwbs = (
<unknown> : container = 33 ), tid = 428, comm = "jbd2/mmcblk1p3-" }
[14:03:42.649725000] (+0.000002875) imx8qxpmek block_bio_backmerge: {
cpu_id = 3 }, { dev = 187695200, sector = 2460080, nr_sector = 8, rwbs =
( <unknown> : container = 33 ), tid = 428, comm = "jbd2/mmcblk1p3-" }
...
...*
I believe <unknown> in the log points to a symptom? While for the
events/container id that do not generate this warning I have in the same
trace
*[14:03:44.697572375] (+2.036943500) imx8qxpmek block_bio_remap: {
cpu_id = 0 }, { dev = 187695200, sector = 9382032, nr_sector = 8, rwbs =
( "RWBS_FLAG_WRITE" : container = 1 ), old_dev = 187695206, old_sector =
278672 }
[14:03:44.697584375] (+0.000012000) imx8qxpmek block_bio_queue: { cpu_id
= 0 }, { dev = 187695200, sector = 9382032, nr_sector = 8, rwbs = (
"RWBS_FLAG_WRITE" : container = 1 ), tid = 1609, comm = "kworker/u8:0" }
[14:03:44.697604250] (+0.000019875) imx8qxpmek block_getrq: { cpu_id = 0
}, { dev = 187695200, sector = 9382032, nr_sector = 8, rwbs = (
"RWBS_FLAG_WRITE" : container = 1 ), tid = 1609, comm = "kworker/u8:0" }*
The interesting thing to note with the working events is that all of
them have "RWBS_FLAG_WRITE" and no other types from
https://github.com/lttng/lttng-modules/blob/stable-2.12/instrumentation/events/lttng-module/block.h#L39
which I would expect to see.
I am lost for hints as to what I need to look up... any help would be
highly appreciated.
--
BR,
Awais
[-- Attachment #1.2: Type: text/html, Size: 3932 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
next reply other threads:[~2021-03-09 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 13:10 Awais Belal via lttng-dev [this message]
2021-03-09 14:34 ` [lttng-dev] lttng-modules: block: invalid/unknown value for rwbs field Francis Deslauriers via lttng-dev
2021-03-09 14:49 ` Jérémie Galarneau via lttng-dev
2021-03-09 15:11 ` Awais Belal 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=f02c9dd6-b95c-19be-a7b0-cca3efda149c@mentor.com \
--to=lttng-dev@lists.lttng.org \
--cc=awais_belal@mentor.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 NNTP newsgroup(s).