> >It occurs in bursts, with phases in which this issue does not show up in
> >between. However, in this case it showed up right after booting into the
> >kernel with the updated driver.
>
> So are you saying that tx hang did occur right after boot? And then you get
> link flap messages?
> When you have this issue, does all of the interfaces are connected?
> I need more info, please send lspci -vvv and full dmesg log after issue
> occurs.
Right after boot into the kernel with the new driver I see eth2 going
UP and DOWN for some time, see the attached dmesg output from my
previous post. There now is no Unit Hang in particular.
I have attached hw.tar.gz, which also contains the lspci output.
/holger
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
