Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: 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: Wed, 16 Mar 2016 14:43:34 +0200	[thread overview]
Message-ID: <1458132214.4473.12.camel@intel.com> (raw)
In-Reply-To: <6454956.W1mfK3ePPj@fractal>

On Wed, 2016-03-16 at 14:37 +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.
> 
> > > Test kms_flip:
> > >         Subgroup basic-flip-vs-wf_vblank:
> > >                 dmesg-warn -> PASS       (hsw-brixbox)
> > >                 pass       -> DMESG-WARN (bdw-ultra)
> > 
> > Unrelated platform.
> > Tomi, there are ACPI erros in the log, maybe needs a BIOS upgrade?
> > It's
> > also affected by
> > https://bugs.freedesktop.org/show_bug.cgi?id=94349
> 
> Brixbox is at the newest BIOS available. Did you mean Intel Ultrabook
> 2in1?

No not that one but the above bdw-ultra. See the ACPI errors in
archive/results/CI_IGT_test/Patchwork_1607/bdw-ultra/html/bdw-ultra@Patchwork_1607@1/igt@kms_flip@basic-flip-vs-wf_vblank.html

--Imre

> 
> > > Test kms_pipe_crc_basic:
> > >         Subgroup read-crc-pipe-c:
> > >                 fail       -> PASS       (hsw-brixbox)
> > >         Subgroup suspend-read-crc-pipe-b:
> > >                 dmesg-warn -> PASS       (skl-nuci5)
> > >         Subgroup suspend-read-crc-pipe-c:
> > >                 pass       -> INCOMPLETE (skl-nuci5)
> > 
> > Unrelated platform, I opened a new bug:
> > https://bugs.freedesktop.org/show_bug.cgi?id=94566
> 
> Suspend-read-crc-pipes are notoriously unstable, and main reason (in
> addition 
> to drv_module_reload_basic) to hangs.
> 
> > Tomi, basic-rte has also DMESG-WARN on snb-dellxps, yet not on this
> > list.
> 
> SNB-dellxps is in a bad state, there's alsa blocking shutdown and
> startup 
> within set timelimits. It'll be probably out until snd is fixed.
> 
> Tomi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-16 12:43 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 [this message]
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
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=1458132214.4473.12.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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