From owner-freebsd-net@freebsd.org  Sat Feb 17 13:57:51 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:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F3F4F101C3;
 Sat, 17 Feb 2018 13:57:51 +0000 (UTC)
 (envelope-from greg@unrelenting.technology)
Received: from hraggstad.unrelenting.technology
 (hraggstad.unrelenting.technology [71.19.146.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "hraggstad.unrelenting.technology",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 017FC7F7E8;
 Sat, 17 Feb 2018 13:57:50 +0000 (UTC)
 (envelope-from greg@unrelenting.technology)
Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id
 9e8bb61a
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO;
 Sat, 17 Feb 2018 13:51:07 +0000 (UTC)
Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update
To: Hans Petter Selasky <hps@selasky.org>, freebsd-net@freebsd.org,
 freebsd-current@freebsd.org
References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology>
 <cd223168-28a2-de44-0eef-f7fbd2e3b5cc@selasky.org>
 <cc1e0689-bd11-fb21-3b8f-8464a11461a1@unrelenting.technology>
 <d47071c3-3382-0d20-24d0-28cd4613c7ab@selasky.org>
From: Greg V <greg@unrelenting.technology>
Message-ID: <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology>
Date: Sat, 17 Feb 2018 16:51:04 +0300
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <d47071c3-3382-0d20-24d0-28cd4613c7ab@selasky.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
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: Sat, 17 Feb 2018 13:57:51 -0000

On 01/20/2018 12:18, Hans Petter Selasky wrote:
> On 01/20/18 00:17, Greg V via freebsd-net wrote:
>>
>> On 01/19/2018 12:54, Hans Petter Selasky wrote:
>>> 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?!
Upgraded CURRENT again today, the problem went away :)