Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
	imre.deak@intel.com, alsa-devel@alsa-project.org,
	intel-gfx@lists.freedesktop.org,
	Libin Yang <libin.yang@linux.intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)
Date: Wed, 16 Mar 2016 16:40:24 +0100	[thread overview]
Message-ID: <s5hlh5ibfdj.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160316153706.GT14170@phenom.ffwll.local>

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:
> > On Wednesday 16 March 2016 10:48:43 Imre Deak wrote:
> > > Tomi, noticed two things that maybe infrastructure related, see below:
> > > 
> > > > Test drv_module_reload_basic:
> > > >                 skip       -> PASS       (bdw-nuci7)
> > > > Test gem_ringfill:
> > > >         Subgroup basic-default-s3:
> > > >                 pass       -> DMESG-WARN (skl-nuci5)
> > > > Test gem_storedw_loop:
> > > >         Subgroup basic-bsd:
> > > >                 pass       -> DMESG-WARN (skl-nuci5)
> > > >         Subgroup basic-bsd1:
> > > >                 pass       -> DMESG-WARN (skl-nuci5)
> > > 
> > > Unrelated platform. All of the above are SND resume failures. Ville
> > > said he contacted Takashi about them.
> > 
> > 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.


Takashi

  reply	other threads:[~2016-03-16 15:40 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         ` Takashi Iwai [this message]
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
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=s5hlh5ibfdj.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel@ffwll.ch \
    --cc=imre.deak@intel.com \
    --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