[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120213221258.GP9751@redhat.com>
Date: Mon, 13 Feb 2012 17:12:58 -0500
From: Don Zickus <dzickus@...hat.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
torvalds@...ux-foundation.org, kexec@...ts.infradead.org,
vgoyal@...hat.com, ebiederm@...ssion.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 Mon, Feb 13, 2012 at 08:52:19AM -0800, Yinghai Lu wrote:
> On Mon, Feb 13, 2012 at 7:28 AM, Don Zickus <dzickus@...hat.com> wrote:
> > On Sat, Feb 11, 2012 at 05:04:15PM -0800, Yinghai Lu wrote:
> >> >
> >> > v2: removed the disable lapic code too
> >>
> >> with this commit, kdump is not working anymore on my setups with
> >> Nehalem, Westmere, sandbridge.
> >> these setup all have VT-d enabled.
> >
> > Hi Yinghai,
> >
> > Thanks for the report. Can you attach the .config you were using and what
> > vendor you were using for Nehalem, Westmere and Sandybridge. I'll try to
> > reproduce it in my lab.
>
> Sure, please check attached one
Looks like I can reproduce the hang with my original patch and things work
when we stick the disable_local_APIC() back in there. I'll keep poking.
Cheers,
Don
--
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