Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755385AbbBGEdt (ORCPT ); Fri, 6 Feb 2015 23:33:49 -0500 Received: from mail-vc0-f174.google.com ([209.85.220.174]:52310 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751453AbbBGEds (ORCPT ); Fri, 6 Feb 2015 23:33:48 -0500 MIME-Version: 1.0 In-Reply-To: <20150207043141.GA4394@wfg-t540p.sh.intel.com> References: <20150207024546.GA27323@wfg-t540p.sh.intel.com> <20150207043141.GA4394@wfg-t540p.sh.intel.com> Date: Fri, 6 Feb 2015 23:33:47 -0500 Message-ID: Subject: Re: [NFSv4.1] 6ae373394c4: kernel boot crash From: Trond Myklebust To: Fengguang Wu Cc: LKML , LKP Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2191 Lines: 63 On Fri, Feb 6, 2015 at 11:31 PM, Fengguang Wu wrote: > Hi Trond, > > On Fri, Feb 06, 2015 at 10:43:34PM -0500, Trond Myklebust wrote: >> On Fri, Feb 6, 2015 at 9:45 PM, Fengguang Wu wrote: >> > >> > Hi Trond, >> > >> > We noticed the below kernel crash on >> > >> > git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing >> > commit 6ae373394c4257bad562817aa60464ff7fe8f9c4 ("NFSv4.1: Ask for no delegation on OPEN if using O_DIRECT") >> > >> > >> > testbox/testcase/testparams: vm-vp-quantal-x86_64/boot/1 >> > >> > 0e3b137fbf0f4ab9 6ae373394c4257bad562817aa6 >> > ---------------- -------------------------- >> > fail:runs %reproduction fail:runs >> > | | | >> > :100 4% 2:46 dmesg.BUG:kernel_test_crashed >> > >> > The last dmesg lines before the kernel crash are >> > >> > [ 0.274266] NET: Registered protocol family 1 >> > [ 0.275236] RPC: Registered named UNIX socket transport module. >> > [ 0.276123] RPC: Registered udp transport module. >> > [ 0.276860] RPC: Registered tcp transport module. >> > [ 0.277617] RPC: Registered tcp NFSv4.1 backchannel transport module >> > >> > Thanks, >> > Fengguang >> >> >> Hi Fengguang, >> >> I'm trying to reproduce this issue, but so far no luck. Do you have >> any details on the test itself that you could share with me? > > It looks like a false report, sorry! The real crash dmesg is much > longer and it ends here: > > [ 14.605487] i6300esb: Unexpected close, not stopping watchdog! > > Which is not relevant to the NFS change at all. > > The dmesg I looked at happen to be truncated (perhaps by email server) > exactly at a NFS line, which treats me to believe it's a good bisect. > > Cheers, > Fengguang Phew. So I'm off the hook then. :-) -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@primarydata.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/