From: Martyn Welch <martyn.welch@ge.com>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>, netdev@vger.kernel.org
Cc: Anton Vorontsov <avorontsov@ru.mvista.com>,
Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
davem@davemloft.net
Subject: Gianfar driver failing on MPC8641D based board
Date: Fri, 05 Feb 2010 14:00:40 +0000 [thread overview]
Message-ID: <4B6C2488.3060403@ge.com> (raw)
I have recently attempted to boot an 8641D based board from an NFS root.
The boot process grinds to a halt not long after the first access of the
NFS root and I receive multiple "nfs: server 192.168.0.1 not responding,
still trying" messages. Wireshark suggests that there is no further
traffic from this board at this point on. The NFS server seems to
eventually try sending duplicate packets it's already sent, which
results in "nfs: server 192.168.0.1 OK" messages, but the "not
responding" messages resume with no further traffic from the board.
I am able to boot to a ramdisk fine and the network seems to work -
though I haven't really pushed the interface from it.
I have attempted to git bisect, though I wasn't able to get much further
than discovering the problem was introduced in the 2.6.33 merge window -
at which point the gianfar network driver fails to compile (I have tried
to git bisect skip many, many times to no avail).
NFS booting fails for this board on todays linux-next, the master branch
of Kumar's PPC tree and the head of the main tree. I have also been able
to NFS boot from a random x86 based board that I have, using the head of
the main tree and the linux-next tree.
Copying the gianfar drivers from 2.6.32 into the head of the main tree
restores the correct behaviour and I'm able to NFS boot. I have heard
from others that the latest drivers work on 83xx and 85xx based boards,
but it seems to be broken on at least the 8641D.
I can see there has been a fair amount of work done on the gianfar
driver, I assume that this is a bug introduced by the multiple queue
support, but I'm way out of my depth on this.
I'm also off for the next week - so if I'm quiet, it'll be because of that.
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square, Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
next reply other threads:[~2010-02-05 13:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:00 Martyn Welch [this message]
2010-02-25 10:31 ` Gianfar driver failing on MPC8641D based board Martyn Welch
2010-02-25 16:46 ` Martyn Welch
2010-02-25 16:46 ` Martyn Welch
2010-02-25 16:51 ` Anton Vorontsov
2010-02-25 16:51 ` Anton Vorontsov
2010-02-25 17:49 ` Anton Vorontsov
2010-02-25 17:49 ` Anton Vorontsov
2010-02-26 0:53 ` Paul Gortmaker
2010-02-26 0:53 ` Paul Gortmaker
2010-02-26 3:14 ` Anton Vorontsov
2010-02-26 3:14 ` Anton Vorontsov
2010-02-26 4:58 ` Kumar Gopalpet-B05799
2010-02-26 4:58 ` Kumar Gopalpet-B05799
2010-02-26 12:06 ` Martyn Welch
2010-02-26 12:06 ` Martyn Welch
2010-02-26 14:35 ` Anton Vorontsov
2010-02-26 14:35 ` Anton Vorontsov
2010-02-26 14:52 ` Paul Gortmaker
2010-02-26 14:52 ` Paul Gortmaker
2010-02-26 15:18 ` Martyn Welch
2010-02-26 15:18 ` Martyn Welch
2010-02-26 15:34 ` Martyn Welch
2010-02-26 16:10 ` Anton Vorontsov
2010-02-26 16:27 ` Paul Gortmaker
2010-02-26 16:27 ` Paul Gortmaker
2010-02-26 21:38 ` Anton Vorontsov
2010-02-26 21:38 ` Anton Vorontsov
2010-02-26 22:12 ` Paul Gortmaker
2010-02-26 22:12 ` Paul Gortmaker
2010-02-27 5:35 ` Kumar Gopalpet-B05799
2010-02-27 5:35 ` Kumar Gopalpet-B05799
2010-03-02 14:02 ` Anton Vorontsov
2010-03-02 14:02 ` Anton Vorontsov
2010-03-01 13:07 ` Martyn Welch
2010-03-01 13:07 ` Martyn Welch
2010-02-26 11:51 ` Martyn Welch
2010-02-26 11:51 ` Martyn Welch
2010-02-25 18:27 ` Kumar Gala
2010-02-25 18:27 ` Kumar Gala
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=4B6C2488.3060403@ge.com \
--to=martyn.welch@ge.com \
--cc=Sandeep.Kumar@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.