From: Mark Jonas <toertel@gmail.com>
To: "adrian.fueloep@holtkamp.de" <adrian.fueloep@holtkamp.de>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] Bootchart2 is not generating a proper chart
Date: Mon, 10 Jul 2023 08:50:38 +0200 [thread overview]
Message-ID: <CAEE5dN2pHT6sEOqPygT7MuUhLhsbAmB4M-3fAgPj4mE+L7p5Sg@mail.gmail.com> (raw)
In-Reply-To: <rVI2.1688478331779822059.Kc7f@lists.yoctoproject.org>
Hi Adrian,
I think when using systemd you'ld better use systemd-bootchart.
At a quick glance this tutorial looks like a good starting point:
https://wiki.rdkcentral.com/display/RDK/Boot+Time+Measurement
Cheers,
Mark
On Tue, Jul 4, 2023 at 3:45 PM adrian.fueloep@holtkamp.de
<adrian.fueloep@holtkamp.de> wrote:
>
> Hello people,
>
> I'm heaving trouble to use bootchart2 in my yocto project.
> I've included bootchart2 from openembedded-core. Kernel Configs and cmd line args are set as described in this document.
> On bootup this message appears:
>
> systemd[1]: bootchart2.service: Failed with result 'protocol'.
> systemd[1]: Failed to start Collect Bootchart Data.
> [FAILED] Failed to start Collect Bootchart Data.
> See 'systemctl status bootchart2.service' for details.
>
> The resulting graph covers only 1,4 seconds.
>
> Does anyone know about this issue?
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13102): https://lists.yoctoproject.org/g/poky/message/13102
> Mute This Topic: https://lists.yoctoproject.org/mt/99946679/4454828
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [toertel@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2023-07-10 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 13:45 Bootchart2 is not generating a proper chart adrian.fueloep
2023-07-10 6:50 ` Mark Jonas [this message]
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=CAEE5dN2pHT6sEOqPygT7MuUhLhsbAmB4M-3fAgPj4mE+L7p5Sg@mail.gmail.com \
--to=toertel@gmail.com \
--cc=adrian.fueloep@holtkamp.de \
--cc=poky@lists.yoctoproject.org \
/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).