- Linux-stable-mirror - lists.linaro.org

stable/linux-4.9.y boot: 62 boots: 0 failed, 48 passed with 14 offline (v4.9.136)

by kernelci.org bot

stable/linux-4.9.y boot: 62 boots: 0 failed, 48 passed with 14 offline (v4.9.136) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.9.y/kernel/v4.9.136/ Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.9.y/kernel/v4.9.136/ Tree: stable Branch: linux-4.9.y Git Describe: v4.9.136 Git Commit: 0bb1a5e5aa1728a2c501cdd916923ef44fc07e2f Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 38 unique boards, 17 SoC families, 13 builds out of 182 Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab socfpga_defconfig: socfpga_cyclone5_de0_sockit: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

[PATCH 3.16, 4.4, 4.9] dm bufio: drop the lock when doing GFP_NOIO allocation

by Mikulas Patocka

This is backport of the upstream patch 41c73a49df31151f4ff868f28fe4f129f113fa2c. It should be backported to stable kernels because this performance problem was seen on the android 4.4 kernel. commit 41c73a49df31151f4ff868f28fe4f129f113fa2c Author: Mikulas Patocka <mpatocka(a)redhat.com> Date: Wed Nov 23 17:04:00 2016 -0500 dm bufio: drop the lock when doing GFP_NOIO allocation If the first allocation attempt using GFP_NOWAIT fails, drop the lock and retry using GFP_NOIO allocation (lock is dropped because the allocation can take some time). Note that we won't do GFP_NOIO allocation when we loop for the second time, because the lock shouldn't be dropped between __wait_for_free_buffer and __get_unclaimed_buffer. Signed-off-by: Mikulas Patocka <mpatocka(a)redhat.com> Signed-off-by: Mike Snitzer <snitzer(a)redhat.com> diff --git a/drivers/md/dm-bufio.c b/drivers/md/dm-bufio.c index 9ef88f0e2382..1c2e1dd7ca16 100644 --- a/drivers/md/dm-bufio.c +++ b/drivers/md/dm-bufio.c @@ -822,6 +822,7 @@ enum new_flag { static struct dm_buffer *__alloc_buffer_wait_no_callback(struct dm_bufio_client *c, enum new_flag nf) { struct dm_buffer *b; + bool tried_noio_alloc = false; /* * dm-bufio is resistant to allocation failures (it just keeps @@ -846,6 +847,15 @@ static struct dm_buffer *__alloc_buffer_wait_no_callback(struct dm_bufio_client if (nf == NF_PREFETCH) return NULL; + if (dm_bufio_cache_size_latch != 1 && !tried_noio_alloc) { + dm_bufio_unlock(c); + b = alloc_buffer(c, GFP_NOIO | __GFP_NORETRY | __GFP_NOMEMALLOC | __GFP_NOWARN); + dm_bufio_lock(c); + if (b) + return b; + tried_noio_alloc = true; + } + if (!list_empty(&c->reserved_buffers)) { b = list_entry(c->reserved_buffers.next, struct dm_buffer, lru_list);

7 years

3
2
0 0

[PATCH 3.16, 4.4, 4.9] dm bufio: avoid sleeping while holding the dm_bufio lock

by Mikulas Patocka

This is backport of the upstream patch 9ea61cac0b1ad0c09022f39fd97e9b99a2cfc2dc. It should be backported to stable kernels because this performance problem was seen on the android 4.4 kernel. commit 9ea61cac0b1ad0c09022f39fd97e9b99a2cfc2dc Author: Douglas Anderson <dianders(a)chromium.org> Date: Thu Nov 17 11:24:20 2016 -0800 dm bufio: avoid sleeping while holding the dm_bufio lock We've seen in-field reports showing _lots_ (18 in one case, 41 in another) of tasks all sitting there blocked on: mutex_lock+0x4c/0x68 dm_bufio_shrink_count+0x38/0x78 shrink_slab.part.54.constprop.65+0x100/0x464 shrink_zone+0xa8/0x198 In the two cases analyzed, we see one task that looks like this: Workqueue: kverityd verity_prefetch_io __switch_to+0x9c/0xa8 __schedule+0x440/0x6d8 schedule+0x94/0xb4 schedule_timeout+0x204/0x27c schedule_timeout_uninterruptible+0x44/0x50 wait_iff_congested+0x9c/0x1f0 shrink_inactive_list+0x3a0/0x4cc shrink_lruvec+0x418/0x5cc shrink_zone+0x88/0x198 try_to_free_pages+0x51c/0x588 __alloc_pages_nodemask+0x648/0xa88 __get_free_pages+0x34/0x7c alloc_buffer+0xa4/0x144 __bufio_new+0x84/0x278 dm_bufio_prefetch+0x9c/0x154 verity_prefetch_io+0xe8/0x10c process_one_work+0x240/0x424 worker_thread+0x2fc/0x424 kthread+0x10c/0x114 ...and that looks to be the one holding the mutex. The problem has been reproduced on fairly easily: 0. Be running Chrome OS w/ verity enabled on the root filesystem 1. Pick test patch: http://crosreview.com/412360 2. Install launchBalloons.sh and balloon.arm from http://crbug.com/468342 ...that's just a memory stress test app. 3. On a 4GB rk3399 machine, run nice ./launchBalloons.sh 4 900 100000 ...that tries to eat 4 * 900 MB of memory and keep accessing. 4. Login to the Chrome web browser and restore many tabs With that, I've seen printouts like: DOUG: long bufio 90758 ms ...and stack trace always show's we're in dm_bufio_prefetch(). The problem is that we try to allocate memory with GFP_NOIO while we're holding the dm_bufio lock. Instead we should be using GFP_NOWAIT. Using GFP_NOIO can cause us to sleep while holding the lock and that causes the above problems. The current behavior explained by David Rientjes: It will still try reclaim initially because __GFP_WAIT (or __GFP_KSWAPD_RECLAIM) is set by GFP_NOIO. This is the cause of contention on dm_bufio_lock() that the thread holds. You want to pass GFP_NOWAIT instead of GFP_NOIO to alloc_buffer() when holding a mutex that can be contended by a concurrent slab shrinker (if count_objects didn't use a trylock, this pattern would trivially deadlock). This change significantly increases responsiveness of the system while in this state. It makes a real difference because it unblocks kswapd. In the bug report analyzed, kswapd was hung: kswapd0 D ffffffc000204fd8 0 72 2 0x00000000 Call trace: [<ffffffc000204fd8>] __switch_to+0x9c/0xa8 [<ffffffc00090b794>] __schedule+0x440/0x6d8 [<ffffffc00090bac0>] schedule+0x94/0xb4 [<ffffffc00090be44>] schedule_preempt_disabled+0x28/0x44 [<ffffffc00090d900>] __mutex_lock_slowpath+0x120/0x1ac [<ffffffc00090d9d8>] mutex_lock+0x4c/0x68 [<ffffffc000708e7c>] dm_bufio_shrink_count+0x38/0x78 [<ffffffc00030b268>] shrink_slab.part.54.constprop.65+0x100/0x464 [<ffffffc00030dbd8>] shrink_zone+0xa8/0x198 [<ffffffc00030e578>] balance_pgdat+0x328/0x508 [<ffffffc00030eb7c>] kswapd+0x424/0x51c [<ffffffc00023f06c>] kthread+0x10c/0x114 [<ffffffc000203dd0>] ret_from_fork+0x10/0x40 By unblocking kswapd memory pressure should be reduced. Suggested-by: David Rientjes <rientjes(a)google.com> Reviewed-by: Guenter Roeck <linux(a)roeck-us.net> Signed-off-by: Douglas Anderson <dianders(a)chromium.org> Signed-off-by: Mike Snitzer <snitzer(a)redhat.com> diff --git a/drivers/md/dm-bufio.c b/drivers/md/dm-bufio.c index 125aedc3875f..b5d3428d109e 100644 --- a/drivers/md/dm-bufio.c +++ b/drivers/md/dm-bufio.c @@ -827,7 +827,8 @@ static struct dm_buffer *__alloc_buffer_wait_no_callback(struct dm_bufio_client * dm-bufio is resistant to allocation failures (it just keeps * one buffer reserved in cases all the allocations fail). * So set flags to not try too hard: - * GFP_NOIO: don't recurse into the I/O layer + * GFP_NOWAIT: don't wait; if we need to sleep we'll release our + * mutex and wait ourselves. * __GFP_NORETRY: don't retry and rather return failure * __GFP_NOMEMALLOC: don't use emergency reserves * __GFP_NOWARN: don't print a warning in case of failure @@ -837,7 +838,7 @@ static struct dm_buffer *__alloc_buffer_wait_no_callback(struct dm_bufio_client */ while (1) { if (dm_bufio_cache_size_latch != 1) { - b = alloc_buffer(c, GFP_NOIO | __GFP_NORETRY | __GFP_NOMEMALLOC | __GFP_NOWARN); + b = alloc_buffer(c, GFP_NOWAIT | __GFP_NORETRY | __GFP_NOMEMALLOC | __GFP_NOWARN); if (b) return b; }

7 years

3
2
0 0

stable/linux-4.4.y boot: 55 boots: 1 failed, 42 passed with 12 offline (v4.4.163)

by kernelci.org bot

stable/linux-4.4.y boot: 55 boots: 1 failed, 42 passed with 12 offline (v4.4.163) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.4.y/kernel/v4.4.163/ Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.4.y/kernel/v4.4.163/ Tree: stable Branch: linux-4.4.y Git Describe: v4.4.163 Git Commit: 7a4269707deb6ab22d488eb1a9eedae3ef88abc5 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 33 unique boards, 16 SoC families, 12 builds out of 178 Boot Failure Detected: arm: multi_v7_defconfig stih410-b2120: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

stable-rc/linux-4.18.y boot: 87 boots: 3 failed, 66 passed with 16 offline, 2 conflicts (v4.18.18)

by kernelci.org bot

stable-rc/linux-4.18.y boot: 87 boots: 3 failed, 66 passed with 16 offline, 2 conflicts (v4.18.18) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.18.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.18.y/kernel/v4.18.18/ Tree: stable-rc Branch: linux-4.18.y Git Describe: v4.18.18 Git Commit: 99661278215dc80915280cfab5c19dbdf5575424 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 53 unique boards, 20 SoC families, 15 builds out of 187 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.18.17-35-g46c86a0ac4a1) sunxi_defconfig: sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17-35-g46c86a0ac4a1) sun8i-h3-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17-35-g46c86a0ac4a1) vexpress_defconfig: qemu: lab-baylibre: new failure (last pass: v4.18.17-35-g46c86a0ac4a1) x86: x86_64_defconfig: qemu: lab-baylibre: new failure (last pass: v4.18.17-35-g46c86a0ac4a1) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab sunxi_defconfig sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

