From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Sukadev Bhattiprolu" <sukadev@us.ibm.com>
Cc: "Auke Kok" <auke-jan.h.kok@intel.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Network problem with 2.6.18-mm1 ?
Date: Thu, 28 Sep 2006 14:10:02 -0700 [thread overview]
Message-ID: <4807377b0609281410p28d445c8mc32e7d2cb71221ab@mail.gmail.com> (raw)
In-Reply-To: <20060928185222.GB3352@us.ibm.com>
On 9/28/06, Sukadev Bhattiprolu <sukadev@us.ibm.com> wrote:
> Thanks. See below for additional info
>
> Auke Kok [auke-jan.h.kok@intel.com] wrote:
> | Sukadev Bhattiprolu wrote:
> | >
> | >I am unable to get networking to work with 2.6.18-mm1 on my system.
> | >
> | >But 2.6.18 kernel on same system works fine. Here is some info about
> | >the system/debug attempts. Attached are the lspci output and config.
> | >
> | >Appreciate any help. Please let me know if you need more info.
It seems you're having interrupt delivery problems or interrupts are
getting lost.
rx_missed_errors indicates frames that were dropped due to the e1000
adapter's fifo getting full and over flowing.
> rx_no_buffer_count: 310
> rx_missed_errors: 5865
rx_no_buffer_count indicates that the driver didn't return buffers to
the hardware soon enough, but the hardware was able to store the
packet (at the time of reception) in the fifo to try again.
Both these indicate to me that there is something wrong with
interrupts. Maybe interrupt sharing
can you possibly try a back to back connection with another linux box
and run tcpdump on both ends then ping? it will tell us if traffic is
truely getting out and coming in okay.
also please send output of lspci -vv and cat /proc/interrupts
Jesse
next prev parent reply other threads:[~2006-09-28 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 1:37 Sukadev Bhattiprolu
2006-09-28 2:02 ` Auke Kok
2006-09-28 18:52 ` Sukadev Bhattiprolu
2006-09-28 21:10 ` Jesse Brandeburg [this message]
2006-09-29 0:52 ` Sukadev Bhattiprolu
2006-09-29 18:08 ` Jesse Brandeburg
2006-09-29 23:30 ` Eric W. Biederman
2006-10-02 23:17 ` Badari Pulavarty
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=4807377b0609281410p28d445c8mc32e7d2cb71221ab@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sukadev@us.ibm.com \
/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®