From: Takashi Iwai <tiwai@suse.de>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
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: Fri, 18 Mar 2016 09:00:13 +0100 [thread overview]
Message-ID: <s5hfuvousfm.wl-tiwai@suse.de> (raw)
In-Reply-To: <4588852.AE9c5HdInh@fractal>
On Fri, 18 Mar 2016 08:36:27 +0100,
Tomi Sarvela wrote:
>
> On Thursday 17 March 2016 18:00:52 Takashi Iwai wrote:
> ...
>
> > > 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.
> >
> > Well, I have no internal access, so I have no idea which one succeeded
> > and which one failed.
> >
> > Unfortunately I can't reproduce it in my side. A simpler unit test
> > that can reliably reproduce the issue would be really appreciated...
>
> Sorry, I was being unclear. They all fail on selected machines (ILK, SNB),
> since CI_DRM_1140.
Do you have the commit of the last working kernel?
> The unit tests that hang quite reliably on first run are
> igt@gem_ringfill_basic-default-s3
> igt@drv_module_reload_basic
> igt@kms_pipe_crc_basic@suspend-read-crc-pipe-[abc]
Where can I get these?
Takashi
_______________________________________________
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-18 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 17:52 [PATCH] drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs Imre Deak
2016-03-14 17:55 ` [PATCH v2] " Imre Deak
2016-03-15 7:50 ` Ander Conselvan De Oliveira
2016-03-15 9:27 ` Imre Deak
2016-03-15 17:54 ` [PATCH RESEND FOR CI] " Imre Deak
2016-03-16 7:31 ` ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3) Patchwork
2016-03-16 8:48 ` Imre Deak
2016-03-16 12:37 ` Tomi Sarvela
2016-03-16 12:43 ` Imre Deak
2016-03-16 15:37 ` Daniel Vetter
2016-03-16 15:40 ` [Intel-gfx] " Takashi Iwai
2016-03-17 7:57 ` Tomi Sarvela
2016-03-17 17:00 ` Takashi Iwai
2016-03-18 7:36 ` [Intel-gfx] " Tomi Sarvela
2016-03-18 8:00 ` Takashi Iwai [this message]
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
2016-03-16 14:12 ` Imre Deak
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=s5hfuvousfm.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libin.yang@linux.intel.com \
--cc=tomi.p.sarvela@intel.com \
/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