stable/linux-4.18.y boot: 126 boots: 8 failed, 93 passed with 16 offline, 9 conflicts (v4.18.18)

by kernelci.org bot

stable/linux-4.18.y boot: 126 boots: 8 failed, 93 passed with 16 offline, 9 conflicts (v4.18.18) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.18.y/kernel/v4.18.1… Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.18.y/kernel/v4.18.18/ Tree: stable Branch: linux-4.18.y Git Describe: v4.18.18 Git Commit: 99661278215dc80915280cfab5c19dbdf5575424 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 65 unique boards, 23 SoC families, 15 builds out of 187 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.18.17) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: new failure (last pass: v4.18.17) meson8b-odroidc1: lab-baylibre: new failure (last pass: v4.18.17) qemu: lab-baylibre: new failure (last pass: v4.18.17) sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17) sun8i-h3-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17) sunxi_defconfig: sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17) sun8i-h3-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17) vexpress_defconfig: qemu: lab-baylibre: new failure (last pass: v4.18.17) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.18.17) meson-gxbb-nanopi-k2: lab-baylibre: new failure (last pass: v4.18.17) meson-gxbb-p200: lab-baylibre: new failure (last pass: v4.18.17) meson-gxl-s905x-khadas-vim: lab-baylibre: new failure (last pass: v4.18.17) meson-gxl-s905x-libretech-cc: lab-baylibre: new failure (last pass: v4.18.17) qemu: lab-baylibre: new failure (last pass: v4.18.17) sun50i-h5-libretech-all-h3-cc: lab-baylibre: new failure (last pass: v4.18.17) x86: x86_64_defconfig: qemu: lab-baylibre: new failure (last pass: v4.18.17) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab sunxi_defconfig sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab multi_v7_defconfig sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab sun50i-h5-libretech-all-h3-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS imx6q-sabrelite: lab-baylibre: FAIL lab-collabora: PASS meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS arm64: defconfig: meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS meson-gxbb-p200: lab-baylibre: FAIL lab-baylibre-seattle: PASS qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

