From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristoffer Harthing Egefelt Subject: Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen Date: Wed, 28 Mar 2012 05:57:22 -0700 (PDT) Message-ID: <1332939442151-5600390.post@n5.nabble.com> References: <1332840330.2485.70.camel@leeds.uk.xensource.com> <1332841414026-5597400.post@n5.nabble.com> <1332842573.2485.88.camel@leeds.uk.xensource.com> <20120327124113.GP12984@reaktio.net> <1332865415525-5598276.post@n5.nabble.com> <20120327192644.GQ12984@reaktio.net> <1332880165775-5598838.post@n5.nabble.com> <1332926106.7702.13.camel@zakaz.uk.xensource.com> <1332928550416-5599996.post@n5.nabble.com> <4F72E6B0.3080405@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F72E6B0.3080405@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.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.