tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wm problem, the dmesg output
On Wed, Aug 06, 2008 at 06:48:21PM +0300, Jukka Marin wrote:
>
> wm2 at pci6 dev 0 function 0: Intel PRO/1000 PT (82571EB), rev. 6
> wm2: interrupting at ioapic0 pin 16, event channel 3
> ...
> wm3 at pci6 dev 0 function 1: Intel PRO/1000 PT (82571EB), rev. 6
> ioapic0: int17 1a9c0<vector=c0,delmode=1,logical,actlo,level,masked,dest=0>
> f000000<target=f>
> wm3: interrupting at ioapic0 pin 17, event channel 6
>
> and
>
> interrupt total rate
> ...
> vcpu0 ioapic0 pin 16 68529180 37
> vcpu0 ioapic0 pin 18 54273505 29
> vcpu0 ioapic0 pin 19 154071320 84
> vcpu0 ioapic0 pin 17 218 0
>
> and (from dmesg.boot):
>
> ioapic0: pin 16 attached to pci0 device 0 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci0 device 2 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci0 device 8 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci0 device 28 INT_B (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci0 device 29 INT_D (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci1 device 0 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci2 device 0 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci3 device 0 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci6 device 0 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci7 device 2 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci7 device 3 INT_A (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
> ioapic0: pin 16 attached to pci7 device 4 INT_D (type 0<type=0> flags
> f<pol=3=Act Lo,trig=3=Level>)
>
> So, (with no knowledge about today's pc hardware at all ;) there are
> multiple devices using this "pin 16" interrupt which appears to work?
Yes, there are multiple devices using pin 16. But maybe wm2 should be using
something else ... Are you using ACPI ? maybe try without it (needs to
be disabled at both xen.gz and netbsd level - I think for xen.gz it's
acpi=off, for netbsd just use -c and then 'disable acpi').
--
Manuel Bouyer, LIP6, Universite Paris VI.
Manuel.Bouyer%lip6.fr@localhost
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index