> Hello John,
> 
> Not much actually, just regular cable modem network traffic (was not
> even utilizing it heavily), vnstat below:
> 
>   eth2
> 18:11
>    ^                                                              r
>    |                                                  r           r
>    |                                                  r           r
>    |                                                  r           r
>    |  r                                               r  r        r
>    |  r                                               r  r        r  r
>    |  r                                               r  r        r  r
>    |  r                          r                    r  r  r  r  r  r
>    |  r                          r                    r  r  r  r  r  r
> r
>    |  r                          r                    r  r  r  r  r  r
> r
>   -+-------------------------------------------------------------------
> -------->
>    |  19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
> 17 18
> 
>   h  rx (KiB)   tx (KiB)      h  rx (KiB)   tx (KiB)      h  rx (KiB)
> tx (KiB)
> 19      89730       8838    03      11249        620    11     126496
> 9383
> 20      10972        596    04      43551       1729    12      86326
> 6513
> 21      11489        611    05      12159        699    13      47805
> 3863
> 22      12073        630    06      12080        712    14      52322
> 4577
> 23      12153        654    07      11894        710    15     135715
> 8618
> 00      11536        594    08       7392        396    16      75680
> 6181
> 01      11159        560    09          0          0    17      33817
> 3213
> 02      11564        575    10        759         51    18       4315
> 190
> 
> The most recent crash was at 16:33.
> 
> The system crashed earlier too but I had X running so I couldn't get a
> screenshot, there is no serial port on this machine and netconsole does
> not work with this type of failure.
> 
> It is unfortunately not reproducible, is there any debugging options
> that you would recommend I can enable that will expose this bug? I'm up
> for anything at this point.
> 
> All of this may have started when I added a 4-port Intel NIC:
> http://www.intel.com/Assets/PDF/prodbrief/323205.pdf
> 
> NIC = Intel Ethernet I340 Server Adatper
> 
> But this is just a guess..
> 
> Justin.
You still didn't tell us what eth interface is on which HW.  We need to know 
that.  Do an 'ethtool -i eth2' and the same for each of the other interfaces in 
the system.  The igb driver that is used on the NIC described above is in high 
use without people reporting this error.

Cheers,
John



------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to