Date: Sat, 17 Feb 2018 15:19:28 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Greg V <greg@unrelenting.technology>, freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update Message-ID: <1ab033e3-114f-eeed-47e5-3b144240f2cc@selasky.org> In-Reply-To: <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology> 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> <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/17/18 14:51, Greg V wrote: > 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 :) OK, nice to know. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ab033e3-114f-eeed-47e5-3b144240f2cc>