Skip to contentSkip to conversation

Segmentation fault when running "make M=tools/testing/nvdimm"

DISCUSSION Soccer Liu 2 participants 3 messages Sep 20, 2017 – Sep 22, 2017 2 messages not in the archive libnvdimm: non-volatile memory device

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Soccer Liu

author
#1 lore raw

Hi:  As part of processing in setting up the environment for running unitests, I was able to work through the instrcutions in https://github.com/pmem/ndctl/tree/0a628fdf4fe58a283b16c1bbaa49bb28b1842bf9
all the way until I hit the followingbuild error (Segmentation fault) when buiding libnvdimm.o.Anyone hit this before?root@ubuntu:/home/soccerl/nvdimm#  make M=tools/testing/nvdimm AR      tools/testing/nvdimm/built-in.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/core.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/bus.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/namespace_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/label.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/claim.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/btt_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/pfn_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dax_devs.o
  CC [M]  tools/testing/nvdimm/config_check.o
  LD [M]  tools/testing/nvdimm/libnvdimm.o
Segmentation fault
scripts/Makefile.build:548: recipe for target 'tools/testing/nvdimm/libnvdimm.o' failed
make[1]: *** [tools/testing/nvdimm/libnvdimm.o] Error 139
Makefile:1511: recipe for target '_module_tools/testing/nvdimm' failed
make: *** [_module_tools/testing/nvdimm] Error 2My devbox has 4.13 Linux in it.
I am not sure whether it has anything to do with fact that I didnt do anything with ndctl/ndctl.spec.in (because I am not sure how to apply those dependendies to my testbox) Thanks Cheng-mean
_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm

#2 lore raw
Quoted 18 lines · Soccer Liu

Hi: As part of processing in setting up the environment for running unitests, I was able to work through the instrcutions in https://github.com/pmem/ndctl/tree/0a628fdf4fe58a283b16c1bbaa49bb28b1842bf9
all the way until I hit the followingbuild error (Segmentation fault) when buiding libnvdimm.o.Anyone hit this before?root@ubuntu:/home/soccerl/nvdimm# make M=tools/testing/nvdimm

  AR      tools/testing/nvdimm/built-in.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/core.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/bus.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/namespace_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/label.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/claim.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/btt_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/pfn_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dax_devs.o
  CC [M]  tools/testing/nvdimm/config_check.o
  LD [M]  tools/testing/nvdimm/libnvdimm.o
Quoted 6 lines

Segmentation fault
scripts/Makefile.build:548: recipe for target 'tools/testing/nvdimm/libnvdimm.o' failed
make[1]: *** [tools/testing/nvdimm/libnvdimm.o] Error 139
Makefile:1511: recipe for target '_module_tools/testing/nvdimm' failed
make: *** [_module_tools/testing/nvdimm] Error 2My devbox has 4.13 Linux in it.
I am not sure whether it has anything to do with fact that I didnt do anything with ndctl/ndctl.spec.in (because I am not sure how to apply those dependendies to my testbox) Thanks

No, this seems like a bug in your toolchain. What version of gcc are you running?
_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm

A message that is not in the archive (sent off-list or not yet received): CAPcyv4gRdiMTnx6+K9gGi6sSc4strDV6qhhWX+n5xBwp=HfPBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

author
#4 lore raw

Thanks for reply, Dan.

After switchingfrom 4.13rc6 to 4.14rc1, this compilation time segmentation fault for libnvdimm.o no longer repros.

Doc does not match the test code below does not match the kconfig requirements under the "Unit Tests" section in https://github.com/pmem/ndctl  testing/nvdimm/config_check.cvoid check(void){        /*        * These kconfig symbols must be set to "m" fornfit_test to        * load and operate.        */       BUILD_BUG_ON(!IS_MODULE(CONFIG_LIBNVDIMM));       BUILD_BUG_ON(!IS_MODULE(CONFIG_BLK_DEV_PMEM));       BUILD_BUG_ON(!IS_MODULE(CONFIG_ND_BTT));       BUILD_BUG_ON(!IS_MODULE(CONFIG_ND_PFN));       BUILD_BUG_ON(!IS_MODULE(CONFIG_ND_BLK));       BUILD_BUG_ON(!IS_MODULE(CONFIG_ACPI_NFIT));       BUILD_BUG_ON(!IS_MODULE(CONFIG_DEV_DAX));       BUILD_BUG_ON(!IS_MODULE(CONFIG_DEV_DAX_PMEM));} After following the doc, I still have to make the following kconfig changes to get pass above checking. CONFIG_DEV_DAX=mCONFIG_DEV_DAX_PMEM=mCONFIG_ACPI_NFIT
It would be great to see  the following kconfig settings got added into to the doc CONFIG_DEV_DAX = mCONFIG_ND_PFN = m CONFIG_ND_BTT = mCONFIG_ACPI_NFIT = mCONFIG_DEV_DAX_PMEM =m

