All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
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 16:04:48 +0100	[thread overview]
Message-ID: <20161021150448.GQ25629@nuc-i3427.alporthouse.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:
> > 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.

That's so CI 1730s.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-10-21 15: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ä
2016-10-28 10:51       ` Ander Conselvan De Oliveira
2016-10-21 15:04     ` Chris Wilson [this message]
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=20161021150448.GQ25629@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.