lkml.org 
[lkml]   [2018]   [Dec]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC][PATCH] printk: increase devkmsg write() ratelimit
On Tue, Dec 18, 2018 at 06:18:42PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> RFC
>
> A painful subject:
>
> I just noticed that stock systemd (no systemd debugging enabled) on my
> x86 box write()-s during shutdown to devkmsg more than before, so old
> devkmsg ratelimits do not apply:
>
> $ sudo journalctl -n 40000 -f | grep "kernel: printk: systemd-shutdow"
> kernel: printk: systemd-shutdow: 35 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 31 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 35 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 36 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 36 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 36 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 36 output lines suppressed due to ratelimiting
> kernel: printk: systemd-shutdow: 35 output lines suppressed due to ratelimiting
>
> I know that there is a "kernel.printk_devkmsg" interface; do we
> expect every systemd-enabled distro to find that out and to tweak
> kernel.printk_devkmsg or shall we change the default devkmsg
> ratelimit instead?

How about we complain to systemd instead?

\
 
 \ /
  Last update: 2018-12-18 11:49    [W:0.126 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site