<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>They do not appear to be.<br><br>ivtv0 = 22<br>ivtv1 = 17<br>eth0 = 20<br><br>
However ivtv1 is sharing with some part fo the chipset:<br><br>dragonfly ~ # cat /proc/interrupts<br> CPU0<br> 0: 14871236 IO-APIC-edge timer<br> 1: 23821 IO-APIC-edge i8042<br> 9: 0 IO-APIC-level acpi
<br> 12: 308115 IO-APIC-edge i8042<br> 14: 187334 IO-APIC-edge ide0<br> 15: 49 IO-APIC-edge ide1<br> 16: 485287 IO-APIC-level uhci_hcd:usb2, uhci_hcd:usb5,<br>i915@pci:0000:00:02.0<br> 17: 57811 IO-APIC-level ivtv1, Intel ICH5
<br> 18: 109 IO-APIC-level uhci_hcd:usb4<br> 19: 174 IO-APIC-level uhci_hcd:usb3<br> 20: 8034881 IO-APIC-level eth0<br> 22: 38977 IO-APIC-level ivtv0<br> 23: 4 IO-APIC-level ehci_hcd:usb1
<br>NMI: 0<br>LOC: 14872124<br>ERR: 0<br>MIS: 0<br>dragonfly ~ #<br></blockquote></div><br>
<br>
I was having a very similiar problem, which is why I asked. For
me, it wasn't just failing though it was resulting in lock ups.
The solution was to turn off APIC in the BIOS and it's been hunky dory
since.<br>