| Summary: | Enable Tracing boot and process times in testing images | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Aníbal Limón <anibal.limon> |
| Component: | core | Assignee: | Aníbal Limón <anibal.limon> |
| Status: | RESOLVED FIXED | QA Contact: | Francisco Pedraza <francisco.j.pedraza.gonzalez> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | leonardo.sandoval.gonzalez, meta.mr.watcher, meta.watcher, richard.purdie, ross.burton |
| Version: | 2.1 | ||
| Target Milestone: | 2.2 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | |||
| Bug Blocks: | 8142 | ||
|
Description
Aníbal Limón
2016-03-17 23:20:49 UTC
Anibal, The following script may be useful for this task: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/pybootchartgui Patch for enable printk times on qemu machines sent to the ML, http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123664.html I'll continue to review systemd and sysvinit. After review the systemd and sysvinit options, i decide only to enable printk times as default on qemu machines and enable systemd log debug option on testimage it dumps to the qemuboot log. The systemd log debug option provides all the information related to systemd boot process for debug. Also when i was working on enable debug in systemd, i noticed if you use journal output for logs (disk I/O) it reaches the timeout see, [1] Patches in review at, http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123803.html http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123804.html http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123805.html [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8142#c19 I forget to mention that we already have a systemd test for boot times [1], Benjamin wrote it using journalctl. [1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime/systemd.py#n132 OE-Core dfa8be08aa6e7ad6dbc615df8875dc2ac1ac8946 added the debug/printk kernel feature, but enabling logging to console breaks the sanity tests as the journal isn't used anymore. (In reply to comment #5) > OE-Core dfa8be08aa6e7ad6dbc615df8875dc2ac1ac8946 added the debug/printk > kernel feature, but enabling logging to console breaks the sanity tests as > the journal isn't used anymore. The main reason for this is because busybox-syslog isn't reciving journalctl forwarded syslog messages, the people from busybox remove the support of systemd [1]. I propose to get disabled of busybox-syslog on systemd images and use syslog-ng or make journalctl to write /var/log/messages? What you think ross? alimon [1] https://git.busybox.net/busybox/commit/?id=accd9eeb719916da974584b33b1aeced5f3bb346 (In reply to comment #6) > (In reply to comment #5) > > OE-Core dfa8be08aa6e7ad6dbc615df8875dc2ac1ac8946 added the debug/printk > > kernel feature, but enabling logging to console breaks the sanity tests as > > the journal isn't used anymore. > > The main reason for this is because busybox-syslog isn't reciving journalctl > forwarded syslog messages, the people from busybox remove the support of > systemd [1]. > > I propose to get disabled of busybox-syslog on systemd images and use > syslog-ng or make journalctl to write /var/log/messages? Another easy option is to drop read /var/log/messages and use journalctl directly to found the message. > > What you think ross? > > alimon > > [1] > https://git.busybox.net/busybox/commit/ > ?id=accd9eeb719916da974584b33b1aeced5f3bb346 Another set of patches for fix the issue with systemd and busybox syslog, http://lists.openembedded.org/pipermail/openembedded-core/2016-July/124421.html Remove dependency of #4528 because that bug is for get statistics about boot time [1]. [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=4528#c8 |