Well, that's it for now anyway...

...
Power cycle is required to complete the update process.
Tool execution completed with the following status: All operations 
completed successfully

The card doesn't even appear in "lspci" anymore... :/
I used a Win7 to flash it since a co-worker already broke one when 
flashing via Linux. No idea how to unbrick it.


On 2015-08-27 01:25, Fujinaka, Todd wrote:
> Attachments don't work on this mailing list (though they may have
> gotten to Greg). Please file a bug on e1000.sourceforge.net and attach
> the files there.
> 
> Todd Fujinaka
> Software Application Engineer
> Networking Division (ND)
> Intel Corporation
> todd.fujin...@intel.com
> (503) 712-4565
> 
> -----Original Message-----
> From: Christian Ruppert [mailto:id...@qasl.de]
> Sent: Wednesday, August 26, 2015 10:24 AM
> To: Rose, Gregory V
> Cc: e1000-de...@lists.sf.net
> Subject: Re: [E1000-devel] X710 / i40e interface resets
> 
> On 2015-08-26 01:19, Rose, Gregory V wrote:
>>> -----Original Message-----
>>> From: Christian Ruppert [mailto:id...@qasl.de]
>>> Sent: Friday, August 21, 2015 7:06 AM
>>> To: Rose, Gregory V
>>> Cc: e1000-de...@lists.sf.net
>>> Subject: RE: [E1000-devel] X710 / i40e interface resets
>>> 
>>> On 2015-07-28 18:51, Rose, Gregory V wrote:
>>> >> -----Original Message-----
>>> >> From: Christian Ruppert [mailto:id...@qasl.de]
>>> >> Sent: Tuesday, July 28, 2015 5:43 AM
>>> >> To: Rose, Gregory V
>>> >> Cc: e1000-de...@lists.sf.net
>>> >> Subject: RE: [E1000-devel] X710 / i40e interface resets
>>> >>
>> 
>> [snip]
>> 
>>> > I've been told that the Tx driver issue detected message is due to
>>> > a MDD (Malicious Driver Detection) event.  We need to find out what
>>> > is causing that so if you could please send me your system log and
>>> > the output of ethtool <intf> and ethtool -i <intf> perhaps I can
>>> > see what might be occurring.  If not then we'll have to debug further.
>>> 
>>> See the initial Mail for ethtool -k and so on. Also:
>>> # ethtool eth0
>>> Settings for eth0:
>>>     Supported ports: [ FIBRE ]
>>>     Supported link modes:   1000baseT/Full
>>>                             10000baseT/Full
>>>     Supported pause frame use: Symmetric
>>>     Supports auto-negotiation: No
>>>     Advertised link modes:  1000baseT/Full
>>>                             10000baseT/Full
>>>     Advertised pause frame use: No
>>>     Advertised auto-negotiation: No
>>>     Speed: 10000Mb/s
>>>     Duplex: Full
>>>     Port: FIBRE
>>>     PHYAD: 0
>>>     Transceiver: external
>>>     Auto-negotiation: off
>>>     Supports Wake-on: d
>>>     Wake-on: d
>>>     Current message level: 0x0000000f (15)
>>>                            drv probe link timer
>>>     Link detected: yes
>>> # ethtool -i eth0
>>> driver: i40e
>>> version: 1.2.48
>>> firmware-version: f4.33.31377 a1.2 n4.42 e191b
>>> bus-info: 0000:02:00.0
>>> supports-statistics: yes
>>> supports-test: yes
>>> supports-eeprom-access: yes
>>> supports-register-dump: yes
>>> supports-priv-flags: yes
>> 
>> I also need the output of 'dmesg' - and I need to figure out how to
>> determine what specific MDD event is occurring.  I'll get back to you
>> with instructions on how to do that when I get the system log from
>> you.
> 
> See the attached file. It's a dmesg from boot + some minutes.
> I'll upgrade the card's firmware tomorrow I guess and try out the new
> drivers btw.
> 
>> 
>> Thanks,
>> 
>> - Greg
> 
> --
> Regards,
> Christian Ruppert

-- 
Regards,
Christian Ruppert

------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to