On Thu, Jun 7, 2018 at 1:19 PM, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > Hi, > > When booting my boards under recent linux-next, I see failures of systemd: > > [FAILED] Failed to start Flush Journal to Persistent Storage. > See 'systemctl status systemd-journal-flush.service' for details. > Starting Create Volatile Files and Directories... > [** ] A start job is running for Create V… [ 223.209289] nfs: > server 192.168.1.10 not responding, still trying > [ 223.209377] nfs: server 192.168.1.10 not responding, still trying > > Effectively the boards fails to boot. Example is here: > https://krzk.eu/#/builders/1/builds/2157 > > This was bisected to: > commit 37ac86c3a76c113619b7d9afe0251bbfc04cb80a > Author: Chuck Lever <chuck.lever@xxxxxxxxxx> > Date: Fri May 4 15:34:53 2018 -0400 > > SUNRPC: Initialize rpc_rqst outside of xprt->reserve_lock > > alloc_slot is a transport-specific op, but initializing an rpc_rqst > is common to all transports. In addition, the only part of initial- > izing an rpc_rqst that needs serialization is getting a fresh XID. > > Move rpc_rqst initialization to common code in preparation for > adding a transport-specific alloc_slot to xprtrdma. > > Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx> > Signed-off-by: Anna Schumaker <Anna.Schumaker@xxxxxxxxxx> > > > Bisect log attached. Full configuration: > 1. exynos_defconfig > 2. ARMv7, octa-core, Exynos5422 and Exynos4412 (Odroid XU3, U3 and others) > 3. NFSv4 client (from Raspberry Pi) > > Let me know if you need any more information. Ah, I forgot maybe the most important information in reproducment - client uses NFS root (NFSv4). Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
