FS#36041 - [systemd] 204-1 journalctl boot reporting inconsistent

Attached to Project: Arch Linux
Opened by Glenn (grepfor) - Saturday, 06 July 2013, 01:24 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 23 July 2013, 19:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Boot-time info reported by journalctl (from systemd 204-1) is often inconsistent between what should be essentially identical boot cycles. The inconsistencies take the form of randomly missing messages from the journalctl output. These lacunas can make it very challenging to understand exactly what is going during the boot sequence.

This problem is documented in detail in the following posting on the Arch forum:

https://bbs.archlinux.org/viewtopic.php?id=163633

The posting contains information on how to reproduce the problem.

If you prefer, I can transcribe that posting here. Just let me know and I'll be happy to do so.

As an aside, I suspect -- but have no hard evidence -- that this issue may be related to the oft-reported journalctl corruption issue, e.g. as reported here:

https://bbs.archlinux.org/viewtopic.php?pid=1239783
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 23 July 2013, 19:53 GMT
Reason for closing:  Upstream
Additional comments about closing:  Follow upstream report: https://bugs.freedesktop.org/show_bug.cg i?id=66664
Comment by Dave Reisner (falconindy) - Sunday, 07 July 2013, 01:51 GMT
Please report this upstream -- there's no packaging issue to be had here.
Comment by Glenn (grepfor) - Sunday, 07 July 2013, 12:35 GMT
Done. https://bugs.freedesktop.org/show_bug.cgi?id=66664

Loading...