From: RandyLin@mxic.com.tw
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] EB40LS ping_test problem
Date: Fri, 19 Sep 2003 01:57:00 -0000 [thread overview]
Message-ID: <OF1BABD18E.E1C16BE8-ON48256DA6.0008D20F-48256DA6.000A5D32@MXIC.COM.TW> (raw)
Andrew Lunn
<andrew@lunn.ch> 收件人： RandyLin@mxic.com.tw
寄件人： 副本抄送： ecos-discuss@sources.redhat.com
ecos-discuss-owner@sources 主旨： Re: [ECOS] EB40LS ping_test problem
.redhat.com
2003/09/17 05:43 PM
> I use ethernal to capture the packets.
> EB40LS first send ARP packet, and Linux reply.
> But EB40LS seems don't receive the reply packets, it resend the ARP
> packets.
> Where may be the problem??
Probably the receive part of the driver. Check to see if you are
getting interrupts when it receives a packet. Then check what actually
happens during the receive.
Andrew
I enable the The CYGDBG_IO_ETH_DRIVERS_DEBUG,and set
CYGDBG_IO_ETH_DRIVERS_DEBUG_VERBOSITY=2,
I got the following message:
Q1: In the first two packets, why it sends arp to 192.9.207.130?
The target is 192.9.207.130!
Q2: Sending bytes is 42, who will do the padding to 60?
Because Linux got 60 bytes of arp.
Q3: EB40LS got arp reply, but it don't send the icmp(ping),
it's just sending the arp out.
=======================================================
hw_addr: 08:88:12:34:56:78
client IP: 192.9.207.130
my IP: 192.9.207.130
server IP: 192.9.207.120
gateway IP: 192.9.207.254
options:
subnet mask: 255.255.255.0
IP broadcast: 192.9.207.255
gateway: 192.9.207.254
Sending 42 bytes
xmit 42 bytes at 20f8c56 sg[1]
020F8C56: FF FF FF FF FF FF 08 88 12 34 56 78 08 06 00 01
|.........4Vx....|
020F8C66: 08 00 06 04 00 01 08 88 12 34 56 78 C0 09 CF 82
|.........4Vx....|
020F8C76: 00 00 00 00 00 00 C0 09 CF 82 |..........
|
Sending 42 bytes
xmit 42 bytes at 20f8bd6 sg[1]
020F8BD6: FF FF FF FF FF FF 08 88 12 34 56 78 08 06 00 01
|.........4Vx....|
020F8BE6: 08 00 06 04 00 01 08 88 12 34 56 78 C0 09 CF 82
|.........4Vx....|
020F8BF6: 00 00 00 00 00 00 C0 09 CF 82 |..........
|
PING server 192.9.207.120
Sending 42 bytes
xmit 42 bytes at 20f8a56 sg[1]
020F8A56: FF FF FF FF FF FF 08 88 12 34 56 78 08 06 00 01
|.........4Vx....|
020F8A66: 08 00 06 04 00 01 08 88 12 34 56 78 C0 09 CF 82
|.........4Vx....|
020F8A76: 00 00 00 00 00 00 C0 09 CF 78 |.........x
|
RxEvent - stat: 504, len: 60
rx 14 bytes at 2128f74 sg[0]
02128F74: 08 88 12 34 56 78 00 50 BF 43 DD AC 08 06 |...4Vx.P.C....
|
rx 46 bytes at 20f89ac sg[1]
020F89AC: 00 01 08 00 06 04 00 02 00 50 BF 43 DD AC C0 09
|.........P.C....|
020F89BC: CF 78 08 88 12 34 56 78 C0 09 CF 82 11 0A 11 75
|.x...4Vx.......u|
020F89CC: C0 09 CF 78 00 8A 00 C3 00 00 20 46 43 45 |...x...... FCE
|
Tx event: 8
recvfrom: Operation timed out
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-09-19 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 1:57 RandyLin [this message]
2003-09-20 20:52 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2003-09-24 10:03 RandyLin
2003-09-22 7:12 RandyLin
2003-09-22 9:27 ` Andrew Lunn
2003-09-17 9:18 RandyLin
2003-09-17 9:43 ` Andrew Lunn
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=OF1BABD18E.E1C16BE8-ON48256DA6.0008D20F-48256DA6.000A5D32@MXIC.COM.TW \
--to=randylin@mxic.com.tw \
--cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).