netdev - Re: mlx4: "failed to allocate default counter port 1"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5592913C.3000207@mellanox.com>
Date:	Tue, 30 Jun 2015 15:53:16 +0300
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	Sebastian Ott <sebott@...ux.vnet.ibm.com>
CC:	Eran Ben Elisha <eranbe@...lanox.com>,
	Jack Morgenstein <jackm@....mellanox.co.il>,
	Hadar Hen Zion <hadarh@...lanox.com>,
	<netdev@...r.kernel.org>
Subject: Re: mlx4: "failed to allocate default counter port 1"

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.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html