Messages in this thread | | | Date | Mon, 13 Feb 2012 17:51:15 -0500 | From | Don Zickus <> | Subject | Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in crash path |
| |
On Mon, Feb 13, 2012 at 05:12:58PM -0500, Don Zickus wrote: > 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@redhat.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.
Hmm, my config worked fine in both cases, hence why I didn't catch it (its based on a bloated Fedora config). I'll look at the differences to see if something pops out.
Cheers, Don -- 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/
| |