From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by ozlabs.org (Postfix) with ESMTP id 7375A67B5A for ; Wed, 26 Jul 2006 19:53:42 +1000 (EST) Received: by nf-out-0910.google.com with SMTP id c2so566185nfe for ; Wed, 26 Jul 2006 02:53:41 -0700 (PDT) Message-ID: Date: Wed, 26 Jul 2006 12:52:00 +0300 From: "Kalle Pokki" Sender: kallepokki@gmail.com To: "Edward Jubenville" Subject: Re: Slow boot with NFS, server not responding In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_218914_27132372.1153907520232" References: Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_218914_27132372.1153907520232 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: server 192.168.0.39 OK Try connecting to an old half-duplex hub instead of a full-duplex switch to see if it works. Perhaps the duplex setting is not consistent between the network driver and PHY. I have a board with exactly the same symptoms, but I've not yet had the time to look into this. However using the old hub provided a temporary "fix"... ------=_Part_218914_27132372.1153907520232 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/25/06, Edward Jubenville <edjubenville@adelphia.net> 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: server 192.168.0.39 OK

Try connecting to an old half-duplex hub instead of a full-duplex switch to see if it works. Perhaps the duplex setting is not consistent between the network driver and PHY.

I have a board with exactly the same symptoms, but I've not yet had the time to look into this. However using the old hub provided a temporary "fix"...



------=_Part_218914_27132372.1153907520232--