Messages in this thread | | | Date | Mon, 4 May 2020 12:12:12 -0700 | From | Kees Cook <> | Subject | Re: [PATCH v1 0/3] allow ramoops to collect all kmesg_dump events |
| |
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?
-- Kees Cook
| |