testcases expect first kernel log line, but not always in logs
Bug #1830479 reported by
Dan Streetman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Debian) |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Won't Fix
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[impact]
boot-and-services and cmdline-
[test case]
run autopkgtest on arm64 with the current kernel, whose kernel log size is too small for journald or rsyslogd to capture the first kernel log messages.
[regression potential]
low; testcase fix only.
[other info]
the specific cause of this currently is too-small kernel log buffer size on arm64, which is being fixed in bug 1824864, but increasing amounts of boot time logging may cause a failure again, or custom kernel configs with small log buffers.
Changed in systemd (Debian): | |
status: | Unknown → New |
Changed in systemd (Debian): | |
status: | New → Fix Committed |
Changed in systemd (Debian): | |
status: | Fix Committed → Fix Released |
Changed in systemd (Ubuntu Cosmic): | |
status: | New → Won't Fix |
Changed in systemd (Ubuntu Bionic): | |
status: | New → Won't Fix |
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
It's a critical but in the Ubuntu platform if the very first kernel log line is not available in the system logs.
And it is present on all arches, apart from the identified buggy arm64 which is in-flight being fixed (in eoan-proposed & disco-proposed with other releases to follow).
cmdline- upstart- boot is only present in xenial? and arm64-kvm testing only started to be done post xenial release. Hence systemd/arm64 autopkgtest status is currently "Always Failed" and doesn't block anything.
This is not applicable to devel series, nor should be applied in prior releases, instead kernel should be fixed.