Messages in this thread | | | Date | Fri, 4 Jun 2010 10:49:21 -0400 | From | Vivek Goyal <> | Subject | Re: [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing |
| |
On Fri, Jun 04, 2010 at 05:49:36PM +0800, Américo Wang wrote: > On Thu, Jun 03, 2010 at 05:13:47PM +0200, Andi Kleen wrote: > >> > NMI would be only needed if the crash kernel is completely > >> > hosed too. > >> > >> That's the case. > > > >You're saying it booted but is hosed after boot? > > > >That seems like a very obscure case. Is that really common? > > > > Actually, I met two of this kind of cases recently. > > One was stucked in early_idt_hander() during booting the second kernel, > the other one is even worse, I even can't find where it hangs.
If you can't initialize the idt, will NMI work?
I think we need to fix those cases instead of creating another NMI handler. To handle cases like network is not up or there is not sufficient space on disk, a user space utility in kdump initrd should work.
Thanks Vivek
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |