Messages in this thread | | | Date | Fri, 4 Feb 2011 10:24:27 +0800 | From | Américo Wang <> | Subject | Re: Query about kdump_msg hook into crash_kexec() |
| |
On Thu, Feb 03, 2011 at 05:08:01PM -0500, Seiji Aguchi wrote: >Hi Eric, > >Thank you for your prompt reply. > >I would like to consider "Needs in enterprise area" and "Implementation of kmsg_dump()" separately. > >(1) Needs in enterprise area > In case of kdump failure, we would like to store kernel buffer to NVRAM/flush memory > for detecting root cause of kernel crash. > >(2) Implementation of kmsg_dump > You suggest to review/test cording of kmsg_dump() more. > >What do you think about (1)? >Is it acceptable for you? >
For "in case of kdump fails", we can move KMSG_DUMP_OOPS/KMSG_DUMP_PANIC before calling crash_kexec(), so you can capture the log before kdump happens.
| |