Quantcast
Channel: Mellanox Interconnect Community: Message List
Viewing all articles
Browse latest Browse all 6148

Re: Re: "Missing UAR" kernel error on boot, ConnectX-3 not detected by the OS

$
0
0

i am having this problem too.

 

this is the message from my syslog:

Oct  2 05:59:56 fr-dev11 kernel: [  670.201294] mlx4_core: Mellanox ConnectX core driver v1.1 (Oct  2 2014)

Oct  2 05:59:56 fr-dev11 kernel: [  670.201319] mlx4_core: Initializing 0000:04:00.0

Oct  2 05:59:56 fr-dev11 kernel: [  670.201465] mlx4_core 0000:04:00.0: Missing UAR, aborting.

 

This is the mlxfwmanager knows:

Querying Mellanox devices firmware ...

 

Device #1:

----------

 

 

  Device Type:      ConnectX3

  Part Number:      0W0RM9_0Y3KKR

  Description:      ConnectX-3 Dual Port 10GbE SFP+ Adapter card for Dell

  PSID:             DEL0A80000023

  PCI Device Name:  /dev/mst/mt4099_pci_cr0

  Port1 MAC:        f452143d2ef0

  Port2 MAC:        f452143d2ef1

  Versions:         Current        Available    

     FW             2.32.5100      N/A          

     PXE            3.4.0306       N/A          

     UEFI           12.5.0022      N/A          

 

 

  Status:           No matching image found

This is my kernel:

Linux 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

 

This is what lshw knows:

 

  *-network UNCLAIMED

       description: Ethernet controller

       product: MT27500 Family [ConnectX-3]

       vendor: Mellanox Technologies

       physical id: 0

       bus info: pci@0000:04:00.0

       version: 00

       width: 64 bits

       clock: 33MHz

       capabilities: pm vpd msix pciexpress cap_list

       configuration: latency=0

       resources: memory:da700000-da7fffff memory:d9800000-d98fffff

 

This is what lspci knows:

 

04:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3]


Viewing all articles
Browse latest Browse all 6148

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>