From owner-freebsd-net@freebsd.org  Fri Jan 19 09:57:23 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 BDE42ECDD2C;
 Fri, 19 Jan 2018 09:57:23 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (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 85A587ACFC;
 Fri, 19 Jan 2018 09:57:22 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.128.70])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 663D026009E;
 Fri, 19 Jan 2018 10:57:19 +0100 (CET)
Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update
To: Greg V <greg@unrelenting.technology>, freebsd-net@freebsd.org,
 freebsd-current@freebsd.org
References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <cd223168-28a2-de44-0eef-f7fbd2e3b5cc@selasky.org>
Date: Fri, 19 Jan 2018 10:54:27 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jan 2018 09:57:23 -0000

On 01/18/18 14:11, Greg V wrote:
> Hi. I've upgraded CURRENT from December 19 
> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) to 
> today 
> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) 
> and my Mellanox ConnectX-2 network card stopped working:
> 
> mlx4_core0: <mlx4_core> mem 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff 
> irq 32 at device 0.0 on pci7
> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017)
> mlx4_core: Initializing mlx4_core
> mlx4_core0: command 0xffa failed: fw status = 0x1
> mlx4_core0: Failed to map EQ context memory, aborting
> device_attach: mlx4_core0 attach returned 12
> 
> 
> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually does 
> work fine!
> 
> Reverting all mlx4 changes between then and now (no big changes, mostly 
> just the 1 << 31 thing from D13858) and rebuilding the mlx4 module with 
> CC=clang50 does not help.
> 
> What happened?!

Hi,

Can you do:

objdump -Dx /boot/kernel/mlx4.ko > mlx4.ko.txt
objdump -Dx /boot/kernel/mlx4en.ko > mlx4en.ko.txt

And diff the text result between working and non-working ko's.

Can you also make sure that /boot/modules does not contain anything *mlx4* ?

--HPS