From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next sleep: 10 runs, 2 regressions (renesas-next-2021-07-19-v5.14-rc1)
Date: Mon, 19 Jul 2021 11:45:39 -0700 (PDT) [thread overview]
Message-ID: <60f5c853.1c69fb81.2969a.4b7c@mx.google.com> (raw)
renesas/next sleep: 10 runs, 2 regressions (renesas-next-2021-07-19-v5.14-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
------------------+------+---------------+----------+--------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 2
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2021-07-19-v5.14-rc1/plan/sleep/
Test: sleep
Tree: renesas
Branch: next
Describe: renesas-next-2021-07-19-v5.14-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 2a022240886d918d1f09a50b86a4065256caac42
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
------------------+------+---------------+----------+--------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 2
Details: https://kernelci.org/test/plan/id/60f5bbbf51d1b9d24f1160c0
Results: 21 PASS, 2 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//renesas/next/renesas-next-2021-07-19-v5.14-rc1/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2021-07-19-v5.14-rc1/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster/20210709.0/armhf/rootfs.cpio.gz
* sleep.rtcwake-mem-3: https://kernelci.org/test/case/id/60f5bbbf51d1b9d24f1160d3
failing since 55 days (last pass: renesas-next-2021-05-11-v5.13-rc1, first fail: renesas-next-2021-05-25-v5.13-rc1)
2021-07-19T17:49:34.538664 rtcwake: assuming RTC uses UTC ...
2021-07-19T17:49:34.543815 rtcwake: wakeup from \"mem\" using rtc0 at Mon Jul 19 17:49:41 2021
2021-07-19T17:49:34.558227 <6>[ 102.121180] PM: suspend entry (deep)
2021-07-19T17:49:34.558785 <6>[ 102.125696] Filesystems sync: 0.000 seconds
2021-07-19T17:49:34.574221 <6>[ 102.133156] Freezing user space processes ... (elapsed 0.001 seconds) done.
2021-07-19T17:49:34.574776 <6>[ 102.143189] OOM killer disabled.
2021-07-19T17:49:35.696278 <6>[ 102.147182] Freezing remaining freezable tasks ...
2021-07-19T17:49:35.696836 <3>[ 103.256493] usb 2-1: device descriptor read/64, error -110
2021-07-19T17:49:36.040722 <6>[ 103.606532] usb 2-1: new high-speed USB device number 5 using dwc2
2021-07-19T17:49:41.289659 <3>[ 108.856486] usb 2-1: device descriptor read/64, error -110
... (19 line(s) more)
* sleep.rtcwake-mem-2: https://kernelci.org/test/case/id/60f5bbbf51d1b9d24f1160d4
failing since 55 days (last pass: renesas-next-2021-05-11-v5.13-rc1, first fail: renesas-next-2021-05-25-v5.13-rc1)
2021-07-19T17:49:14.231951 <6>[ 81.781704] smsc95xx 2-1.1:1.0 eth0: Link is Down
2021-07-19T17:49:14.232177 rtcwake: assuming RTC uses UTC ...
2021-07-19T17:49:14.232525 <4>[ 81.793127] ------------[ cut here ]------------
2021-07-19T17:49:14.257038 rtcwake: wakeup from \"mem\" using rtc0 at Mon Jul 19 17:49:21 202<4>[ 81.802064] WARNING: CPU: 2 PID: 152 at fs/kernfs/dir.c:1509 kernfs_remove_by_name_ns+0xa8/0xb0
2021-07-19T17:49:14.257265 1
2021-07-19T17:49:14.257454 <4>[ 81.818292] kernfs: can not remove 'attached_dev', no directory
2021-07-19T17:49:14.269906 <4>[ 81.825472] Modules linked in: btmrvl_sdio btmrvl
2021-07-19T17:49:14.270216 <6>[ 81.825477] PM: suspend entry (deep)
2021-07-19T17:49:14.270648 <4>[ 81.825479] mwifiex_sdio mwifiex bluetooth
2021-07-19T17:49:14.281208 <6>[ 81.831038] Filesystems sync: 0.000 seconds
... (64 line(s) more)
reply other threads:[~2021-07-19 22:07 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=60f5c853.1c69fb81.2969a.4b7c@mx.google.com \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).