On Sat, Oct 25, 2014 at 12:51:25PM +0000, Mathieu Desnoyers wrote: > FYI, the main reason why my customer wants to go with a > "trace into memory that survives soft reboot" approach > rather than to use things like kexec/kdump is that they > care about the amount of time it takes to reboot their > machines. They want a solution where they can extract the > detailed crash data after reboot, after the machine is > back online, rather than requiring a few minutes of offline > time to extract the crash details. IIRC, on x86 there's no guarantee that your memory content will be preserved over reboot. BIOS is free to mess with it. -- Kirill A. Shutemov -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
