linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Dorau, Lukasz" <lukasz.dorau@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
	"Slusarz, Marcin" <marcin.slusarz@intel.com>
Subject: Re: nfit_test: issue #2: modprobe: ERROR: could not insert 'nfit_test': Unknown symbol in module, or unknown parameter
Date: Fri, 13 Mar 2020 08:41:26 -0700	[thread overview]
Message-ID: <CAPcyv4igs_41gvtoqkA6a8LshkrXsKLBaZa3KwkuRRPyczdXSg@mail.gmail.com> (raw)
In-Reply-To: <SN6PR11MB28647C6C4DE888D1B74A903B96FA0@SN6PR11MB2864.namprd11.prod.outlook.com>

On Fri, Mar 13, 2020 at 2:49 AM Dorau, Lukasz <lukasz.dorau@intel.com> wrote:
>
> On Thursday, March 12, 2020 6:06 PM Dan Williams <dan.j.williams@intel.com> wrote:
> >
> > Yes, you're environment is not being careful to exclude the production
> > version of the modules from being loaded. The ndctl unit test core
> > also sanity checks nfit_Test and reports the collisions before running
> > tests. See nfit_test_init():
> >
> >     https://github.com/pmem/ndctl/blob/master/test/core.c#L119
> >
> > I'd recommend at least running:
> >
> >     make TESTS=libndctl check
> >
> > ...from latest ndctl.git to sanity check your nfit_test module
> > dependencies before trying to load it manually.
> >
> > See the troubleshooting document:
> >
> >     https://github.com/pmem/ndctl#troubleshooting
> >
> > ...for other tips about how to prevent the production modules from loading.
>
> Thanks for tips! I have followed those instructions and it did not help:
>
> $ cat /etc/depmod.d/nvdimm-extra
> override nfit * extra
> override device_dax * extra
> override dax_pmem * extra
> override dax_pmem_core * extra
> override dax_pmem_compat * extra
> override libnvdimm * extra
> override nd_blk * extra
> override nd_btt * extra
> override nd_e820 * extra
> override nd_pmem * extra
>
> $ find /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/ -name "*nfit*"
> /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/kernel/drivers/acpi/nfit
> /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/kernel/drivers/acpi/nfit/nfit.ko.xz
> /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/extra/nfit.ko.xz
> /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/extra/test/nfit_test.ko.xz
> /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/extra/test/nfit_test_iomap.ko.xz
>
> $ make TESTS=libndctl check
> [...]
> make --no-print-directory check-TESTS
> SKIP: libndctl
> ============================================================================
> Testsuite summary for ndctl 67
> ============================================================================
> # TOTAL: 1
> # PASS:  0
> # SKIP:  1
> # XFAIL: 0
> # FAIL:  0
> # XPASS: 0
> # ERROR: 0
> ============================================================================
>
> $ cat test/test-suite.log
> [...]
> .. contents:: :depth: 2
>
> SKIP: libndctl
> ==============
>
> test/init: nfit_test_init: nfit.ko: appears to be production version: /lib/modules/5.6.0-rc1-13504-g7b27a8622f80/kernel/drivers/acpi/nfit/nfit.ko.xz
> __ndctl_test_skip: explicit skip test_libndctl:2695
> nfit_test unavailable skipping tests
> libdaxctl: daxctl_unref: context 0xe02a00 released
> libndctl: ndctl_unref: context 0xe05f20 released
> attempted: 1 skipped: 1
> SKIP libndctl (exit status: 77)
>
> As you can see 'ndctl' also cannot load the extra test version of the modules even if there is the following file:
>
> $ cat /etc/depmod.d/nvdimm-extra
> override nfit * extra
> override device_dax * extra
> override dax_pmem * extra
> override dax_pmem_core * extra
> override dax_pmem_compat * extra
> override libnvdimm * extra
> override nd_blk * extra
> override nd_btt * extra
> override nd_e820 * extra
> override nd_pmem * extra
>
> Can I try anything else? Do you have any suggestions?

Do you have the nfit, or libnvdimm modules loading from the initramfs?
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

  reply	other threads:[~2020-03-13 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 14:38 Dorau, Lukasz
2020-03-12 17:05 ` Dan Williams
2020-03-13  9:49   ` Dorau, Lukasz
2020-03-13 15:41     ` Dan Williams [this message]
2020-03-16  8:41       ` Dorau, Lukasz

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=CAPcyv4igs_41gvtoqkA6a8LshkrXsKLBaZa3KwkuRRPyczdXSg@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=lukasz.dorau@intel.com \
    --cc=marcin.slusarz@intel.com \
    --subject='Re: nfit_test: issue #2: modprobe: ERROR: could not insert '\''nfit_test'\'': Unknown symbol in module, or unknown parameter' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).