From: Tomi Sarvela <tomi.p.sarvela@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Libin Yang <libin.yang@linux.intel.com>,
alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)
Date: Thu, 17 Mar 2016 09:57:23 +0200 [thread overview]
Message-ID: <1656335.ihdoht0X68@fractal> (raw)
In-Reply-To: <s5hlh5ibfdj.wl-tiwai@suse.de>
On Wednesday 16 March 2016 16:40:24 Takashi Iwai wrote:
> On Wed, 16 Mar 2016 16:37:06 +0100, Daniel Vetter wrote:
> > On Wed, Mar 16, 2016 at 02:37:24PM +0200, Tomi Sarvela wrote:
> > >
> > > SND is recurring problem. I'd like to see drm-intel-nightly not breaking
> > > when pulling sound updates.
> >
> > We need to escalate this again, snd team seriously sucks at quality
> > control :( Adding Libin&Takashi. If this doesn't improve I need to throw
> > sound trees out of -nightly for real.
>
> Sorry about that, but I couldn't get the warning on my machine.
>
> How is the procedure to reproduce the bug? Please give the exact
> commit id and environment you're testing, too.
Our CI has been built to mimic user environment, so base is up-to-date Ubuntu
15.04. This affects to boot-up mechanics and usermode software versions. There
are about dozen machines, 8 gens, from ILK to SKL.
Reproduction: CI is doing these steps
- Compile kernel: CI_DRM is drm-intel-nightly HEAD
- Deploy it to testhost: copy to /boot, recreate initrd
- Boot testhost to init 3
- Run newest IGT/piglit with basic testset
- Collect results
The last commits tested are:
CI_DRM_1140 git://anongit.freedesktop.org/drm-intel
3e5ecc8c5ff80cb1fb635ce1cf16b7cd4cfb1979
CI_DRM_1141 git://anongit.freedesktop.org/drm-intel
fc881ebd9c3c26919c7d1113f8bf7014e1a05563
CI_DRM_1142 git://anongit.freedesktop.org/drm-intel
9f8709ffd099e85e5e116ed7d09f1b8009f40847
CI_DRM_1143 git://anongit.freedesktop.org/drm-intel
5356c22379fc96cb087ee59bfdbbe46ec3bdf654
CI_DRM_1144 git://anongit.freedesktop.org/drm-intel
a5c43f5d1b4968a370f54bdda5387ce213aca785
CI_DRM_1145 git://anongit.freedesktop.org/drm-intel
bf3dcd53821a7d6c81f7061c6c7956aad57ec615
CI_DRM_1146 git://anongit.freedesktop.org/drm-intel
be0d1481fb1a2fd1cb199b81c9c01154a78d43dd
CI_DRM_1147 git://anongit.freedesktop.org/drm-intel
dbbc6d276864d7b7a3a1edb04f0511153f9c3852
Note that drm-intel-nightly history changes, so the exact commits might not be
there any more.
Tomi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-17 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457977942-11772-1-git-send-email-imre.deak@intel.com>
[not found] ` <20160316073153.17251.51881@emeril.freedesktop.org>
[not found] ` <1458118123.27377.11.camel@intel.com>
[not found] ` <6454956.W1mfK3ePPj@fractal>
2016-03-16 15:37 ` ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3) Daniel Vetter
2016-03-16 15:40 ` [Intel-gfx] " Takashi Iwai
2016-03-17 7:57 ` Tomi Sarvela [this message]
2016-03-17 17:00 ` Takashi Iwai
2016-03-18 7:36 ` [Intel-gfx] " Tomi Sarvela
2016-03-18 8:00 ` Takashi Iwai
2016-03-18 8:12 ` Tomi Sarvela
2016-03-18 15:02 ` Takashi Iwai
2016-03-16 15:50 ` Jani Nikula
2016-03-16 15:54 ` Daniel Vetter
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=1656335.ihdoht0X68@fractal \
--to=tomi.p.sarvela@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libin.yang@linux.intel.com \
--cc=tiwai@suse.de \
/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).