On 11/26/18 13:31, John Baldwin wrote:
> 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
On Mon, Nov 26, 2018 at 10:31:43AM -0800, John Baldwin wrote:
> 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:
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:
>
On 11/25/18 18:22, Richard M.Timoney wrote:
> 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
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:
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 0x8060a4e7 at kdb_backtrace+0x67
#1
