[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVhbAM9vjx-uFcuc0ndsUp0aez9_TsQHStje5G5iwYbag@mail.gmail.com>
Date: Thu, 16 Feb 2012 13:53:29 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Don Zickus <dzickus@...hat.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
torvalds@...ux-foundation.org, kexec@...ts.infradead.org,
vgoyal@...hat.com, akpm@...ux-foundation.org, tglx@...utronix.de,
mingo@...e.hu, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in
crash path
On Thu, Feb 16, 2012 at 9:27 AM, Don Zickus <dzickus@...hat.com> wrote:
> So I think I figured it out. I went through and commented out code in
> disable_local_APIC until I narrowed it down to the piece of code that
> needs to be disabled for it to work.
>
> Surprise, surprise... its LVTPC or perf! :-) Actually it is the
> nmi_watchdog which uses perf. My theory is NMIs are not disabled and one
> is generated by the local apic during decompression (just bad timing) and
> *splat*.
>
> Yinghai, you can probably prove this by
>
> echo 0 > /proc/sys/kernel/nmi_watchdog
>
> then do your kdump crash test.
yes. that will make kdump crash working.
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists