From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org, kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: stable/linux-5.13.y baseline: 115 runs, 2 regressions (v5.13.8)
Date: Wed, 04 Aug 2021 20:10:13 -0700 (PDT) [thread overview]
Message-ID: <610b5695.1c69fb81.3f444.e880@mx.google.com> (raw)
stable/linux-5.13.y baseline: 115 runs, 2 regressions (v5.13.8)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-------------------+------+--------------+----------+-------------------+------------
bcm2837-rpi-3-b-32 | arm | lab-baylibre | gcc-8 | bcm2835_defconfig | 2
Details: https://kernelci.org/test/job/stable/branch/linux-5.13.y/kernel/v5.13.8/plan/baseline/
Test: baseline
Tree: stable
Branch: linux-5.13.y
Describe: v5.13.8
URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
SHA: 3cfdd7252e00ecf3f3dc9508525acf1e67b7d343
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-------------------+------+--------------+----------+-------------------+------------
bcm2837-rpi-3-b-32 | arm | lab-baylibre | gcc-8 | bcm2835_defconfig | 2
Details: https://kernelci.org/test/plan/id/610b1a83cdf1234e8cb13667
Results: 4 PASS, 2 FAIL, 0 SKIP
Full config: bcm2835_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//stable/linux-5.13.y/v5.13.8/arm/bcm2835_defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b-32.txt
HTML log: https://storage.kernelci.org//stable/linux-5.13.y/v5.13.8/arm/bcm2835_defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b-32.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-6-g8983f3b738df/armel/baseline/rootfs.cpio.gz
* baseline.dmesg.alert: https://kernelci.org/test/case/id/610b1a83cdf1234e8cb1366b
new failure (last pass: v5.13.7)
13 lines
2021-08-04T22:53:33.351634 kern :alert : Register r0 information: NULL pointer
2021-08-04T22:53:33.353647 kern :alert : Register r1 information: non-paged memory
2021-08-04T22:53:33.354775 kern :alert : R<8>[ 13.433297] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=alert RESULT=fail UNITS=lines MEASUREMENT=13>
2021-08-04T22:53:33.355634 egister r2 information: NULL pointer
2021-08-04T22:53:33.356509 kern :alert : Register r3 information: non-slab/vmalloc memory
2021-08-04T22:53:33.357385 kern :alert : Register r4 information: NULL pointer
* baseline.dmesg.emerg: https://kernelci.org/test/case/id/610b1a83cdf1234e8cb1366c
new failure (last pass: v5.13.7)
36 lines
2021-08-04T22:53:33.361324 kern :alert : Register r5 information: slab kernfs_iattrs_cache start c357a000 pointer offset 0
2021-08-04T22:53:33.395677 kern :alert : Register r6 information: non-slab/vmalloc memory
2021-08-04T22:53:33.396508 kern :alert : Register r7 information: NULL pointer
2021-08-04T22:53:33.397884 kern :alert : Register r8<8>[ 13.477057] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=emerg RESULT=fail UNITS=lines MEASUREMENT=36>
2021-08-04T22:53:33.398800 information: NULL point<8>[ 13.487991] <LAVA_SIGNAL_ENDRUN 0_dmesg 647004_1.5.2.4.1>
2021-08-04T22:53:33.399594 er
2021-08-04T22:53:33.400329 kern :alert : Register r9 information: non-paged memory
reply other threads:[~2021-08-05 3:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=610b5695.1c69fb81.3f444.e880@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox