From owner-freebsd-net@freebsd.org Sat Jan 20 09:21:52 2018 Return-Path: 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 59AE8EC53D3; Sat, 20 Jan 2018 09:21:52 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 1BCEC701F8; Sat, 20 Jan 2018 09:21:52 +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 A803A26012B; Sat, 20 Jan 2018 10:21:49 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Hans Petter Selasky Message-ID: Date: Sat, 20 Jan 2018 10:18:57 +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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2018 09:21:52 -0000 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: 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. > That results in 180883 lines (9.2 megabytes) of diff for mlx4.ko. The > CC=clang50 one is only a bit better at 7.6 MB :( Can you open this diff using "meld". And look for instructions which have changed, not only their location. --HPS