linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Michael Ellerman <michaele@au1.ibm.com>,
	Ameen Rahman <ameen.rahman@qlogic.com>
Subject: Re: MSI-X vector allocation failure in upstream kernel
Date: Fri, 08 Oct 2010 12:26:12 +1100	[thread overview]
Message-ID: <1286501172.2463.395.camel@pasglop> (raw)
In-Reply-To: <9101728E-3FFC-457E-AF5B-87B2037FEC32@qlogic.com>

On Tue, 2010-10-05 at 10:18 -0700, Anirban Chakraborty wrote:
> Hi All,
> 
> I am trying to test qlcnic driver (for 10Gb QLogic network adapter) on a Power 6 system 
> (IBM P 520, System type 8203) with upstream kernel and I do see that the kernel is 
> not able to allocate any MSI-X vectors. The driver requests for 4 vectors in pci_enable_msix,
> which returns 2. The driver again attempts, this time for 2 vectors but the kernel can't allocate 
> and it returns a value of 0xfffffffd. I upgraded the system FW to 01EL350 (from 01EL340)
>  just to make sure if MSI-X is enabled in the system. Is there anything that I am missing? 
> 
> Any pointers will be highly appreciated.

I think the people who can help you at the moment are on vacation :-)

Can you make sure kernel debug is enabled and you have "debug" on the
kernel command line, and send the full dmesg log of what's going on ?

Hopefully, Michael will be back next week and will be able to have a
look at it.

Cheers,
Ben.

  reply	other threads:[~2010-10-08  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 17:18 MSI-X vector allocation failure in upstream kernel Anirban Chakraborty
2010-10-08  1:26 ` Benjamin Herrenschmidt [this message]
2010-10-13  1:51 ` Michael Ellerman

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=1286501172.2463.395.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=ameen.rahman@qlogic.com \
    --cc=anirban.chakraborty@qlogic.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michaele@au1.ibm.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).