wierd networking problem on 2.6.26 with e1000

wierd networking problem on 2.6.26 with e1000

[david]

apologies for the poor report, I'll learn more tomorrow.

I've got a pair of boxes dual opteron dual-core with 16G ram LSI raid, and 
several quad E1000 cards. I had an emergancy requiring me to setup the 
boxes quickly for a new purpose, on one of them I left my old 2.6.22.1 32 
bit build, but on the other I tried a 2.6.26 64 bit build. both boxes have 
the same 32 bit userspace and are running heartbeat to move a VIP from one 
to the other.

when I logged into the 2.6.22.1 box and ssh'd over to the 2.6.26 box I had 
no communications problems at all, but if I moved the VIP (eth0:0) onto 
the 2.6.26 box and connected in to that I would occasionally see delays of 
a min or two where I lost all communications with the box. At the time 
this breakdown happened I was still connected in from the 2.6.22 box to 
the real IP of the second one with no problems, but attempts to connect to 
that real IP from other systems failed (unable to get an ARP response)

I will be able to post my configs tomorrow, but the version difference 
between the two kernels will limit the usability of that. any suggestions 
on other things I should do when I setup a new test?

David Lang

Re: wierd networking problem on 2.6.26 with e1000

[David Miller]

From: david@lang.hm
Date: Fri, 18 Jul 2008 00:07:15 -0700 (PDT)

David please report networking problems with at least netdev CC:'d, thanks.
I've added it this time.

> apologies for the poor report, I'll learn more tomorrow.
> 
> I've got a pair of boxes dual opteron dual-core with 16G ram LSI raid, and 
> several quad E1000 cards. I had an emergancy requiring me to setup the 
> boxes quickly for a new purpose, on one of them I left my old 2.6.22.1 32 
> bit build, but on the other I tried a 2.6.26 64 bit build. both boxes have 
> the same 32 bit userspace and are running heartbeat to move a VIP from one 
> to the other.
> 
> when I logged into the 2.6.22.1 box and ssh'd over to the 2.6.26 box I had 
> no communications problems at all, but if I moved the VIP (eth0:0) onto 
> the 2.6.26 box and connected in to that I would occasionally see delays of 
> a min or two where I lost all communications with the box. At the time 
> this breakdown happened I was still connected in from the 2.6.22 box to 
> the real IP of the second one with no problems, but attempts to connect to 
> that real IP from other systems failed (unable to get an ARP response)
> 
> I will be able to post my configs tomorrow, but the version difference 
> between the two kernels will limit the usability of that. any suggestions 
> on other things I should do when I setup a new test?
> 
> David Lang