Andrei wrote:
> Did you try using ethereal or tcpdump to see what is going on the wire?
I ran ethereal on the NFS server and on a PC connected to the same hub as
the target board highlighted the problem. Many NFS READ REPLY messages from
the server were getting lost on their way to the target boa
On 7/25/06, Edward Jubenville wrote:
I am having trouble booting the kernel with a root file system over NFS.
> Once the kernel has mounted the file system, it cycles through this pair
> of
> messages, endlessly:
>
> nfs: server 192.168.0.39 not responding, still trying
> nfs: ser
Hi
> I am having trouble booting the kernel with a root file system over NFS.
> Once the kernel has mounted the file system, it cycles through this pair of
> messages, endlessly:
>
> nfs: server 192.168.0.39 not responding, still trying
> nfs: server 192.168.0.39 OK
We had the same
Hi Edward,
Did you try using ethereal or tcpdump to see what is going on the wire?
I doubt this is your case, but once I've seen a similar behaviour (different
board and CPU!) when an ethernet controller had small Rx FIFO and no DMA, and
the
driver was not able to read the first 1.5kB packet of
I am having trouble booting the kernel with a root file system over NFS.
Once the kernel has mounted the file system, it cycles through this pair of
messages, endlessly:
nfs: server 192.168.0.39 not responding, still trying
nfs: server 192.168.0.39 OK
I can't figure out if this is
