From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: Tegra baseline test results for v4.14-rc3
Date: Mon, 2 Oct 2017 10:39:37 +0100 [thread overview]
Message-ID: <c874cf3e-0f59-6922-fa68-40223cca7c13@nvidia.com> (raw)
In-Reply-To: <39a8ab29-1eda-674a-6f55-d4cf95eff223-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 02/10/17 10:34, Jon Hunter wrote:
> Here are some basic Tegra test results for Linux v4.14-rc3.
> Logs and other details at:
>
> https://nvtb.github.io//linux/test_v4.14-rc3/20171001153104/
>
>
> Test summary
> ------------
>
> Build: zImage:
> Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
>
> Build: Image:
> Pass: ( 1/ 1): defconfig
>
> Boot to userspace: defconfig:
> Pass: ( 4/ 4): qemu-vexpress64, tegra132-norrin,
> tegra210-p2371-0000, tegra210-smaug
>
> Boot to userspace: multi_v7_defconfig:
> Pass: ( 5/ 5): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra124-nyan-big, tegra20-trimslice, tegra30-beaver
>
> Boot to userspace: tegra_defconfig:
> Pass: ( 5/ 5): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra124-nyan-big, tegra20-trimslice, tegra30-beaver
>
> PM: System suspend: multi_v7_defconfig:
> FAIL: ( 3/ 5): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra30-beaver
> Pass: ( 2/ 5): tegra124-nyan-big, tegra20-trimslice
>
> PM: System suspend: tegra_defconfig:
> FAIL: ( 3/ 5): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra30-beaver
> Pass: ( 2/ 5): tegra124-nyan-big, tegra20-trimslice
The cause of the above suspend failure has been identified and a
candidate for fixing this is under review [0].
Cheers
Jon
[0] https://www.spinics.net/lists/linux-usb/msg161139.html
--
nvpublic
prev parent reply other threads:[~2017-10-02 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 9:34 Tegra baseline test results for v4.14-rc3 Jon Hunter
[not found] ` <39a8ab29-1eda-674a-6f55-d4cf95eff223-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-02 9:39 ` Jon Hunter [this message]
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=c874cf3e-0f59-6922-fa68-40223cca7c13@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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