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

[Greg V]

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?!
>
> 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 also make sure that /boot/modules does not contain anything 
> *mlx4* ?
Yeah, it did not contain that.