Hello John,
I’ve done some additional digging on my end. I tested using a 5.10.11
kernel and observed the following:
1) With the default of CONFIG_LOG_BUF_SHIFT=17, I was not able to reproduce
the issue.
2) With CONFIG_LOG_BUF_SHIFT=20, I was able to reproduce the behavior
mentioned before.
Hello,
This dmesg uses /dev/kmsg; we've verified that we don't see this long
dmesg time when reading from syslog (via dmesg -S).
We've also tried testing this with logging daemons disabled as well as
within initrd - both result in similar behavior.
If it's relevant, this was done on a toybox she
On 2021-01-22, "J. Avila" wrote:
> When doing some internal testing on a 5.10.4 kernel, we found that the
> time taken for dmesg seemed to increase from the order of milliseconds
> to the order of seconds when the dmesg size approached the ~1.2MB
> limit. After doing some digging, we found that by
Hello,
When doing some internal testing on a 5.10.4 kernel, we found that the
time taken for dmesg seemed to increase from the order of milliseconds to
the order of seconds when the dmesg size approached the ~1.2MB limit. After
doing some digging, we found that by reverting all of the patches in p
4 matches
Mail list logo