stable/linux-4.14.y boot: 124 boots: 3 failed, 96 passed with 16 offline, 9 conflicts (v4.14.80)

by kernelci.org bot

stable/linux-4.14.y boot: 124 boots: 3 failed, 96 passed with 16 offline, 9 conflicts (v4.14.80) Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.14.y/kernel/v4.14.8… Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.14.y/kernel/v4.14.80/ Tree: stable Branch: linux-4.14.y Git Describe: v4.14.80 Git Commit: 0b047cbc44ae7d0cea41a99cd7ec1f009360a605 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Tested: 62 unique boards, 23 SoC families, 15 builds out of 185 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.14.79) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: new failure (last pass: v4.14.79) meson8b-odroidc1: lab-baylibre: new failure (last pass: v4.14.79) qemu: lab-baylibre: new failure (last pass: v4.14.79) vexpress_defconfig: qemu: lab-baylibre: new failure (last pass: v4.14.79) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.14.79) meson-gxbb-nanopi-k2: lab-baylibre: new failure (last pass: v4.14.79) meson-gxl-s905x-khadas-vim: lab-baylibre: new failure (last pass: v4.14.79) meson-gxl-s905x-libretech-cc: lab-baylibre: new failure (last pass: v4.14.79) qemu: lab-baylibre: new failure (last pass: v4.14.79) x86: x86_64_defconfig: qemu: lab-baylibre: new failure (last pass: v4.14.79) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS imx6q-sabrelite: lab-baylibre: FAIL lab-collabora: PASS vexpress_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS arm64: defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS meson-gxbb-p200: lab-baylibre: FAIL lab-baylibre-seattle: PASS meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

