Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: panics related to nfit_test?
Date: Fri, 7 Apr 2017 16:28:57 -0400	[thread overview]
Message-ID: <58E7F689.8010709@hpe.com> (raw)
In-Reply-To: <58E7C875.8050008@hpe.com>

On 04/07/2017 01:12 PM, Linda Knippers wrote:
> On 04/07/2017 12:44 PM, Dan Williams wrote:
>> On Fri, Apr 7, 2017 at 6:28 AM, Linda Knippers <linda.knippers@hpe.com> wrote:
>> I've seen reports of this crash
>> signature from the team trying to integrate the ndctl unit tests into
>> the 0day kbuild robot, but I have thus far been unable to reproduce
>> them. On my system if I do:
>>
>> # modprobe nfit_test
>> # rmmod nfit_test
>> rmmod: ERROR: Module nfit_test is in use
>>
>> Are you saying you are able to remove nfit_test on your system without
>> first disabling regions?
> 
> No, sorry.  I missed that step in my description.  I'm doing 'ndctl disable-region all'
> before the rmmod.

I've been doing a bit more testing and once, I had 'ndctl check' make it through
all the tests and pass.  A few times I've made it part way through the tests before
I hit the panic.  However, if I just modprobe the modules, disable the regions,
and then rmmod nfit_test, it panics for me 100% of the time.  Try this in a script.

modprobe nfit
modprobe dax
modprobe dax_pmem
modprobe libnvdimm
modprobe nd_blk
modprobe nd_btt
modprobe nd_e820
modprobe nd_pmem
lsmod |grep nfit
modprobe nfit_test
lsmod |grep nfit
ndctl disable-region all
rmmod nfit_test

-- ljk

> 
> -- ljk
> 
> 

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-04-07 20:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 13:28 panics related to nfit_test? Linda Knippers
2017-04-07 16:44 ` Dan Williams
2017-04-07 17:12   ` Linda Knippers
2017-04-07 20:28     ` Linda Knippers [this message]
2017-04-07 21:46       ` Dan Williams
     [not found]         ` <CAPcyv4gS+z_HiMrgvayDaQr2qNKtZ+6boMdDZj0hQrxJhc+U6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-07 21:55           ` Linda Knippers
2017-04-14 15:50             ` Dan Williams
2017-04-14 22:12               ` Linda Knippers
2017-04-14 22:28                 ` Dan Williams
2017-04-14 23:31                   ` Linda Knippers
2017-04-14 23:42                     ` Dan Williams
2017-04-16 18:55                       ` Linda Knippers

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=58E7F689.8010709@hpe.com \
    --to=linda.knippers@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    /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