(forgot the list) >>> Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> schrieb am 01.06.2021 um 14:57 in Nachricht <60b64b0c.ed38.00a...@rz.uni-regensburg.de>: >>>> Lennart Poettering <lenn...@poettering.net> schrieb am 01.06.2021 um 14:43 in > Nachricht <YLYrch+r3wc+QqO5@gardel-login>: > > On Di, 01.06.21 14:33, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > > wrote: > > > >> >>> Lennart Poettering <lenn...@poettering.net> schrieb am 01.06.2021 um 13:39 > >> in > >> Nachricht <YLYcdMZ+MgmcPdmG@gardel-login>: > >> > On Di, 01.06.21 12:42, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) > >> wrote: > >> > > >> >> Jun 01 12:33:10 h18 systemd‑journald[3256]: Missed 195 kernel messages > >> >> > >> >> A few questions: > >> >> 1) What causes this? > >> > > >> > Dunno. Something is massively flooding the kernel log buffer. Probably > >> > some borked driver or so. "dmesg" might tell you what. > >> > >> I had meant the dropping of messages, not the creation of such. It seems
> > it's > >> intentional. > > > > Ahumm. It does not. Generating such high frequency log messages is a > > bug. Please report to your kernel maintainers. > > OK, maybe read again the beginning of my message: I had >500 processes in > "D" state when doing "echo w >/proc/sysrq-trigger". > > > > >> > You could also enlarge the kernel log buffer, see log_buf_mem= kernel > >> > cmdline switch. > >> > >> Confused: So is it the kernel dropping/loosing messages, or is it journald? > > > > The kernel is generating them faster than userspace can keep up with them. > > That's bad. > > > > > Lennart > > > > -- > > Lennart Poettering, Berlin > > > > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
