From: Linda Knippers <ljknh-DaQTI0RpDDMAvxtiuMwx3w@public.gmane.org>
To: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
Subject: Re: panics related to nfit_test?
Date: Fri, 7 Apr 2017 17:55:07 -0400 [thread overview]
Message-ID: <58E80ABB.3040807@ymail.com> (raw)
In-Reply-To: <CAPcyv4gS+z_HiMrgvayDaQr2qNKtZ+6boMdDZj0hQrxJhc+U6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04/07/2017 05:46 PM, Dan Williams wrote:
> On Fri, Apr 7, 2017 at 1:28 PM, Linda Knippers <linda.knippers-ZPxbGqLxI0U@public.gmane.org> wrote:
>> 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-ZPxbGqLxI0U@public.gmane.org> 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
>>
>
> What distribution are you using? This loop is running fine in my
> Fedora Rawhide virtual machine environment. The other report of this
> was from a Debian environment. So I wonder if there is some timing
> differences related to udev or libkmod that prevent me from hitting
> the failure condition?
I'm running RHEL7.3 with a 4.11-rc5 kernel on bare metal with no
physical NVDIMMs. My system is a 2-socket box with E5-2695 v4
processors and a total of 72 cores with HT on. Maybe you need
more cores.
-- ljk
next prev parent reply other threads:[~2017-04-07 21:55 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
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 [this message]
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=58E80ABB.3040807@ymail.com \
--to=ljknh-daqti0rpddmavxtiumwx3w@public.gmane.org \
--cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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