mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: david@lang.hm
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: jesse.brandeburg@intel.com, jeffrey.t.kirsher@intel.com,
	bruce.w.allan@intel.com, john.ronciak@intel.com,
	auke-jan.h.kok@intel.com, davem@davemloft.net
Subject: wierd networking problem on 2.6.26 with e1000
Date: Fri, 18 Jul 2008 00:07:15 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0807172357390.6370@asgard> (raw)

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

             reply	other threads:[~2008-07-18  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  7:07 david [this message]
2008-07-18  7:12 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.10.0807172357390.6370@asgard \
    --to=david@lang.hm \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®