> 4. kernel panics again before a user checks the 1st panic messages in NVRAM. > > > To avoid missing 1st panic messages, this patch adds a new parameter ,efi_pstore_overwrite, > to efi_pstore so that we can specify whether efi_pstore overwrites existing entries in NVRAM or not. Since the EFI backend has so little storage space ... perhaps it should have some overwrite rules built into it? E.g. in the case where there is an OOPS already logged, and a panic happens, then I think the right thing to do is overwrite the oops with the panic. [The oops *might* have already made it to /var/log/messages, but even if it didn't, a user with a PICK ONLY ONE choice would have to go for the log of the panic] In the situation you describe where we already have a panic, then I don't think than anyone would want the earlier panic to be overwritten by the new one. If this seems a plausible route ... we'd need to tabulate the overwrite rules. I think they are: shutdown/reboot/kexec - can be overwritten by OOPS OOPS can be overwritten by panic panic can never be overwritten I'd like to avoid a kernel parameter ... chances are too high that the machine would be automatically rebooted without the right boot argument. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
