I believe after the commit 340016 for the dynamic IRQ layout, my Xen VM
started to panic. I just upgraded the kernel today and saw this:
xen: unable to map IRQ#2
panic: Unable to register interrupt override
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff8060a4e7 at kdb_backtrace+0x67
#1 0xffffffff805c3787 at vpanic+0x177
#2 0xffffffff805c3603 at panic+0x43
#3 0xffffffff8093a766 at madt_parse_ints+0x96
#4 0xffffffff803353f9 at acpi_walk_subtables+0x29
#5 0xffffffff8093a5e6 at xenpv_register_pirqs+0x56
#6 0xffffffff80928296 at intr_init_sources+0x116
#7 0xffffffff8055eba8 at mi_startup+0x118
#8 0xffffffff8029902c at btext+0x2c
The following kernel works:
@(#)FreeBSD 11.2-STABLE #4: Thu Nov 1 02:24:07 EDT 2018
FreeBSD 11.2-STABLE #4: Thu Nov 1 02:24:07 EDT 2018
root at creme-brulee:/usr/obj/usr/src/sys/CREME-BRULEE
The following kernel produces the panic above immediately on boot:
@(#)FreeBSD 11.2-STABLE #5: Wed Nov 21 11:08:38 EST 2018
FreeBSD 11.2-STABLE #5: Wed Nov 21 11:08:38 EST 2018
root at creme-brulee:/usr/obj/usr/src/sys/CREME-BRULEE
Attached is a screen grab of the console of the panic.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
I have the same failure to boot 11-stable as a DomU host on xen_version:
4.4.1
Kernel I was trying was recent, FreeBSD 11.2-STABLE (GENERIC) #23
r334205:340834
commit 340016 for the dynamic IRQ layout seems rather involved and I doubt I
could isolate the problem, but maybe it is in
338631:
xen: legacy PVH fixes for the new interrupt count
Register interrupts using the PIC pic_register_sources method instead
of doing it in apic_setup_io. This is now required, since the internal
interrupt structures are not yet setup when calling apic_setup_io.
--
Richard M. Timoney
(richardt at maths.tcd.ie) Tel. +353-1-896 1196
School of Mathematics, Trinity College, Dublin 2, Ireland
WWW https://www.maths.tcd.ie/~richardt FAX +353-1-896 2282
On 11/22/18 12:39 PM, Joe Clarke wrote:> I believe after the commit 340016 for the dynamic IRQ layout, my Xen VM > started to panic. I just upgraded the kernel today and saw this: > > xen: unable to map IRQ#2 > panic: Unable to register interrupt override > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff8060a4e7 at kdb_backtrace+0x67 > #1 0xffffffff805c3787 at vpanic+0x177 > #2 0xffffffff805c3603 at panic+0x43 > #3 0xffffffff8093a766 at madt_parse_ints+0x96 > #4 0xffffffff803353f9 at acpi_walk_subtables+0x29 > #5 0xffffffff8093a5e6 at xenpv_register_pirqs+0x56 > #6 0xffffffff80928296 at intr_init_sources+0x116 > #7 0xffffffff8055eba8 at mi_startup+0x118 > #8 0xffffffff8029902c at btext+0x2c > > The following kernel works: > > @(#)FreeBSD 11.2-STABLE #4: Thu Nov 1 02:24:07 EDT 2018 > FreeBSD 11.2-STABLE #4: Thu Nov 1 02:24:07 EDT 2018 > root at creme-brulee:/usr/obj/usr/src/sys/CREME-BRULEE > > The following kernel produces the panic above immediately on boot: > > @(#)FreeBSD 11.2-STABLE #5: Wed Nov 21 11:08:38 EST 2018 > FreeBSD 11.2-STABLE #5: Wed Nov 21 11:08:38 EST 2018 > root at creme-brulee:/usr/obj/usr/src/sys/CREME-BRULEE > > Attached is a screen grab of the console of the panic.Hmm, I don't see any obvious candidates of Xen changes that weren't included in the MFC. I've added royger@ (who maintains Xen in FreeBSD) to the cc to see if he has an idea. Roger, the main changes that aren't MFC'd to 11 from 12/head seem to be some refcounting on event channels and PVHv2 vs PVHv1? -- John Baldwin ????????????????????????????????????????????????????????????????????????????