From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 1FA32E0096A; Mon, 15 Jun 2015 06:43:13 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [192.36.1.252 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mx-3.enea.com (sestofw01.enea.se [192.36.1.252]) by yocto-www.yoctoproject.org (Postfix) with SMTP id 3E875E00496 for ; Mon, 15 Jun 2015 06:43:07 -0700 (PDT) Received: from [192.168.14.77] (192.168.14.77) by smtp.enea.com (172.21.1.209) with Microsoft SMTP Server id 14.3.224.2; Mon, 15 Jun 2015 15:43:05 +0200 Message-ID: <557ED669.4090203@enea.com> Date: Mon, 15 Jun 2015 16:43:05 +0300 From: Liviu Gheorghisan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "meta-freescale@yoctoproject.org" X-Originating-IP: [192.168.14.77] Subject: [meta-fsl-ppc] NFS boot problem on p2041rdb with kernel from meta-fsl-ppc @ dizzy. X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2015 13:43:13 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Hello, I have a problem booting over NFS the p2041rdb board with the kernel from meta-fsl-ppc on dizzy branch (version 3.12, although it's the same kernel revision on fido and master branches as well): URI: git://git.freescale.com/ppc/sdk/linux.git REV: 6619b8b55796cdf0cec04b66a71288edd3057229 After the p2041rdb board boots I can login successfully, but after a few seconds I see this: nfs: server X.Y.Z.W not responding, still trying ... nfs: server X.Y.Z.W not responding, still trying ... ...over and over again, during which the board is frozen, and only a reset fixes it. This problem only reproduces if the rootfs image is big enough (let's say more than 4.5GB), otherwise NFS boot works OK. I boot with these bootargs: $> setenv bootargs 'root=/dev/nfs rw nfsroot=X.Y.Z.W:/unix/linux_rootfs ip=dhcp console=ttyS0,115200 memmap=16M$0xf7000000 mem=4080M max_addr=f6ffffff' This is not a problem related to the NFS server that I'm using since I use that server for a lot of other boards/mounts - all working fine. Network connectivity is OK at all times, and there is no firewall between the board and the NFS server. Personally I suspect this is a problem in the SunRPC client (NFS works over RPC) from kernel/net/sunrpc/clnt.c regarding the time-out handling. Do you have any idea or suggestion? Thanks, -- Liviu Gheorghisan Software Engineer http://www.enea.com