stable-rc/linux-4.14.y boot: 124 boots: 3 failed, 96 passed with 16 offline, 9 conflicts (v4.14.80)

by kernelci.org bot

stable-rc/linux-4.14.y boot: 124 boots: 3 failed, 96 passed with 16 offline, 9 conflicts (v4.14.80) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.80/ Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.80 Git Commit: 0b047cbc44ae7d0cea41a99cd7ec1f009360a605 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 62 unique boards, 23 SoC families, 15 builds out of 185 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.14.79-32-g24f453c41e18) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: new failure (last pass: v4.14.79) meson8b-odroidc1: lab-baylibre: new failure (last pass: v4.14.79) qemu: lab-baylibre: new failure (last pass: v4.14.79) vexpress_defconfig: qemu: lab-baylibre: new failure (last pass: v4.14.79) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: new failure (last pass: v4.14.79) meson-gxbb-nanopi-k2: lab-baylibre: new failure (last pass: v4.14.79) meson-gxbb-p200: lab-baylibre: new failure (last pass: v4.14.79) meson-gxl-s905x-khadas-vim: lab-baylibre: new failure (last pass: v4.14.79) meson-gxl-s905x-libretech-cc: lab-baylibre: new failure (last pass: v4.14.79) qemu: lab-baylibre: new failure (last pass: v4.14.79) x86: x86_64_defconfig: qemu: lab-baylibre: new failure (last pass: v4.14.79-32-g24f453c41e18) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: FAIL lab-collabora: PASS qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS vexpress_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS arm64: defconfig: meson-gxbb-p200: lab-baylibre: FAIL lab-baylibre-seattle: PASS bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

