On larger systems, information in the kernel log is lost because
there is so much early text printed, that it overflows the static
log buffer before the log_buf_len kernel parameter can be processed,
and a bigger log buffer allocated.
Distros are relunctant to increase memory usage by increasing the
size of the static log buffer, so minimize the problem by allocating
the new log buffer as early as possible.
--
* Mike Travis <[email protected]> wrote:
>
> On larger systems, information in the kernel log is lost because
> there is so much early text printed, that it overflows the static
> log buffer before the log_buf_len kernel parameter can be processed,
> and a bigger log buffer allocated.
>
> Distros are relunctant to increase memory usage by increasing the
> size of the static log buffer, so minimize the problem by allocating
> the new log buffer as early as possible.
I think this looks sane in principle and will solve quite a few 'the log buffer
got too large' problems which previously resulted in somewhat complex looking
printk-reduction patches. Andrew, if you agree with the patches, wanna carry
them?
Thanks,
Ingo