> There's also an "either/or" choice between using efi-capsule with pstore, and the > traditional kexec/kdump method for getting a memory dump from a crash. We > have to go through a reset to save the capsule - but we don't want a reset for > kexec. Perhaps we can pass the reset parameters through the kexec path to > the new kernel to make it do the right kind of reset ... but the value of the capsule > dump is minimal if kdump managed to dump everything. Tony, I tried to log kmsg into the kexec path months ago. It was rejected due to the impelementation problem. But, as Eric said, it should be OK if it is implemented in the kdump kenel. http://marc.info/?l=linux-kernel&m=136917686732183&w=2 The only problem with kdump here is the implementation in the initial ram disk. Fixing the initial ramdisk so it logs to kmsg before it touches scarier hardware should be the solution. Seiji -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
