[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] no-carrier on qlogic 8242 10gig with linux 3.x running xen


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Kristoffer Harthing Egefelt <k@xxxxxxx>
  • Date: Wed, 28 Mar 2012 05:57:22 -0700 (PDT)
  • Delivery-date: Wed, 28 Mar 2012 12:58:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

>The IRQs listed when querying the hardware are the Xen IRQs, not dom0 IRQs.
>You can find the mapping with the 'i' debug key.

>If you are using xl, then something like:
>  xl debug-keys 'i'
>  xl dmesg | less

Good stuff - but can you explain how come, in the BIOS, the NIC and the RAID
controller share IRQ 15, but in /proc/interrupts they have different irqs:

  16:       6326  xen-pirq-ioapic-level  megasas
  38:      83524 xen-pirq-ioapic-level  eth0[0], eth1[0]
 
Does this mean that there shouldn't be any interrupt collisions using
pci=nomsi ?

--
View this message in context: 
http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5600390.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.