From: Ira Snyder <iws@ovro.caltech.edu>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
netdev@vger.kernel.org, Stephen Hemminger <shemminger@vyatta.com>,
Arnd Bergmann <arnd@arndb.de>,
Jan-Bernd Themann <THEMANN@de.ibm.com>
Subject: Re: [RFC v3] net: add PCINet driver
Date: Wed, 5 Nov 2008 15:17:44 -0800 [thread overview]
Message-ID: <20081105231744.GB17821@ovro.caltech.edu> (raw)
In-Reply-To: <20081105212225.GA17821@ovro.caltech.edu>
On Wed, Nov 05, 2008 at 01:22:25PM -0800, Ira Snyder wrote:
Despite my best efforts at testing this version, a bug slipped past.
There is some problem with this driver, nfsroot, and Linux routing. If
you do not apply the fix below, udp packets sent by the nfsroot code
have corrupted checksums after they get routed across the network to
another host.
If I boot both hosts to Linux via other means, the driver works fine
with no issues. It only happens for nfsroot.
If I run an nfs server on the PCINET_HOST computer, removing the
routing, it also works fine.
Remove the following line from pcinet_host.c and pcinet_fsl.c:
ndev->features |= NETIF_F_NO_CSUM; /* No checksum needed */
In case anyone knows offhand what might be causing this, my setup is as
follows:
cPCI Crate
|-------------------------|
| PCINET_FSL |
|-------------------------|
| ^ 10.0.0.2 |
| | |
| PCINet Driver Link here |
| | |
| v 10.0.0.1 |
|-------------------------|
| PCINET_HOST |
|-------------------------|
^ 192.168.17.14
|
Normal ethernet link here
|
v
|-------------------------|
| Ethernet switch |
|-------------------------|
^
|
Normal ethernet link here
|
v 192.168.17.59
|-------------------------|
| NFS Server |
|-------------------------|
Ira
next prev parent reply other threads:[~2008-11-05 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 21:22 [RFC v3] net: add PCINet driver Ira Snyder
2008-11-05 23:17 ` Ira Snyder [this message]
2010-03-31 4:46 ` Kumar Gala
2010-03-31 15:25 ` Ira W. Snyder
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=20081105231744.GB17821@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=THEMANN@de.ibm.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 NNTP newsgroup(s).