This has been reproduced with both systemd 213 and systemd 215. Steps to reproduce: boot with /usr/lib/systemd-bootchart as PID 1 under QEMU. Wait an extra 20 seconds after the boot completes. Expected result: a .svg file with the boot chart will appear in /run/log, and a notice will appear on stderr indicating that the boot chart has been written. Actual result: the notice appears on stderr, and the .svg file is created, but the svg file is blank (0 bytes.) This is not guaranteed to happen all the time, sometimes it works correctly. The operating system is Poky, as generated by the Yocto Project. (Yocto is something similar to buildroot, Poky is the name we use for the OS Yocto generates.) In this case, Yocto is generating Linux images for a 32-bit x86 target and then running them under QEMU. I believe KVM acceleration is not enabled. I mention this because it's not your typical Linux distro. I believe there are a few systemd developers within Intel's OTC who would be familiar with Yocto and Poky though. Auke Kok (the original author of systemd-bootchart) was kind enough to spend about an hour squinting at this bug today, and neither of us could figure it out. (BTW Auke, commenting out do_journal_append from bootchart.c did *not* fix it.)
Created attachment 114691 [details] [review] proposed patch
Comment on attachment 114691 [details] [review] proposed patch Could you please try the following patch? https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg29562.html
I just came across this bug report again. Unfortunately, I no longer have access to the workstation where I was reproducing this bug. That was two jobs ago.
boochart has been split out off the systemd package, and has its own bug tracker now. If this issue is still relevant, please create a new issue on the bootchart github page. Thanks. https://github.com/systemd/systemd-bootchart
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.