From: Or Gerlitz <ogerlitz@mellanox.com>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Eran Ben Elisha <eranbe@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
Hadar Hen Zion <hadarh@mellanox.com>, <netdev@vger.kernel.org>
Subject: Re: mlx4: "failed to allocate default counter port 1"
Date: Tue, 30 Jun 2015 15:53:16 +0300 [thread overview]
Message-ID: <5592913C.3000207@mellanox.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1506301229520.1799@denkbrett>
On 6/30/2015 1:45 PM, Sebastian Ott wrote:
> [ 88.909558] mlx4_slave_cmd op=3840, ret=-22, status=3
> [ 88.909562] mlx4_core 0000:00:00.0: mlx4_allocate_default_counters: failed to allocate default counter port 1 err -22
> [ 88.909564] mlx4_core 0000:00:00.0: Failed to allocate default counters, aborting
> [ 88.961735] mlx4_core: probe of 0000:00:00.0 failed with error -22
Do you run the VF on the same system/kernel as the PF, or the VF is
probed to VM which runs the latest kernel and the PF runsolder kernel
(which?)
Can you also hook the PF code that serves this flow to see where we
actually fail? basically, we should be going this way
mlx4_ALLOC_RES_wrapper --> counter_alloc_res -- so I'd like to see which
of the branches in counter_alloc_res fails...
Or.
next prev parent reply other threads:[~2015-06-30 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 10:45 mlx4: "failed to allocate default counter port 1" Sebastian Ott
2015-06-30 12:21 ` Or Gerlitz
2015-06-30 13:19 ` Sebastian Ott
2015-06-30 12:53 ` Or Gerlitz [this message]
2015-06-30 13:24 ` Sebastian Ott
2015-06-30 13:52 ` Or Gerlitz
2015-06-30 14:17 ` Sebastian Ott
2015-07-01 13:18 ` Or Gerlitz
2015-07-01 13:59 ` Sebastian Ott
2015-07-01 14:18 ` Sebastian Ott
2015-07-01 20:38 ` Or Gerlitz
2015-07-02 9:20 ` Sebastian Ott
2015-07-29 12:50 ` Sebastian Ott
2015-07-29 13:25 ` Or Gerlitz
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=5592913C.3000207@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=eranbe@mellanox.com \
--cc=hadarh@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=sebott@linux.vnet.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).