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.6-rc1
Date: Tue, 19 Apr 2016 10:26:51 +0100 [thread overview]
Message-ID: <5715F9DB.5040403@nvidia.com> (raw)
In-Reply-To: <5715F45E.3080305-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 19/04/16 10:03, Jon Hunter wrote:
> Here are some basic Tegra test results for Linux v4.6-rc1.
> Logs and other details at:
>
> https://nvtb.github.io//linux/test_v4.6-rc1/20160330013102/
>
>
> Test summary
> ------------
>
> Build: zImage:
> Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
>
> Build: Image:
> Pass: ( 1/ 1): defconfig
>
> Boot to userspace: defconfig:
> Pass: ( 3/ 3): qemu-vexpress64, tegra132-norrin,
> tegra210-p2371-0000
>
> Boot to userspace: multi_v7_defconfig:
> Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra20-trimslice, tegra30-beaver
>
> Boot to userspace: tegra_defconfig:
> Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra20-trimslice, tegra30-beaver
>
> PM: System suspend: multi_v7_defconfig:
> FAIL: ( 1/ 4): tegra124-jetson-tk1
This failure occurs intermittently and was caused by enabling the UHS-I
modes for Tegra124. To workaround this we have disabled these mode for
now [0].
Jon
[0] http://www.spinics.net/lists/linux-mmc/msg36245.html
WARNING: multiple messages have this Message-ID (diff)
From: jonathanh@nvidia.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v4.6-rc1
Date: Tue, 19 Apr 2016 10:26:51 +0100 [thread overview]
Message-ID: <5715F9DB.5040403@nvidia.com> (raw)
In-Reply-To: <5715F45E.3080305@nvidia.com>
On 19/04/16 10:03, Jon Hunter wrote:
> Here are some basic Tegra test results for Linux v4.6-rc1.
> Logs and other details at:
>
> https://nvtb.github.io//linux/test_v4.6-rc1/20160330013102/
>
>
> Test summary
> ------------
>
> Build: zImage:
> Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
>
> Build: Image:
> Pass: ( 1/ 1): defconfig
>
> Boot to userspace: defconfig:
> Pass: ( 3/ 3): qemu-vexpress64, tegra132-norrin,
> tegra210-p2371-0000
>
> Boot to userspace: multi_v7_defconfig:
> Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra20-trimslice, tegra30-beaver
>
> Boot to userspace: tegra_defconfig:
> Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
> tegra20-trimslice, tegra30-beaver
>
> PM: System suspend: multi_v7_defconfig:
> FAIL: ( 1/ 4): tegra124-jetson-tk1
This failure occurs intermittently and was caused by enabling the UHS-I
modes for Tegra124. To workaround this we have disabled these mode for
now [0].
Jon
[0] http://www.spinics.net/lists/linux-mmc/msg36245.html
next prev parent reply other threads:[~2016-04-19 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 9:03 Tegra baseline test results for v4.6-rc1 Jon Hunter
2016-04-19 9:03 ` Jon Hunter
[not found] ` <5715F45E.3080305-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-04-19 9:26 ` Jon Hunter [this message]
2016-04-19 9:26 ` Jon Hunter
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=5715F9DB.5040403@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.