public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ander Conselvan De Oliveira <conselvan2@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT:  failure for Broxton ddi phy refactoring (rev5)
Date: Fri, 21 Oct 2016 17:23:55 +0300	[thread overview]
Message-ID: <20161021142355.GS4329@intel.com> (raw)
In-Reply-To: <1477059405.2720.9.camel@gmail.com>

On Fri, Oct 21, 2016 at 05:16:45PM +0300, Ander Conselvan De Oliveira wrote:
> On Wed, 2016-10-19 at 16:56 +0000, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: Broxton ddi phy refactoring (rev5)
> > URL   : https://patchwork.freedesktop.org/series/13320/
> > State : failure
> > 
> > == Summary ==
> > 
> > Series 13320v5 Broxton ddi phy refactoring
> > https://patchwork.freedesktop.org/api/1.0/series/13320/revisions/5/mbox/
> > 
> > Test drv_module_reload_basic:
> >                 pass       -> DMESG-WARN (fi-skl-6700hq)
> 
> [   37.937419] [drm:lspcon_init [i915]] No LSPCON detected, found unknown
> [   37.937488] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
> [   37.937569] [drm:intel_ddi_init [i915]] *ERROR* LSPCON init failed on port B
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=98353
> 
> > Test gem_exec_suspend:
> >         Subgroup basic-s3:
> >                 dmesg-warn -> PASS       (fi-skl-6700hq)
> > Test kms_cursor_legacy:
> >         Subgroup basic-busy-flip-before-cursor-legacy:
> >                 pass       -> DMESG-WARN (fi-ilk-650)
> 
> [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO
> underrun
> 
> Also happened once in CI 1733.
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=98251 ?
> 
> 
> > Test kms_force_connector_basic:
> >         Subgroup force-load-detect:
> >                 incomplete -> PASS       (fi-byt-j1900)
> >                 pass       -> INCOMPLETE (fi-ivb-3770)
> 
> BUG: unable to handle kernel NULL pointer dereference at           (null)
> [<ffffffffa00aa424>] intel_get_load_detect_pipe+0xe4/0x610 [i915]
> 
> Seems to happen sporadically between CI 1726 and 1736 across different machines.

https://patchwork.freedesktop.org/patch/116624/

> 
> 
> Ander
> 
> > Test kms_pipe_crc_basic:
> >         Subgroup suspend-read-crc-pipe-a:
> >                 dmesg-warn -> PASS       (fi-skl-6700hq)
> >         Subgroup suspend-read-crc-pipe-b:
> >                 dmesg-warn -> PASS       (fi-skl-6700hq)
> >         Subgroup suspend-read-crc-pipe-c:
> >                 dmesg-warn -> PASS       (fi-skl-6700hq)
> > 
> > fi-bdw-5557u     total:246  pass:231  dwarn:0   dfail:0   fail:0   skip:15 
> > fi-bsw-n3050     total:246  pass:203  dwarn:1   dfail:0   fail:0   skip:42 
> > fi-bxt-t5700     total:246  pass:216  dwarn:0   dfail:0   fail:0   skip:30 
> > fi-byt-j1900     total:246  pass:213  dwarn:1   dfail:0   fail:1   skip:31 
> > fi-byt-n2820     total:246  pass:209  dwarn:1   dfail:0   fail:1   skip:35 
> > fi-hsw-4770      total:246  pass:224  dwarn:0   dfail:0   fail:0   skip:22 
> > fi-hsw-4770r     total:246  pass:223  dwarn:1   dfail:0   fail:0   skip:22 
> > fi-ilk-650       total:246  pass:159  dwarn:25  dfail:0   fail:2   skip:60 
> > fi-ivb-3520m     total:246  pass:221  dwarn:0   dfail:0   fail:0   skip:25 
> > fi-ivb-3770      total:186  pass:164  dwarn:0   dfail:0   fail:0   skip:21 
> > fi-kbl-7200u     total:246  pass:222  dwarn:0   dfail:0   fail:0   skip:24 
> > fi-skl-6260u     total:246  pass:232  dwarn:0   dfail:0   fail:0   skip:14 
> > fi-skl-6700hq    total:246  pass:222  dwarn:1   dfail:0   fail:0   skip:23 
> > fi-skl-6700k     total:246  pass:221  dwarn:1   dfail:0   fail:0   skip:24 
> > fi-skl-6770hq    total:246  pass:232  dwarn:0   dfail:0   fail:0   skip:14 
> > fi-snb-2520m     total:246  pass:210  dwarn:0   dfail:0   fail:0   skip:36 
> > fi-snb-2600      total:209  pass:176  dwarn:0   dfail:0   fail:0   skip:32 
> > 
> > Results at /archive/results/CI_IGT_test/Patchwork_2762/
> > 
> > 21787266bd182df4c0d2067cf1b5c2379f61c24d drm-intel-nightly: 2016y-10m-19d-15h-
> > 39m-22s UTC integration manifest
> > b7c7077 drm/i915: Address broxton phy registers based on phy and channel
> > number
> > 88ab5e1 drm/i915: Add location of the Rcomp resistor to bxt_ddi_phy_info
> > 12c0f43 drm/i915: Create a struct to hold information about the broxton phys
> > 6e830b9 drm/i915: Move broxton vswing sequence to intel_dpio_phy.c
> > df0c1d2 drm/i915: Move DPIO phy documentation section to intel_dpio_phy.c
> > 421e554 drm/i915: Move broxton phy code to intel_dpio_phy.c
> > 125da91 drm/i915: Pass lane count to bxt_ddi_phy_calc_lane_optmin_mask()
> > cf9f51f drm/i915: Explicitly map broxton DPIO power wells to phys
> > 8f7b31c drm/i915: Rename struct i915_power_well field data to id
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-10-21 14:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 16:22 [PATCH v2 0/9] Broxton ddi phy refactoring Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 1/9] drm/i915: Rename struct i915_power_well field data to id Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 2/9] drm/i915: Explicitly map broxton DPIO power wells to phys Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 3/9] drm/i915: Pass lane count to bxt_ddi_phy_calc_lane_optmin_mask() Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 4/9] drm/i915: Move broxton phy code to intel_dpio_phy.c Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 5/9] drm/i915: Move DPIO phy documentation section " Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 6/9] drm/i915: Move broxton vswing sequence " Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 7/9] drm/i915: Create a struct to hold information about the broxton phys Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 8/9] drm/i915: Add location of the Rcomp resistor to bxt_ddi_phy_info Ander Conselvan de Oliveira
2016-10-06 16:22 ` [PATCH v2 9/9] drm/i915: Address broxton phy registers based on phy and channel number Ander Conselvan de Oliveira
2016-10-07  7:28   ` [PATCH v3 " Ander Conselvan de Oliveira
2016-10-10 11:53     ` Imre Deak
2016-10-19  7:54       ` [PATCH v4 " Ander Conselvan de Oliveira
2016-10-19  7:59       ` [PATCH v5 " Ander Conselvan de Oliveira
2016-10-06 17:21 ` ✗ Fi.CI.BAT: warning for Broxton ddi phy refactoring (rev2) Patchwork
2016-10-07  7:50 ` ✗ Fi.CI.BAT: warning for Broxton ddi phy refactoring (rev3) Patchwork
2016-10-07  8:35 ` Patchwork
2016-10-19  9:57 ` ✗ Fi.CI.BAT: failure for Broxton ddi phy refactoring (rev5) Patchwork
2016-10-19 16:56 ` Patchwork
2016-10-21 14:16   ` Ander Conselvan De Oliveira
2016-10-21 14:23     ` Ville Syrjälä [this message]
2016-10-28 10:51       ` Ander Conselvan De Oliveira
2016-10-21 15:04     ` Chris Wilson
2016-10-28  9:46 ` ✗ Fi.CI.BAT: warning " Patchwork

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=20161021142355.GS4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox