xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Kristoffer Harthing Egefelt <k@itoc.dk>
To: xen-devel@lists.xensource.com
Subject: Re: no-carrier on qlogic 8242 10gig with linux	3.x	running xen
Date: Wed, 28 Mar 2012 05:57:22 -0700 (PDT)	[thread overview]
Message-ID: <1332939442151-5600390.post@n5.nabble.com> (raw)
In-Reply-To: <4F72E6B0.3080405@citrix.com>

>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.

  reply	other threads:[~2012-03-28 12:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  8:48 no-carrier on qlogic 8242 10gig with linux 3.x running xen Kristoffer Harthing Egefelt
2012-03-27  9:25 ` Wei Liu
2012-03-27  9:43   ` Kristoffer Harthing Egefelt
2012-03-27 10:02     ` Wei Liu
2012-03-27 12:41       ` Pasi Kärkkäinen
2012-03-27 16:23         ` Kristoffer Harthing Egefelt
2012-03-27 16:37           ` Wei Liu
2012-03-27 18:45             ` Kristoffer Harthing Egefelt
2012-03-27 18:58               ` Konrad Rzeszutek Wilk
2012-03-27 18:59                 ` Konrad Rzeszutek Wilk
2012-03-27 19:26           ` Pasi Kärkkäinen
2012-03-27 20:29             ` Kristoffer Harthing Egefelt
2012-03-27 21:31               ` Kristoffer Harthing Egefelt
2012-03-27 21:51                 ` Konrad Rzeszutek Wilk
2012-03-27 22:35                   ` Kristoffer Harthing Egefelt
2012-03-28 14:37                     ` Konrad Rzeszutek Wilk
2012-03-29  8:30                       ` Kristoffer Harthing Egefelt
2012-03-29 14:59                         ` Konrad Rzeszutek Wilk
2012-03-29 18:43                           ` Kristoffer Harthing Egefelt
2012-05-10 15:42                             ` Konrad Rzeszutek Wilk
2012-05-13 20:24                               ` Kristoffer Harthing Egefelt
2012-05-23  9:40                                 ` Kristoffer Harthing Egefelt
2012-05-23 14:27                                   ` Pasi Kärkkäinen
2012-05-25 21:03                                   ` Konrad Rzeszutek Wilk
2012-03-28  8:55                 ` Fajar A. Nugraha
2012-03-28  9:29                   ` Kristoffer Harthing Egefelt
2012-03-28 13:27                     ` Andrew Cooper
2012-03-29  8:35                       ` Kristoffer Harthing Egefelt
2012-03-29 11:50                         ` Andrew Cooper
2012-03-28  9:15               ` Ian Campbell
2012-03-28  9:55                 ` Kristoffer Harthing Egefelt
2012-03-28 10:23                   ` Andrew Cooper
2012-03-28 12:57                     ` Kristoffer Harthing Egefelt [this message]
2012-03-28 13:06                       ` Jan Beulich
2012-07-31 21:50       ` Anirban Chakraborty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1332939442151-5600390.post@n5.nabble.com \
    --to=k@itoc.dk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).