stable-rc/linux-4.4.y boot: 98 boots: 2 failed, 79 passed with 12 offline, 5 conflicts (v4.4.163)

by kernelci.org bot

stable-rc/linux-4.4.y boot: 98 boots: 2 failed, 79 passed with 12 offline, 5 conflicts (v4.4.163) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.163/ Tree: stable-rc Branch: linux-4.4.y Git Describe: v4.4.163 Git Commit: 7a4269707deb6ab22d488eb1a9eedae3ef88abc5 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 42 unique boards, 20 SoC families, 15 builds out of 178 Boot Regressions Detected: arm: multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: new failure (last pass: v4.4.162-102-g3116ad4951a1) meson8b-odroidc1: lab-baylibre: new failure (last pass: v4.4.162-102-g2adb31f2a949) qemu: lab-baylibre: new failure (last pass: v4.4.162-102-g2adb31f2a949) vexpress_defconfig: qemu: lab-baylibre: new failure (last pass: v4.4.162-116-gb63fc4e232df) arm64: defconfig: qemu: lab-baylibre: new failure (last pass: v4.4.162-116-gb63fc4e232df) x86: x86_64_defconfig: qemu: lab-baylibre: new failure (last pass: v4.4.162-116-gb63fc4e232df) Boot Failures Detected: arm: multi_v7_defconfig meson8b-odroidc1: 1 failed lab stih410-b2120: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: FAIL lab-collabora: PASS qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS vexpress_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS arm64: defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS x86: x86_64_defconfig: qemu: lab-linaro-lkft: PASS lab-baylibre: FAIL lab-mhart: PASS lab-collabora: PASS --- For more info write to <info(a)kernelci.org>

7 years

1
0
0 0

[PATCH] kdb: use correct pointer when 'btc' calls 'btt'

by Christophe Leroy

On a powerpc 8xx, 'btc' fails as follows: Entering kdb (current=0x(ptrval), pid 282) due to Keyboard Entry kdb> btc btc: cpu status: Currently on cpu 0 Available cpus: 0 kdb_getarea: Bad address 0x0 when booting the kernel with 'debug_boot_weak_hash', it fails as well Entering kdb (current=0xba99ad80, pid 284) due to Keyboard Entry kdb> btc btc: cpu status: Currently on cpu 0 Available cpus: 0 kdb_getarea: Bad address 0xba99ad80 On other platforms, Oopses have been observed too, see https://github.com/linuxppc/linux/issues/139 This is due to btc calling 'btt' with %p pointer as an argument. This patch replaces %p by %px to get the real pointer value as expected by 'btt' Signed-off-by: Christophe Leroy <christophe.leroy(a)c-s.fr> Cc: <stable(a)vger.kernel.org> # 4.15+ --- kernel/debug/kdb/kdb_bt.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/debug/kdb/kdb_bt.c b/kernel/debug/kdb/kdb_bt.c index 6ad4a9fcbd6f..7921ae4fca8d 100644 --- a/kernel/debug/kdb/kdb_bt.c +++ b/kernel/debug/kdb/kdb_bt.c @@ -179,14 +179,14 @@ kdb_bt(int argc, const char **argv) kdb_printf("no process for cpu %ld\n", cpu); return 0; } - sprintf(buf, "btt 0x%p\n", KDB_TSK(cpu)); + sprintf(buf, "btt 0x%px\n", KDB_TSK(cpu)); kdb_parse(buf); return 0; } kdb_printf("btc: cpu status: "); kdb_parse("cpu\n"); for_each_online_cpu(cpu) { - sprintf(buf, "btt 0x%p\n", KDB_TSK(cpu)); + sprintf(buf, "btt 0x%px\n", KDB_TSK(cpu)); kdb_parse(buf); touch_nmi_watchdog(); } -- 2.13.3

7 years

7
9
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror