From: Bjorn Helgaas <helgaas@kernel.org>
To: Eugenia Emantayev <eugenia@mellanox.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: mlx4 fails ("go bit not cleared") without MSI
Date: Wed, 13 Jan 2016 16:08:43 -0600 [thread overview]
Message-ID: <20160113220843.GA21544@localhost> (raw)
Hi Eugenia,
Due to my own stupidity, I tried to use mlx4 without turning on
CONFIG_PCI_MSI=y. The driver failed miserably:
pci 0000:01:00.0: [15b3:1007] type 00 class 0x020000
mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
mlx4_core: Initializing 0000:01:00.0
mlx4_core 0000:01:00.0: PCIe link speed is 8.0GT/s, device supports 8.0GT/s
mlx4_core 0000:01:00.0: PCIe link width is x8, device supports x8
mlx4_core 0000:01:00.0: command 0x23 timed out (go bit not cleared)
mlx4_core 0000:01:00.0: device is going to be reset
mlx4_core 0000:01:00.0: device was reset successfully
mlx4_core 0000:01:00.0: Failed to initialize queue pair table, aborting
mlx4_core: probe of 0000:01:00.0 failed with error -5
The lack of MSI was my own fault, but it took me a long time to figure it
out.
The fact that mlx4 has a "msi_x" module parameter makes me think that
mlx4 is *supposed* to work without MSI. Would you consider either
fixing the non-MSI fallback path, or printing a warning when the
driver can't set up MSIs?
This is easy to reproduce; just turn off CONFIG_PCI_MSI or boot with
"pci=nomsi".
Bjorn
next reply other threads:[~2016-01-13 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 22:08 Bjorn Helgaas [this message]
[not found] <HE1PR05MB1418EEAC4F82E2ECF9AC0920CEC10@HE1PR05MB1418.eurprd05.prod.outlook.com>
[not found] ` <CAErSpo5PsAvix815Z1Ge5-UTx5z-0m5W2p4F9J=s8AB03=C+Dw@mail.gmail.com>
2016-01-20 9:42 ` mlx4 fails ("go bit not cleared") without MSI Yishai Hadas
2016-01-20 17:00 ` Bjorn Helgaas
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=20160113220843.GA21544@localhost \
--to=helgaas@kernel.org \
--cc=eugenia@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 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).