"Multiple entries for PCI IRQ 16" and "xlock already held"
panics on 5.3-BETA(3,4,5)
Pavel Gubin
pg at ie.tusur.ru
Thu Sep 23 09:55:28 PDT 2004
On Thu, Sep 23, 2004 at 10:29:47AM -0400, John Baldwin wrote:
> > > > panices immediately with "panic: Multiple entries for PCI IRQ 16"
[]
> > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN#
> > INT active-lo level 0 2:A 2 16
> > INT active-lo level 0 2:A 2 23
>
> This is the real bug and I guess I can improve the message. Then problem is
> not two lines for IRQ 16, but that the PCI interrrupt for bus 0, device 2,
> pin #A has two different IRQs listed, so we don't know which one we are
> supposed to use. This is definitely a BIOS bug and your motherboard
> manufacturer needs to harassed into giving you a BIOS update.
Then shame on MSI.. And some stupid question - maybe a kernel can be given
a hint which one to use (e.g. using /boot/loader.conf...)? Just in case this
is not very uncommon situation to find such a bug in MP table.
> > > > panic: _sx_xlock (user map): xlock already held @
> > > > /var/data/5/src/sys/vm/vm_map.c:2997 cpuid = 0
> > >
> > > This is the real bug, can you do 'l *0xc05b541c' from kgdb?
> >
> > (kgdb) l *0xc05b541c
> > 0xc05b541c is in pmap_enter_quick
>
> I would try asking alc@ if he has any ideas for this one.
Then if I may help in some way (testing patch etc) - I'm at your service
:)
--
Pavel Gubin
TUSC&R / Industrial Electronics dept / System Administrator
2:5005/14 at fidonet / Phone +7-3822-423067 / ICQ 28835566
More information about the freebsd-current
mailing list