On Mon, May 04, 2020 at 03:17:40PM -0400, Pavel Tatashin wrote: > On Mon, May 4, 2020 at 3:12 PM Kees Cook <keescook@xxxxxxxxxxxx> wrote: > > > > On Mon, May 04, 2020 at 02:47:45PM -0400, Pavel Tatashin wrote: > > > > > # reboot -f > > > > > > > > > > After VM is back: > > > > > > > > > > # mount -t pstore pstore /mnt > > > > > # head /mnt/dmesg-ramoops-0 > > > > > Restart#1 Part1 > > > > > > > > Is there a reason that using ramoops.console_size isn't sufficient for > > > > this? > > > > > > Unfortunately, the console option is not working for us (Microsoft), > > > we have an embedded device with a serial console, and the baud rate > > > reduces the reboot performance, so we must keep the console quiet. We > > > also want to be able collect full shutdown logs from the field that > > > are collected during kexec based updates. > > > > I meant collecting console via pstore (i.e. /mnt/console-ramoops-0). Are > > you saying that's still too large for your situation? > > pstore /mnt/console-ramoops-0 outputs only messages below the console > loglevel, and our console loglevel is set to 3 due to slowness of > serial console. Which means only errors and worse types of messages > are recorded. AFAIK, there is no way to have different log levels for > different consoles. Ah-ha! Okay, thanks. Please include this rationale in the v2 changelog. That makes perfect sense; I just didn't see it and maybe others will need the same clarity too. Thanks! -Kees -- Kees Cook
