From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MAC driver issues
Date: Tue, 05 Sep 2006 09:33:04 +0100 [thread overview]
Message-ID: <44FD3640.30208@cambridgebroadband.com> (raw)
In-Reply-To: <44FCA93E.1000009@dlasys.net>
Hi David,
I think in order to get any help from this list you need to be more specific
about how this problem relates to PowerPCs.
You also need to say exactly what "never gets handed off to the ARP protocol"
means.
FWIW, in my experience the hardware independent parts of the networking stack are
very stable and the problem is almost always with the drivers, or with the IP
configuration (e.g. two interfaces on the same subnet).
Alex
David H. Lynch Jr. wrote:
> I am trying to get a network driver working.
>
> It sends - I can capture the output with Etherreal and it looks good.
> It receives - I can dump the received packets when the come in and they
> look ok to me.
>
>
> BUT,
> If I try to ping another host, first Linux sends and ARP broadcast,
> the appropriate client sends an ARP response.
> Etherreal is happy with both.
> My driver gets the response - The driver says the packet lenght is
> 64 bytes, which includes something like 14 bytes of padding at the end.
> But the actual packet looks perfect exactly like what etherreal says
> it should (and what I get when I capture a received ARP packet in
> another driver).
> At the end of the recive interrupt the skb is passed to Linux with
> the netif_rc(ndev) function. This returns SUCCESS.
>
> However, the paket never gets handed of to the ARP protocol - I put
> some debugging in there and I never see it, while if I switch to a
> different NIC
> driver nearly the identical ARP packet gets processed by arp inside
> Linux.
>
> I have tried to chase this down, but I can't follow what is going
> on inside of all the /net/core/dev.c etc.
>
> Has anyone seen something similar to this ?
>
> Does anyone have a clue where I can find some info on trying to
> follow something through netif_rx to see where things are going off the
> rails ?
>
>
>
next prev parent reply other threads:[~2006-09-05 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 7:26 booting Linux in Linux using kexec tools Reddy Suneel-ASR125
2006-09-04 21:39 ` Guennadi Liakhovetski
2006-09-04 22:31 ` MAC driver issues David H. Lynch Jr.
2006-09-05 8:33 ` Alex Zeffertt [this message]
2006-09-06 6:25 ` MAC driver issue David H. Lynch Jr.
2006-09-06 8:25 ` Alex Zeffertt
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=44FD3640.30208@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=dhlii@dlasys.net \
--cc=linuxppc-embedded@ozlabs.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).