Hi On 2015-07-31, Stefan Lippers-Hollmann wrote: > On 2015-07-25, Bastian Blank wrote: > > output (udev.log-priority=8 at the kernel command line) from a failed > > boot. [...] > Loading, please wait... > invalid udev.log[ 2.343952] random: systemd-udevd urandom read with 4 bits > of entropy available > -priority ignored: 8 [...]
Well, obviously (or rather not quite that obviously), the maximum log
level is 7.
systemd-223/src/libudev/libudev-util.c:
int util_log_priority(const char *priority)
{
[...]
if (prio >= 0 && prio <= 7)
return prio;
else
return -ERANGE;
[...]
}
However it seems to be even harder to reproduce with udev.log-priority=7
set. While it triggers in roughly 85% of all reboots on this system
without serial console and special logging parameters, it takes quite a
few reboots to reproduce with serial console and udev.log-priority=7.
The attached bootlog (serial console && udev.log-priority=7) has
unfortunately not been recorded with an official Debian kernel, but
I've been able to reproduce it with 4.0.0-2-amd64 as well. Just that I
missed increasing the scrollback buffer in time and wasn't able to
fetch a full bootlog then - and, regardless of the kernel in use,
reproducing takes quite many reboots (too many for now) with full
logging enabled.
Regards
Stefan Lippers-Hollmann
boot.log.gz
Description: application/gzip
pgp8ub8TfHObx.pgp
Description: Digitale Signatur von OpenPGP
