kernel-packages team mailing list archive

[Jorge Niedbalski <1507482@xxxxxxxxxxxxxxxxxx>]

@talat-b87

It seems to me that the link is up, I have no clue why the link is being
showed as failed.

Settings for eth7:
	Supported ports: [ ]
	Supported link modes:   1000baseT/Full 
	                        1000baseKX/Full 
	                        10000baseT/Full 
	                        10000baseKX4/Full 
	                        10000baseKR/Full 
	                        40000baseKR4/Full 
	                        40000baseCR4/Full 
	                        40000baseSR4/Full 
	                        40000baseLR4/Full 
	Supported pause frame use: No
	Supports auto-negotiation: No
	Advertised link modes:  1000baseT/Full 
	                        1000baseKX/Full 
	                        10000baseT/Full 
	                        10000baseKX4/Full 
	                        10000baseKR/Full 
	                        40000baseKR4/Full 
	                        40000baseCR4/Full 
	                        40000baseSR4/Full 
	                        40000baseLR4/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: No
	Speed: 56000Mb/s
	Duplex: Full
	Port: Other
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	Link detected: yes


[ 17.666714] mlx4_core 0000:08:00.0: mlx4_ib: Port 1 logical link is up

root@nova-compute:/home/ubuntu# ibstat
CA 'mlx4_0'
	CA type: MT4103
	Number of ports: 2
	Firmware version: 2.35.5100
	Hardware version: 0
	Node GUID: 0xe41d2d03000a1120
	System image GUID: 0xe41d2d03000a1123
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 56
		Base lid: 3
		LMC: 0
		SM lid: 2
		Capability mask: 0x02514868
		Port GUID: 0xe41d2d03000a1121
		Link layer: InfiniBand

@inaddy, Could you please copy this to vivid/trusty series?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507482

Title:
  ethtool self-test failed and creates a FW reset.

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On ConnectX3 device we try to run self-test and it’s failed, also seen
  that cause a FW reset.

  Steps to reproduce:

  
  ~# ethtool -t ens2
  The test result is FAIL
  The test extra info:
  Interrupt Test   -16
  Link Test        0
  Speed Test       0
  Register Test    0
  Loopback Test    0

  ~# dmesg
  [341548.619799] mlx4_core 0000:07:00.0: command 0x31 timed out (go bit not cleared)
  [341548.803801] mlx4_core 0000:07:00.0: command 0x49 timed out (go bit not cleared)
  [341548.803808] mlx4_core 0000:07:00.0: device is going to be reset
  [341549.816587] mlx4_core 0000:07:00.0: device was reset successfully
  [341549.823425] mlx4_en 0000:07:00.0: Internal error detected, restarting device

  ~# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="15.10 (Wily Werewolf)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Wily Werewolf (development branch)"
  VERSION_ID="15.10"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

  ~# uname -r
  4.2.0-7-generic

  ~# ethtool -i ens2
  driver: mlx4_en
  version: 2.2-1 (Feb 2014)
  firmware-version: 2.34.5000
  bus-info: 0000:07:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507482/+subscriptions