For a couple months now, I have noticed that running dmesg -w on my workstation does not appear to print out new kernel messages. In other words dmesg --follow “hangs”. Additionally when running tail -f /var/log/kern.log to monitor new dmesg messages picked up by sysklogd (part of syslogng), the latest messages do not come through until sysklogd periodically “reopens” the /dev/kmsg kernel message buffer. Why is this a problem? This is a problem because I use the dmesg log to monitor important hardware related messages such as the kernel recognizing a USB device or diagnosing bluetooth/wifi issues.
Most of my workstations & laptops require a passphrase typed in to open the encrypted root filesystem. So my steps to booting are as follows: Power on machine Wait for FDE passphrase prompt Type in FDE passphrase Wait for boot to complete and automatic XFCE session to start Since I need to know when the computer is ready to accept the passphrase, it is important the framebuffer is usable during the early part of the boot.