netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: brouer@redhat.com, Tariq Toukan <tariqt@mellanox.com>,
	Eran Ben Elisha <eranbe@mellanox.com>
Subject: mlx5 driver loading failing on v4.19 / net-next / bpf-next
Date: Wed, 29 Aug 2018 17:05:00 +0200	[thread overview]
Message-ID: <20180829170358.5d822db8@redhat.com> (raw)

Hi Saeed,

I'm having issues loading mlx5 driver on v4.19 kernels (tested both
net-next and bpf-next), while kernel v4.18 seems to work.  It happens
with a Mellanox ConnectX-5 NIC (and also a CX4-Lx but I removed that
from the system now).

One pain point is very long boot-time, caused by some timeout code in
the driver. The kernel console log (dmesg) says:

[    5.763330] mlx5_core 0000:03:00.0: firmware version: 16.22.1002
[    5.769367] mlx5_core 0000:03:00.0: 126.016 Gb/s available PCIe bandwidth, limited by 8 GT/s x16 link at 0000:00:02.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)

(...) other drivers loading

[   66.816635] mlx5_core 0000:03:00.0: wait_func:964:(pid 112): ENABLE_HCA(0x104) timeout. Will cause a leak of a command resource
[   66.828123] mlx5_core 0000:03:00.0: enable hca failed
[   66.845516] mlx5_core 0000:03:00.0: mlx5_load_one failed with error code -110
[   66.852802] mlx5_core: probe of 0000:03:00.0 failed with error -110

[   66.859347] mlx5_core 0000:03:00.1: firmware version: 16.22.1002
[   66.865388] mlx5_core 0000:03:00.1: 126.016 Gb/s available PCIe bandwidth, limited by 8 GT/s x16 link at 0000:00:02.0 (capable of 252.048 Gb/s with 16 GT/s x16 link)

[  125.787395] XFS (sda3): Mounting V5 Filesystem
[  125.848509] XFS (sda3): Ending clean mount
[  127.984784] mlx5_core 0000:03:00.1: wait_func:964:(pid 5): ENABLE_HCA(0x104) timeout. Will cause a leak of a command resource
[  127.996090] mlx5_core 0000:03:00.1: enable hca failed
[  128.013819] mlx5_core 0000:03:00.1: mlx5_load_one failed with error code -110
[  128.021076] mlx5_core: probe of 0000:03:00.1 failed with error -110


Do you have any idea what could be causing this?

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

             reply	other threads:[~2018-08-29 19:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 15:05 Jesper Dangaard Brouer [this message]
2018-08-30  8:35 ` mlx5 driver loading failing on v4.19 / net-next / bpf-next Tariq Toukan
  -- strict thread matches above, loose matches on Subject: below --
2018-09-13 22:55 Alexei Starovoitov
2018-09-14  6:36 ` Jesper Dangaard Brouer
2018-09-14  8:22   ` Saeed Mahameed
2018-09-14  8:52     ` Jesper Dangaard Brouer
2018-09-14 18:26       ` Saeed Mahameed

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=20180829170358.5d822db8@redhat.com \
    --to=brouer@redhat.com \
    --cc=eranbe@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.com \
    --cc=tariqt@mellanox.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).