commit 1b710b1b10eff9d46666064ea25f079f70bc67a8 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1b710b1b10eff9d46666064ea25f079f70bc67a8) is breaking both syslog-ng and metalog from detecting real-time kernel log updates which results in no logs captured to /var/log/kernel.log. dmesg and /dev/kmsg do show log updates. If this commit is reversed, normal logging occurs. I have tested reversing this patch with kernel versions 5.5.6, 5.5.9, 5.4.24, and 5.4.25. I am running kernels compiled locally on a modified Arch Linux AMD x64 setup, using sysvinit and OpenRC. Thanks for providing the kernel and any help fixing this bug.
Created attachment 288369 [details] output from lscpu I have the exact same issue with "dmesg --follow" (haven't checked my /var/log/kern.log being affected). Reverting the mentioned commit also fixes this for me. I am having this issue on a machine with AMD Opteron CPUs running Gentoo Linux with sysvinit/openrc. I do _not_ have this issue on my Notebook with Intel Core i7 CPU running the same Gentoo Linux sysvinit/openrc combination. I had a talk in IRC with another user being affected by this and we happen to have the same AMD CPU family and Model on our affected systems. Attached is my CPU information.
Created attachment 288399 [details] output from lscpu Adding output from lscpu from my system. Since my initial report, I have additionally successfully tested reversing this patch with kernel versions up to 5.6.3.
Commit ab6f762f0f53162 5.7-rc1 (Linus' HEAD) should fix the problem. -ss
Thanks! I applied commit ab6f762f0f53162 to 5.6.4 and verified that this fixes the problem.