netdev - RE: loop on reset adapter with ixgbe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <F6FB0E698C9B3143BDF729DF222866466FD88724@ORSMSX110.amr.corp.intel.com>
Date:	Wed, 20 Nov 2013 18:58:52 +0000
From:	"Skidmore, Donald C" <donald.c.skidmore@...el.com>
To:	William Dauchy <william@...di.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	"Keller, Jacob E" <jacob.e.keller@...el.com>,
	"Fastabend, John R" <john.r.fastabend@...el.com>,
	"Tantilov, Emil S" <emil.s.tantilov@...el.com>,
	"Potenza, Leonardo" <leonardo.potenza@...el.com>
Subject: RE: loop on reset adapter with ixgbe



> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-
> owner@...r.kernel.org] On Behalf Of William Dauchy
> Sent: Wednesday, November 20, 2013 10:25 AM
> To: netdev@...r.kernel.org
> Cc: Keller, Jacob E; Fastabend, John R; Tantilov, Emil S; Potenza, Leonardo
> Subject: loop on reset adapter with ixgbe
> 
> Hi,
> 
> On some machines with a network card named "Intel Corporation 82599EB
> 10-Gigabit SFI/SFP+"
> 
> At boot time, I'm getting an infinite loop showing these messages:
> 
> ixgbe 0000:03:00.0 eth0: initiating reset to clear Tx work after link loss ixgbe
> 0000:03:00.0 eth0: Reset adapter ixgbe 0000:03:00.0 eth0: detected SFP+: 3
> 
> ethtool info:
> driver: ixgbe
> version: 3.8.21-k
> firmware-version: 0x00000000
> 
> I'm using the last linux stable branch v3.10.x.
> 
> I need to unplug/plug the network/cable (a twinax cable) several times to
> stabilize the situation and get some network.
> I was wondering if I should consider this as a driver/firmware bug or if I
> should look for a physical issue (I changed the physical cable several times).
> Or do you need some more info to help understand this issue?
> 
> Best regards,
> --
> William

I also just noticed your firmware looks in correct.  What is the DevID for your device?  Likewise do you have another NIC and if so could you check it's firmware-version?

Thanks,
-Don Skidmore <donald.c.skidmore@...el.com>


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html