From owner-freebsd-drivers@freebsd.org Sun Sep 4 16:00:23 2016 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B5D1A9D8A6 for ; Sun, 4 Sep 2016 16:00:23 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from smtp.hungerhost.com (smtp.hungerhost.com [216.38.51.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC5F9867 for ; Sun, 4 Sep 2016 16:00:22 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from pool-108-46-177-117.nycmny.fios.verizon.net ([108.46.177.117]:61583 helo=[192.168.1.11]) by vps.hungerhost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1bgZqH-00089X-A4; Sun, 04 Sep 2016 12:00:21 -0400 From: "George Neville-Neil" To: "Hans Petter Selasky" Cc: freebsd-drivers@freebsd.org Subject: Re: Issues with mlx5en ? Date: Sun, 04 Sep 2016 12:00:20 -0400 Message-ID: In-Reply-To: <11ee453b-1d4e-744c-65f5-7961f6cb61c7@selasky.org> References: <27D0515C-6567-447E-9B6C-8885538CDFD8@neville-neil.com> <11ee453b-1d4e-744c-65f5-7961f6cb61c7@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; markup=markdown X-Mailer: MailMate (1.9.5r5260) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com X-Authenticated-Sender: vps.hungerhost.com: gnn@neville-neil.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2016 16:00:23 -0000 On 29 Aug 2016, at 13:12, Hans Petter Selasky wrote: > On 08/29/16 18:35, George Neville-Neil wrote: >> Howdy, >> >> I'm trying to do some testing on the mlx5 cards at Sentex. WIth both >> HEAD and stable11 I get this: >> >> root@mercat1:~ # kldload mlx5en >> mlx5_core0: mem 0xf8000000-0xf9ffffff irq 32 at device >> 0.0 >> on pci3 >> mlx5_core0: INFO: firmware version: 12.100.6440 >> mlx5_core: WARN: command failed, status bad parameter(0x3), syndrome >> 0x5add95 >> mlx5_core: WARN: mlx5_core0:mlx5_core_get_caps:305:(pid 763): >> QUERY_HCA_CAP : type(9) opmode(1) Failed(-22) >> mlx5_core0: ERR: query hca failed >> mlx5_core0: ERR: mlx5_dev_init failed -22 >> device_attach: mlx5_core0 attach returned 22 >> mlx5_core0: mem 0xf6000000-0xf7ffffff irq 32 at device >> 0.1 >> on pci3 >> mlx5_core0: INFO: firmware version: 12.100.6440 >> mlx5_core: WARN: command failed, status bad parameter(0x3), syndrome >> 0x5add95 >> mlx5_core: WARN: mlx5_core0:mlx5_core_get_caps:305:(pid 763): >> QUERY_HCA_CAP : type(9) opmode(1) Failed(-22) >> mlx5_core0: ERR: query hca failed >> mlx5_core0: ERR: mlx5_dev_init failed -22 >> device_attach: mlx5_core0 attach returned 22 >> >> this is the output of pciconf -lv >> >> none72@pci0:2:0:0: class=0x020700 card=0x000815b3 >> chip=0x101315b3 >> rev=0x00 >> hdr=0x00 >> vendor = 'Mellanox Technologies' >> device = 'MT27700 Family [ConnectX-4]' >> class = network >> none73@pci0:2:0:1: class=0x020700 card=0x000815b3 >> chip=0x101315b3 >> rev=0x00 >> hdr=0x00 >> vendor = 'Mellanox Technologies' >> device = 'MT27700 Family [ConnectX-4]' >> class = network >> >> Thouhgts? > > Hi George, > > Did you try to upgrade the firmware? The latest official is 12.16.xxx? > > Also, did you try to set the port mode to ETH using: > > mlxconfig -d PCI_ID set LINK_TYPE_P1=2 > mlxconfig -d PCI_ID set LINK_TYPE_P2=2 > > Links: > http://www.mellanox.com/page/management_tools > http://www.mellanox.com/page/firmware_NIC_FW_update > With the firmware update the devices work, but netmap does not, which is a different issue, I know. Thanks, George