From: "Christopher Friesen" <cfriesen@nortel.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sf.net
Subject: Re: help with e1000 issue?
Date: Thu, 19 Jan 2006 10:48:01 -0600 [thread overview]
Message-ID: <43CFC2C1.2080308@nortel.com> (raw)
In-Reply-To: <4807377b0601181316w2ac0fb0dod976e456816331ae@mail.gmail.com>
Jesse Brandeburg wrote:
> On 1/18/06, Christopher Friesen <cfriesen@nortel.com> wrote:
>>So, somehow we're getting into a state where we can't receive packets,
>>and we're never getting out of that state.
> Are you sure that you're able to transmit and you aren't just handing
> it to the hardware and it never gets out? tcpdump on a remote machine
> would verify.
I haven't tried the new driver yet, so this is still with the old driver
(had the hung machine still up from yesterday).
It looks like tx is working--we see the packets on the other machines on
the network. I tested unicast and broadcast, and both seem to be working.
I tried a broadcast ping to the whole subnet. For that one the icmp
packet goes out, then we see ARPs from everyone on the subnet trying to
get the MAC address of the machine with eth issues.
On the machine with hung ethernet:
root@172.24.101.12:/root> ping -b 172.25.0.0
WARNING: pinging broadcast address
PING 172.25.0.0 (172.25.0.0) 56(84) bytes of data.
64 bytes from 172.25.101.12: icmp_seq=1 ttl=64 time=0.041 ms
64 bytes from 172.25.101.12: icmp_seq=2 ttl=64 time=0.046 ms
On the other machine:
root@10.102.92.28:/root> tcpdump -n -i bond1 host 172.25.101.12
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond1, link-type EN10MB (Ethernet), capture size 96 bytes
01:51:27.275594 IP 172.25.101.12 > 172.25.0.0: icmp 64: echo request seq 1
01:51:27.275748 arp who-has 172.25.101.12 tell 172.25.80.0
01:51:27.275824 arp who-has 172.25.101.12 tell 172.25.101.16
01:51:27.276248 arp who-has 172.25.101.12 tell 172.25.101.13
01:51:27.276373 arp who-has 172.25.101.12 tell 172.25.101.1
01:51:28.275674 arp who-has 172.25.101.12 tell 172.25.101.16
01:51:28.276258 arp who-has 172.25.101.12 tell 172.25.101.1
01:51:28.278017 arp who-has 172.25.101.12 tell 172.25.80.0
01:51:28.278260 IP 172.25.101.12 > 172.25.0.0: icmp 64: echo request seq 2
01:51:28.278388 arp who-has 172.25.101.12 tell 172.25.101.13
01:51:29.275520 arp who-has 172.25.101.12 tell 172.25.101.16
01:51:29.276018 arp who-has 172.25.101.12 tell 172.25.101.1
01:51:29.280032 IP 172.25.101.12 > 172.25.0.0: icmp 64: echo request seq 3
01:51:29.280277 arp who-has 172.25.101.12 tell 172.25.80.0
01:51:29.280524 arp who-has 172.25.101.12 tell 172.25.101.13
Chris
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
parent reply other threads:[~2006-01-19 16:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4807377b0601181316w2ac0fb0dod976e456816331ae@mail.gmail.com>]
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=43CFC2C1.2080308@nortel.com \
--to=cfriesen@nortel.com \
--cc=e1000-devel@lists.sf.net \
--cc=jesse.brandeburg@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).