From owner-freebsd-current@freebsd.org  Thu Jan 18 13:11:22 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 CBD88E797FB;
 Thu, 18 Jan 2018 13:11:22 +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 B96086C90A;
 Thu, 18 Jan 2018 13:11:22 +0000 (UTC)
 (envelope-from greg@unrelenting.technology)
Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id
 ade421a3
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO;
 Thu, 18 Jan 2018 13:11:13 +0000 (UTC)
From: Greg V <greg@unrelenting.technology>
Subject: mlx4 weird error "Failed to map EQ context memory" after update
To: freebsd-net@freebsd.org, freebsd-current@freebsd.org
Message-ID: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology>
Date: Thu, 18 Jan 2018 16:11:11 +0300
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 13:11:22 -0000

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?!