From: Vivek Goyal <vgoyal@redhat.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Vitaly Mayatskikh <v.mayatskih@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing
Date: Fri, 4 Jun 2010 10:49:21 -0400 [thread overview]
Message-ID: <20100604144921.GG4111@redhat.com> (raw)
In-Reply-To: <20100604094936.GA5975@cr0.nay.redhat.com>
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
next prev parent reply other threads:[~2010-06-04 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 7:39 [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 1/5] x86: Introduce ELF_CORE_EXTRACT_REGS Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 2/5] x86: Split __show_regs() Vitaly Mayatskikh
2010-06-02 9:50 ` Pekka Enberg
2010-06-02 10:00 ` Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 3/5] vmcore: Introduce dump_old_log() Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 4/5] x86: Add new callback for unhandled NMIs Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 5/5] Document unknown_nmi_dump_log variable Vitaly Mayatskikh
2010-06-02 15:16 ` [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing Vivek Goyal
2010-06-03 9:01 ` Vitaly Mayatskikh
2010-06-03 9:30 ` Andi Kleen
2010-06-03 12:33 ` Vitaly Mayatskikh
2010-06-03 15:13 ` Andi Kleen
2010-06-04 9:32 ` Vitaly Mayatskikh
2010-06-04 10:15 ` Andi Kleen
2010-06-04 13:58 ` Vitaly Mayatskikh
2010-06-04 9:49 ` Américo Wang
2010-06-04 10:16 ` Andi Kleen
2010-06-04 14:49 ` Vivek Goyal [this message]
2010-06-04 14:42 ` Vivek Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100604144921.GG4111@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=v.mayatskih@gmail.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).