Re: mlx4 weird error "Failed to map EQ context memory" after update

From: Greg V <greg_at_unrelenting.technology>
Date: Sat, 17 Feb 2018 16:51:04 +0300
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 :)
Received on Sat Feb 17 2018 - 12:57:51 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC