From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master sleep: 6 runs, 2 regressions (renesas-devel-2021-05-31-v5.13-rc4)
Date: Mon, 31 May 2021 07:41:01 -0700 (PDT) [thread overview]
Message-ID: <60b4f57d.1c69fb81.86705.3487@mx.google.com> (raw)
renesas/master sleep: 6 runs, 2 regressions (renesas-devel-2021-05-31-v5.13-rc4)
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/master/kernel/renesas-devel-2021-05-31-v5.13-rc4/plan/sleep/
Test: sleep
Tree: renesas
Branch: master
Describe: renesas-devel-2021-05-31-v5.13-rc4
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: a17b18482334959148cabda392caea262c68ba77
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/60b4ec0505ca8ae7cdb3afb8
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/master/renesas-devel-2021-05-31-v5.13-rc4/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2021-05-31-v5.13-rc4/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster/20210520.0/armhf/rootfs.cpio.gz
* sleep.rtcwake-mem-2: https://kernelci.org/test/case/id/60b4ec0505ca8ae7cdb3afbd
failing since 20 days (last pass: v5.12-451-gae657abc971d2, first fail: renesas-devel-2021-05-10-v5.13-rc1)
2021-05-31 13:58:17.581000+00:00 rtcwake: wakeup from \"mem\" using rtc0 at Mon May 31 13:58:23 2021
2021-05-31 13:58:17.590000+00:00 <6>[ 82.226855] PM: suspend entry (deep)
2021-05-31 13:58:17.597000+00:00 <6>[ 82.233313] Filesystems sync: 0.000 seconds
2021-05-31 13:58:17.609000+00:00 <6>[ 82.240673] Freezing user space processes ... (elapsed 0.001 seconds) done.
2021-05-31 13:58:17.615000+00:00 <6>[ 82.252035] OOM killer disabled.
2021-05-31 13:58:17.891000+00:00 <6>[ 82.258030] Freezing remaining freezable tasks ...
2021-05-31 13:58:17.899000+00:00 <3>[ 82.525698] dwmmc_rockchip ff0c0000.mmc: Busy; trying anyway
2021-05-31 13:58:18.411000+00:00 <3>[ 83.042244] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
2021-05-31 13:58:18.419000+00:00 <6>[ 83.054042] smsc95xx 2-1.1:1.0 eth0: Link is Down
2021-05-31 13:58:18.429000+00:00 <6>[ 83.061728] smsc95xx 2-1.1:1.0 eth0: hardware isn't capable of remote wakeup
... (26 line(s) more)
* sleep.rtcwake-mem-3: https://kernelci.org/test/case/id/60b4ec0505ca8ae7cdb3afbe
failing since 20 days (last pass: v5.12-451-gae657abc971d2, first fail: renesas-devel-2021-05-10-v5.13-rc1)
2021-05-31 13:58:37.854000+00:00 rtcwake: wakeup from \"mem\" using rtc0 at Mon May 31 13:58:43 2021
2021-05-31 13:58:37.865000+00:00 <6>[ 102.502910] PM: suspend entry (deep)
2021-05-31 13:58:37.886000+00:00 <6>[ 102.522063] Filesystems sync: 0.000 seconds
2021-05-31 13:58:37.897000+00:00 <6>[ 102.529474] Freezing user space processes ... (elapsed 0.001 seconds) done.
2021-05-31 13:58:37.902000+00:00 <6>[ 102.540895] OOM killer disabled.
2021-05-31 13:58:39.425000+00:00 <6>[ 102.546890] Freezing remaining freezable tasks ...
2021-05-31 13:58:39.438000+00:00 <3>[ 104.061253] usb 2-1: device descriptor read/64, error -110
2021-05-31 13:58:39.787000+00:00 <6>[ 104.421287] usb 2-1: new high-speed USB device number 5 using dwc2
2021-05-31 13:58:45.026000+00:00 <3>[ 109.661231] usb 2-1: device descriptor read/64, error -110
2021-05-31 13:58:57.913000+00:00 <4>[ 122.552719]
... (21 line(s) more)
reply other threads:[~2021-05-31 16:04 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=60b4f57d.1c69fb81.86705.3487@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).