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, 14 Apr 2017 19:31:28 -0400 [thread overview]
Message-ID: <58F15BD0.9040708@hpe.com> (raw)
In-Reply-To: <CAPcyv4hYa2B8Zg9Tw1RfBFNwXX9+m+DnwytyxwqZwWsVW-o+Ug@mail.gmail.com>
On 04/14/2017 06:28 PM, Dan Williams wrote:
>
> I have not, but I did send out a new patch that makes sure to shutdown
> the nfit_test trickery before freeing the test objects. Does this
> patch cleanup any of the failures you are seeing?
>
> https://patchwork.kernel.org/patch/9681861/
>
I tried it and got similar results. On my server, once it panicked in rmmod, once it
panicked when disabling the regions. I got excited on my laptop because it survived
the rmmod, but then panicked a few seconds later. I also got a panic that might
have been during the modprobe but I can't be sure because I don't get good information
when my laptop crashes.
I see people posting tests so it's working for some people. Anyone else
interested in sharing what you're running on and exactly how you're building
and installing your kernel and these modules?
-- ljk
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-04-14 23:31 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
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 [this message]
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=58F15BD0.9040708@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.