From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Jack Morgenstein <jackm@dev.mellanox.co.il>
Cc: linux-pci@vger.kernel.org, yinghai@kernel.org,
bhelgaas@google.com, amirv@mellanox.com, ogerlitz@mellanox.com,
eugenia@mellanox.com, Guo Chao <yan@linux.vnet.ibm.com>,
Gavin Shan <shangw@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@au1.ibm.com>
Subject: Re: mlx4_core probe error after applying Yinghai's patch
Date: Tue, 14 Jan 2014 17:15:25 +0800 [thread overview]
Message-ID: <20140114091525.GB27684@richard> (raw)
In-Reply-To: <20140114105031.71882944@jpm-OptiPlex-GX620>
On Tue, Jan 14, 2014 at 10:50:31AM +0200, Jack Morgenstein wrote:
>On Tue, 14 Jan 2014 14:22:15 +0800
>Wei Yang <weiyang@linux.vnet.ibm.com> wrote:
>
>> Error log:
>> mlx4_core 0003:05:00.0: Multiple PFs not yet supported. Skipping
>> PF. mlx4_core: probe of 0003:05:00.0 failed with error -22
>
>1. Please include the full error log starting from host bootup and
>driver start
Will provide one later.
>
>2. What FW is loaded on the card?
$ mst status
MST modules:
------------
MST PCI module loaded
MST PCI configuration module loaded
MST devices:
------------
/dev/mst/mt4099_pciconf0 - PCI configuration cycles access.
domain:bus:dev.fn=0003:05:00.0 addr.reg=88 data.reg=92
Chip revision is: 01
/dev/mst/mt4099_pci_cr0 - PCI direct access.
domain:bus:dev.fn=0003:05:00.0 bar=0x3d0508d300000 size=0x100000
Chip revision is: 01
# mlxburn -d /dev/mst/mt4099_pci_cr0 -fwver
-I- FW Version: 2.30.3200
>
>3. Please provide output of "lspci -vv -nn" for the Mellanox device(s)
$lspci | grep Mel
0003:05:00.0 Network controller: Mellanox Technologies MT27500 Family [ConnectX-3]
$lspci -s 0003:05:00.0 -n
0003:05:00.0 0280: 15b3:1003
The output with -vvv is attached in the first mail.
--
Richard Yang
Help you, Help me
next prev parent reply other threads:[~2014-01-14 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 6:22 mlx4_core probe error after applying Yinghai's patch Wei Yang
2014-01-14 7:55 ` Or Gerlitz
2014-01-14 8:27 ` Wei Yang
2014-01-14 8:39 ` Or Gerlitz
2014-01-14 8:52 ` Wei Yang
2014-01-14 8:50 ` Jack Morgenstein
2014-01-14 9:15 ` Wei Yang [this message]
2014-01-14 10:25 ` Jack Morgenstein
2014-01-14 11:19 ` Guo Chao
[not found] ` <52d51b4c.c413ec0a.290f.03c3SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-14 11:21 ` Jack Morgenstein
[not found] ` <20140114103712.GD27684@richard>
[not found] ` <20140114132340.50df7d6f@jpm-OptiPlex-GX620>
[not found] ` <52d52032.4981e00a.3dcc.ffff81fdSMTPIN_ADDED_BROKEN@mx.google.com>
[not found] ` <20140115094113.64ca756e@jpm-OptiPlex-GX620>
[not found] ` <1389772791.6933.84.camel@pasglop>
[not found] ` <52d653d3.8425e00a.76d0.1e60SMTPIN_ADDED_BROKEN@mx.google.com>
[not found] ` <20140115160204.24a44af0@jpm-OptiPlex-GX620>
[not found] ` <20140116020946.GA8702@richard>
[not found] ` <20140116021429.GB8702@richard>
2014-01-29 8:50 ` Or Gerlitz
2014-01-30 7:08 ` Wei Yang
2014-01-30 8:09 ` Or Gerlitz
2014-01-14 8:54 ` Jack Morgenstein
2014-01-14 9:16 ` Wei Yang
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=20140114091525.GB27684@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=amirv@mellanox.com \
--cc=benh@au1.ibm.com \
--cc=bhelgaas@google.com \
--cc=eugenia@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=linux-pci@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=shangw@linux.vnet.ibm.com \
--cc=yan@linux.vnet.ibm.com \
--cc=yinghai@kernel.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.