When I ran "make check", I am seeing either SKIPs or FAILs for those test cases. (I haven't even put in any of my  private changes yet)
=====================================
   ndctl 58.2: test/test-suite.log
=====================================# TOTAL: 14
# PASS:  0
# SKIP:  9
# XFAIL: 0
# FAIL:  5
# XPASS: 0
# ERROR: 0

root@nvdimm:/home/soccerl/linux414rc1/tools# lsmod
Module                  Size  Used by
nfit_test              28672  1
nfit_test_iomap        16384  1 nfit_test
efivarfs               16384  1

Is this expected for the 4.14rc build? Or I did something wrongWhich  build is known for test lean result?

==============================================================FAIL: create.sh ===============+ DEV=
+ NDCTL=../ndctl/ndctl
+ BUS='-b nfit_test.0'
+ json2var='s/[{}",]//g; s/:/=/g'
+ SECTOR_SIZE=4096
+ rc=77
+ set -e
+ check_min_kver 4.5
+ local ver=4.5
++ uname -r
+ : 4.14.0-rc1
+ '[' -n 4.5 ']'
++ echo -e '4.5\n4.14.0-rc1'
++ head -1
++ sort -V
+ [[ 4.5 == \4\.\5 ]]
+ set -e
+ trap 'err $LINENO' ERR
+ modprobe nfit_test
+ ../ndctl/ndctl disable-region -b nfit_test.0 all
disabled 0 regions
+ ../ndctl/ndctl zero-labels -b nfit_test.0 all
zeroed 0 nmem
+ ../ndctl/ndctl enable-region -b nfit_test.0 all
enabled 0 regions
+ rc=1
+ dev=x
++ ../ndctl/ndctl create-namespace -b nfit_test.0 -t pmem -m raw failed to create namespace: No such device or address
+ json=
++ err 52
++ echo 'test/create: failed at line 52'
test/create: failed at line 52
++ exit 1
FAIL create.sh (exit status: 1)==================
FAIL: clear.sh
==============+ DEV=
+ NDCTL=../ndctl/ndctl
+ BUS='-b nfit_test.0'
+ BUS1='-b nfit_test.1'
+ json2var='s/[{}",]//g; s/:/=/g'
+ rc=77
+ set -e
+ check_min_kver 4.6
+ local ver=4.6
++ uname -r
+ : 4.14.0-rc1
+ '[' -n 4.6 ']'
++ echo -e '4.6\n4.14.0-rc1'
++ sort -V
++ head -1
+ [[ 4.6 == \4\.\6 ]]
+ set -e
+ trap 'err $LINENO' ERR
+ modprobe nfit_test
+ ../ndctl/ndctl disable-region -b nfit_test.0 all
disabled 0 regions
+ ../ndctl/ndctl zero-labels -b nfit_test.0 all
zeroed 0 nmem
+ ../ndctl/ndctl enable-region -b nfit_test.0 all
enabled 0 regions
+ rc=1
+ dev=x
++ ../ndctl/ndctl create-namespace -b nfit_test.0 -t pmem -m raw failed to create namespace: No such device or address
+ json=
++ err 52
++ echo 'test/clear: failed at line 52'
test/clear: failed at line 52
++ exit 1
FAIL clear.sh (exit status: 1)====================================
FAIL: multi-dax.sh
==================+ DEV=
+ NDCTL=../ndctl/ndctl
+ DAXCTL=../daxctl/daxctl
+ BUS='-b nfit_test.0'
+ BUS1='-b nfit_test.1'
+ json2var='s/[{}",]//g; s/:/=/g'
+ rc=77
+ check_min_kver 4.13
+ local ver=4.13
++ uname -r
+ : 4.14.0-rc1
+ '[' -n 4.13 ']'
++ echo -e '4.13\n4.14.0-rc1'
++ sort -V
++ head -1
+ [[ 4.13 == \4\.\1\3 ]]
+ set -e
+ trap 'err $LINENO' ERR
+ modprobe nfit_test
+ ../ndctl/ndctl disable-region -b nfit_test.0 all
disabled 0 regions
+ ../ndctl/ndctl zero-labels -b nfit_test.0 all
zeroed 0 nmem
+ ../ndctl/ndctl enable-region -b nfit_test.0 all
enabled 0 regions
+ query='. | sort_by(.available_size) | reverse | .[0].dev'
++ ../ndctl/ndctl list -b nfit_test.0 -t pmem -Ri
++ jq -r '. | sort_by(.available_size) | reverse | .[0].dev' ./multi-dax.sh: line 49: jq: command not found
+ region=
++ err 49
++ rc=1
++ echo 'test/multi-dax: failed at line 49'
test/multi-dax: failed at line 49
++ exit 1
FAIL multi-dax.sh (exit status: 1) =====================================FAIL: btt-check.sh ==================disabled 0 regions
zeroed 0 nmem
enabled 0 regions
failed to create namespace: No such device or address test/btt-check: failed at line 61
FAIL btt-check.sh (exit status: 1)====================
FAIL: blk-exhaust.sh
====================+ NDCTL=../ndctl/ndctl
+ BUS='-b nfit_test.0'
+ BUS1='-b nfit_test.1'
+ rc=77
+ set -e
+ check_min_kver 4.11
+ local ver=4.11
++ uname -r
+ : 4.14.0-rc1
+ '[' -n 4.11 ']'
++ echo -e '4.11\n4.14.0-rc1'
++ sort -V
++ head -1
+ [[ 4.11 == \4\.\1\1 ]]
+ set -e
+ trap 'err $LINENO' ERR
+ modprobe nfit_test
+ ../ndctl/ndctl disable-region -b nfit_test.0 all
disabled 0 regions
+ ../ndctl/ndctl zero-labels -b nfit_test.0 all
zeroed 0 nmem
+ ../ndctl/ndctl enable-region -b nfit_test.0 all
enabled 0 regions
+ rc=1
+ ../ndctl/ndctl create-namespace -b nfit_test.0 -t pmem
failed to create namespace: No such device or address
++ err 49
++ echo 'test/label-compat.sh: failed at line 49' test/label-compat.sh: failed at line 49
++ exit 1
FAIL blk-exhaust.sh (exit status: 1)
=============================

On Thursday, September 21, 2017 12:16 PM, Dan Williams <[email protected]> wrote:

Quoted 16 lines · Soccer Liu

Hi:  As part of processing in setting up the environment for running unitests, I was able to work through the instrcutions in https://github.com/pmem/ndctl/tree/0a628fdf4fe58a283b16c1bbaa49bb28b1842bf9
all the way until I hit the followingbuild error (Segmentation fault) when buiding libnvdimm.o.Anyone hit this before?root@ubuntu:/home/soccerl/nvdimm#  make M=tools/testing/nvdimm AR      tools/testing/nvdimm/built-in.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/core.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/bus.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dimm.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/region.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/namespace_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/label.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/claim.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/btt_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/pfn_devs.o
  CC [M]  tools/testing/nvdimm/../../../drivers/nvdimm/dax_devs.o

Quoted 8 lines

  CC [M]  tools/testing/nvdimm/config_check.o
  LD [M]  tools/testing/nvdimm/libnvdimm.o
Segmentation fault
scripts/Makefile.build:548: recipe for target 'tools/testing/nvdimm/libnvdimm.o' failed
make[1]: *** [tools/testing/nvdimm/libnvdimm.o] Error 139
Makefile:1511: recipe for target '_module_tools/testing/nvdimm' failed
make: *** [_module_tools/testing/nvdimm] Error 2My devbox has 4.13 Linux in it.
I am not sure whether it has anything to do with fact that I didnt do anything with ndctl/ndctl.spec.in (because I am not sure how to apply those dependendies to my testbox) Thanks

No, this seems like a bug in your toolchain. What version of gcc are you running?

_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm