Hello e1000 Developers,
I have a RHEL 5.3 (2.6.18-128.el5, driver e1000e-1.0.2.5 built) machine,
with two network adapters, which I'm trying to get to Team/Bond - an (i)
Intel PRO/1000 PT Server single-socket, and (ii) Intel PRO/1000 GT Desktop
single-socket. Individually, the cards work fine. Also, their Team (mode 1)
setup is fine, and logs show Teaming to be working.
However, Teaming does not actually work, and the issue appears to be very
close, indeed the same, as that described in
https://bugzilla.redhat.com/show_bug.cgi?id=483034 (Clsoed Duplicate). In
short, when a fault occurs on the active Team member (eth0), the switch
occurs, but the machine is no longer pingable/accessible, until eth0
eventually becomes the active member. Again, the bonding/teaming log shows
the correct bonding status on the cards and bond/team at all times.
I upgraded the RHEL box from 2.6.18-128.el5 to 2.6.18-164.el5 (so, RHEL
5.4), but the issue still occured.
So, I tried rebuilding the e1000e-1.0.2.5 src (previously built for
2.6.18-128.el5) to match the 2.6.18-164.el5 kernel. However, this resulted
in a build error -
".../e1000e-1.0.2.5/src/kcompat.h:1505: error: redefinition of 'struct
napi_struct'
Googleing this build error, I found that it's been commented on in this
mailing list recently (
http://www.mail-archive.com/[email protected]/msg01883.html),
though for a different build.
If you'd care to comment on the above path to get Teaming/Bonding working,
this would be much appreciated.
Regards,
Ed
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
