Date: Tue, 17 Feb 2015 10:56:57 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: sbruno@freebsd.org Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Xen HVM Panic, HEAD Message-ID: <20150217085657.GR34251@kib.kiev.ua> In-Reply-To: <54E2BF1E.4090002@ignoranthack.me> References: <54E2BF1E.4090002@ignoranthack.me>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > https://people.freebsd.org/~sbruno/Xen_APIC_panic.png > > I suspect that there may be one or two more lines above this that are > relevant to this panic, but XENHVM kernel's now panic booting on Xen > server. The working kernel output looks like this: > > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > XEN: Hypervisor version 4.2 detected. > CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz > K8-class CPU) > Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 > Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> > Features2=0x81ba2201<SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV> > AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> > AMD Features2=0x1<LAHF> > Hypervisor: Origin = "XenVMMXenVMM" > real memory = 1434451968 (1368 MB) > avail memory = 1353293824 (1290 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: <Xen HVM> > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 2 > ioapic0: Changing APIC ID to 1 > MADT: Forcing active-low polarity and level trigger for SCI I am not sure why your machine uses native lapic instead of xen lapic, and should it be other way, or not. Regardless, show the line number for the ipi_startup+0x56. Did you performed clean kernel build ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150217085657.GR34251>