From: Michael Ellerman <michael@ellerman.id.au>
To: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Ameen Rahman <ameen.rahman@qlogic.com>
Subject: Re: MSI-X vector allocation failure in upstream kernel
Date: Wed, 13 Oct 2010 12:51:28 +1100 [thread overview]
Message-ID: <1286934688.24583.12.camel@concordia> (raw)
In-Reply-To: <9101728E-3FFC-457E-AF5B-87B2037FEC32@qlogic.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
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.
OK, that's the platform code saying it can only support 2, that seems
low, but it's possible.
> The driver again attempts, this time for 2 vectors but the kernel can't allocate
> and it returns a value of 0xfffffffd.
OK, that's odd. That is -3, which AFAICS we don't return from the linux
code. So it must be coming from firmware? In which case it would be
"parameter error".
> I upgraded the system FW to 01EL350 (from 01EL340) just to make sure
> if MSI-X is enabled in the system.
Is that the latest FW version?
Adding #define DEBUG at the top of arch/powerpc/platforms/pseries/msi.c
will give us lots of useful info.
Or you can enable CONFIG_DYNAMIC_DEBUG, and enable it that way.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-10-13 1:51 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
2010-10-13 1:51 ` Michael Ellerman [this message]
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=1286934688.24583.12.camel@concordia \
--to=michael@ellerman.id.au \
--cc=ameen.rahman@qlogic.com \
--cc=anirban.chakraborty@qlogic.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.