Re: HEAD/6.1_RC2 DOM0 problems?

[Chuck Silvers <chuq%chuq.com@localhost>]

On Sat, Mar 23, 2013 at 10:16:34AM -0700, Jeff Rizzo wrote:
> On 3/23/13 9:17 AM, Manuel Bouyer wrote:
> >On Sat, Mar 23, 2013 at 08:15:50AM -0700, Jeff Rizzo wrote:
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 5 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 6 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 7 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 8 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 9 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 10 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 11 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 12 already mapped
> >>(XEN) irq.c:1514: dom0: pirq 0 or irq 13 already mapped
> >>ioapic0: can't remap to apid 4
> >>ioapic1 at mainbus0 apid 5
> >>ioapic1: can't remap to apid 5
> >>ioapic2 at mainbus0 apid 6
> >>
> >><hang>
> >>
> >
> >
> >I was not aware of the HEAD issue, maybe we should try to not remap ioapic
> >which already has the right apid ...
> >
> 
> I actually just got this same hang on the 6.1_RC2 dom0 kernel with
> Chuck's patch.  :/

I tried a few older kernels, I'm now getting the same remap errors with
6.0-RELEASE and even a netbsd-5 branch kernel.  but I don't remember seeing
those messages before, and I'm not sure what changed that would cause me
to see them now.  I thought it might have been that I upgraded to a newer
xen kernel, but the binary I have is dated last july, and I think I've tested
something with xen since then.  maybe not, though.

anyway, I don't have have any problem with a -current or netbsd-6 DOM0
in spite of the remap error messages, and this is with AMD CPUs.

-Chuck