Messages in this thread | | | Date | Tue, 25 Aug 2009 13:42:33 +0200 | From | Andreas Herrmann <> | Subject | Re: BUG: 2.6.30.1 pv_ops kernel boot failure - bisected |
| |
On Tue, Aug 25, 2009 at 12:04:54PM +0100, James Dingwall wrote: > > Hi, > > I have encountered what appears to be a bug when using the 2.6.30 stable > series as a pv_ops kernel under Xen 3.4.1. The problem appears to have > been introduced with the following commit (provided I bisected it > correctly) > > commit bb9b409349f533a919b6b6d95698fbe6ff4aa209 > Author: Andreas Herrmann <andreas.herrmann3@amd.com> > Date: Mon Jun 8 15:55:09 2009 +0200 > > x86: Detect use of extended APIC ID for AMD CPUs > > When I try and boot the domU (xm create -c) I do not get any output. > With this commit reverted I can boot 2.6.30.5 pv_ops without issue, > output follows below. The system is a dual Opteron 242. If more > details about the hardware or configuration are required to debug this > please let me know. I'm willing to test any patches.
So it seems that commit
commit 2cb078603abb612e3bcd428fb8122c3d39e08832 Author: Jeremy Fitzhardinge <jeremy@goop.org> Date: Wed Jul 22 09:59:35 2009 -0700
x86, amd: Don't probe for extended APIC ID if APICs are disabled
If we've logically disabled apics, don't probe the PCI space for the AMD extended APIC ID.
[ Impact: prevent boot crash under Xen. ]
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Reported-by: Bastian Blank <bastian@waldi.eu.org> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
needs to be added to 2.6.30.y for proper boot under Xen. James, can you test this please?
Thanks,
Andreas
-- Operating | Advanced Micro Devices GmbH System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany Research | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München (OSRC) | Registergericht München, HRB Nr. 43632
-- 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/
| |