Buildresult: powerpc-fixes/85xx/sbc8548_defconfig/powerpc-gcc5 built on Jul 29 2019, 23:38

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jul 29 2019, 23:38
Duration:	0:00:38.780636
Builder:	ka3
Revision:	powerpc/nvdimm: Pick nearby online node if the device node is not online (`225db419ce6a7468e7b219eee8e7ecc1f80f75b2)`
Target:	powerpc-fixes/85xx/sbc8548_defconfig/powerpc-gcc5
Branch:	powerpc-fixes
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	85xx/sbc8548_defconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify 225db419ce6a7468e7b219eee8e7ecc1f80f75b2^{commit} 225db419ce6a7468e7b219eee8e7ecc1f80f75b2 already have revision, skipping fetch # git checkout -q -f -B kisskb 225db419ce6a7468e7b219eee8e7ecc1f80f75b2 # git clean -qxdf # < git log -1 # commit 225db419ce6a7468e7b219eee8e7ecc1f80f75b2 # Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> # Date: Mon Jul 29 15:21:28 2019 +0530 # # powerpc/nvdimm: Pick nearby online node if the device node is not online # # Currently, nvdimm subsystem expects the device numa node for SCM device to be # an online node. It also doesn't try to bring the device numa node online. Hence # if we use a non-online numa node as device node we hit crashes like below. This # is because we try to access uninitialized NODE_DATA in different code paths. # # cpu 0x0: Vector: 300 (Data Access) at [c0000000fac53170] # pc: c0000000004bbc50: ___slab_alloc+0x120/0xca0 # lr: c0000000004bc834: __slab_alloc+0x64/0xc0 # sp: c0000000fac53400 # msr: 8000000002009033 # dar: 73e8 # dsisr: 80000 # current = 0xc0000000fabb6d80 # paca = 0xc000000003870000 irqmask: 0x03 irq_happened: 0x01 # pid = 7, comm = kworker/u16:0 # Linux version 5.2.0-06234-g76bd729b2644 (kvaneesh@ltc-boston123) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #135 SMP Thu Jul 11 05:36:30 CDT 2019 # enter ? for help # [link register ] c0000000004bc834 __slab_alloc+0x64/0xc0 # [c0000000fac53400] c0000000fac53480 (unreliable) # [c0000000fac53500] c0000000004bc818 __slab_alloc+0x48/0xc0 # [c0000000fac53560] c0000000004c30a0 __kmalloc_node_track_caller+0x3c0/0x6b0 # [c0000000fac535d0] c000000000cfafe4 devm_kmalloc+0x74/0xc0 # [c0000000fac53600] c000000000d69434 nd_region_activate+0x144/0x560 # [c0000000fac536d0] c000000000d6b19c nd_region_probe+0x17c/0x370 # [c0000000fac537b0] c000000000d6349c nvdimm_bus_probe+0x10c/0x230 # [c0000000fac53840] c000000000cf3cc4 really_probe+0x254/0x4e0 # [c0000000fac538d0] c000000000cf429c driver_probe_device+0x16c/0x1e0 # [c0000000fac53950] c000000000cf0b44 bus_for_each_drv+0x94/0x130 # [c0000000fac539b0] c000000000cf392c __device_attach+0xdc/0x200 # [c0000000fac53a50] c000000000cf231c bus_probe_device+0x4c/0xf0 # [c0000000fac53a90] c000000000ced268 device_add+0x528/0x810 # [c0000000fac53b60] c000000000d62a58 nd_async_device_register+0x28/0xa0 # [c0000000fac53bd0] c0000000001ccb8c async_run_entry_fn+0xcc/0x1f0 # [c0000000fac53c50] c0000000001bcd9c process_one_work+0x46c/0x860 # [c0000000fac53d20] c0000000001bd4f4 worker_thread+0x364/0x5f0 # [c0000000fac53db0] c0000000001c7260 kthread+0x1b0/0x1c0 # [c0000000fac53e20] c00000000000b954 ret_from_kernel_thread+0x5c/0x68 # # The patch tries to fix this by picking the nearest online node as the SCM node. # This does have a problem of us losing the information that SCM node is # equidistant from two other online nodes. If applications need to understand these # fine-grained details we should express then like x86 does via # /sys/devices/system/node/nodeX/accessY/initiators/ # # With the patch we get # # # numactl -H # available: 2 nodes (0-1) # node 0 cpus: # node 0 size: 0 MB # node 0 free: 0 MB # node 1 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 # node 1 size: 130865 MB # node 1 free: 129130 MB # node distances: # node 0 1 # 0: 10 20 # 1: 20 10 # # cat /sys/bus/nd/devices/region0/numa_node # 0 # # dmesg \| grep papr_scm # [ 91.332305] papr_scm ibm,persistent-memory:ibm,pmemory@44104001: Region registered with target node 2 and online node 0 # # Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/20190729095128.23707-1-aneesh.kumar@linux.ibm.com # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 225db419ce6a7468e7b219eee8e7ecc1f80f75b2 # < make -s -j 80 ARCH=powerpc O=/kisskb/build/powerpc-fixes_85xx_sbc8548_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- 85xx/sbc8548_defconfig # make -s -j 80 ARCH=powerpc O=/kisskb/build/powerpc-fixes_85xx_sbc8548_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- INFO: Uncompressed kernel (size 0x47a5b4) overlaps the address of the wrapper(0x400000) INFO: Fixing the link_address of wrapper to (0x500000) INFO: Uncompressed kernel (size 0x469ec0) overlaps the address of the wrapper(0x400000) INFO: Fixing the link_address of wrapper to (0x500000) Image Name: Linux-5.3.0-rc2-g225db419ce6a Created: Mon Jul 29 23:38:57 2019 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 2293504 Bytes = 2239.75 KiB = 2.19 MiB Load Address: 00000000 Entry Point: 00000000 Image Name: Linux-5.3.0-rc2-g225db419ce6a Created: Mon Jul 29 23:38:57 2019 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 2323243 Bytes = 2268.79 KiB = 2.22 MiB Load Address: 00500000 Entry Point: 005002a4 Completed OK # rm -rf /kisskb/build/powerpc-fixes_85xx_sbc8548_defconfig_powerpc-gcc5 # Build took: 0:00:38.780636

© Michael Ellerman 2006-2018.