Re: [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing

[Vitaly Mayatskikh <v.mayatskih@gmail.com>]

At Wed, 2 Jun 2010 11:16:11 -0400, Vivek Goyal wrote:
 
> I am not sure what is the problem we are trying to solve here. If we are
> unable to capture the dump because second kernel did not boot due to
> some dirver issue etc, above patch is not going to help either.
> 
> If kernel has booted, then one should be able to capture the dump, filter
> it and look at the log buffers and cpu registers.
> 
> Most of the failures I have seen in capture kernel is that it was unable
> to boot due to either deivce issues or failure in early boot. Once it has
> crossed those hurdles, after that capturing the dump is easy part.
> 
> How many times does it happen in second kernel that kernel is spinning in
> a loop and NMI can still get you information out.
> 
> So can you please give some more information about what kind of failures
> while capturing the dump you are addressing by this patchset.

Obviously, this change doesn't help if 2nd kernel is not able to
boot. But there are other problems, which may prevent vmcore to be
captured. For example, machine has RAM > HDD and it may save vmcore
only over network. If network fails (e.g., due to bugs in NIC drivers
or NFS, what is not so rare), and dump capture environment is
non-interactive, or it doesn't have development tools like `crash',
there's no chance even to guess what has happened.

Other possibilities of failure may include broken RAID controller,
HDD, RAM. NMI button in such situations is a last chance to see old
log.

-- 
wbr, Vitaly