From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758000AbcHCPOl (ORCPT ); Wed, 3 Aug 2016 11:14:41 -0400 Received: from arroyo.ext.ti.com ([198.47.19.12]:46695 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757746AbcHCPOg (ORCPT ); Wed, 3 Aug 2016 11:14:36 -0400 Subject: Re: Kernel NFS boot failure To: Vladimir Murzin , netdev References: <674e6841-d2c5-ccae-6633-a699e848e6d2@ti.com> <57A1DE28.7020604@arm.com> CC: "linux-omap@vger.kernel.org" , Sekhar Nori , linux-arm , open list From: Grygorii Strashko Message-ID: Date: Wed, 3 Aug 2016 18:04:40 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <57A1DE28.7020604@arm.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vladimir, On 08/03/2016 03:06 PM, Vladimir Murzin wrote: > On 03/08/16 12:41, Grygorii Strashko wrote: >> We observe Kernel boot failure while running NFS boot stress test (1000 iterations): >> - Linux version 4.7.0 I'd like to pay your attention that this issue also reproducible with Kernel 4.7.0! The same can be seen from the log I've provided in first e-mail: [ 0.000000] Linux version 4.7.0 (lcpdbld@dflsdit-build06.dal.design.ti.com) (gcc version 4.9.3 20150413 (prerelease) (Linaro GCC 4.9-2015.05) ) #1 SMP Fri Jul 29 17:41:27 CDT 2016 I've not run the test with current master at it's not been tagged yet. >> - am335x-evm (TI AM335x EVM) >> - failure rate 10-20 times per test. >> Originally this issue was reproduced using TI Kernel 4.4 >> ( git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git, branch: ti-linux-4.4.y) >> on both am335x-evm and am57xx-beagle-x15(am57xx-evm) platforms. >> This issues has not been reproduced with TI Kernel 4.1 before. >> >> The SysRq shows that system stuck in nfs_fs_mount() >> >> [ 207.904632] [] (schedule) from [] (rpc_wait_bit_killable+0x2c/0xd8) >> [ 207.912996] [] (rpc_wait_bit_killable) from [] (__wait_on_bit+0x84/0xc0) >> [ 207.921812] [] (__wait_on_bit) from [] (out_of_line_wait_on_bit+0x64/0x70) >> [ 207.930810] [] (out_of_line_wait_on_bit) from [] (__rpc_execute+0x18c/0x544) >> [ 207.939988] [] (__rpc_execute) from [] (rpc_run_task+0x13c/0x158) >> [ 207.948166] [] (rpc_run_task) from [] (rpc_call_sync+0x44/0xc4) >> [ 207.956163] [] (rpc_call_sync) from [] (rpc_ping+0x48/0x68) >> [ 207.963796] [] (rpc_ping) from [] (rpc_create_xprt+0xec/0x164) >> [ 207.971702] [] (rpc_create_xprt) from [] (rpc_create+0xf0/0x1a0) >> [ 207.979794] [] (rpc_create) from [] (nfs_create_rpc_client+0xd4/0xec) >> [ 207.988338] [] (nfs_create_rpc_client) from [] (nfs_init_client+0x20/0x78) >> [ 207.997332] [] (nfs_init_client) from [] (nfs_create_server+0xa0/0x3bc) >> [ 208.006057] [] (nfs_create_server) from [] (nfs3_create_server+0x8/0x20) >> [ 208.014879] [] (nfs3_create_server) from [] (nfs_try_mount+0xc4/0x1f0) >> [ 208.023513] [] (nfs_try_mount) from [] (nfs_fs_mount+0x290/0x910) >> [ 208.031702] [] (nfs_fs_mount) from [] (mount_fs+0x44/0x168) >> >> Has anyone else seen this issue? >> >> I'd be appreciated for any help or advice related to this issue? > > I did not look at details, but because it is 4.4 and __wait_on_bit > showed up you might want to look at [1] > > [1] https://lkml.org/lkml/2015/11/20/472 Thanks. I'll take a look. -- regards, -grygorii