mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [NFSv4.1] 6ae373394c4: kernel boot crash
Date: Fri, 6 Feb 2015 20:31:41 -0800	[thread overview]
Message-ID: <20150207043141.GA4394@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <CAHQdGtSzYoeKN+Tc1-7m7m00Z2cd4iGAB-L65__1UC5uzs7CvQ@mail.gmail.com>

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 <fengguang.wu@intel.com> 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

  reply	other threads:[~2015-02-07  4:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07  2:45 Fengguang Wu
2015-02-07  3:43 ` Trond Myklebust
2015-02-07  4:31   ` Fengguang Wu [this message]
2015-02-07  4:33     ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150207043141.GA4394@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=trond.myklebust@primarydata.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®