public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT:  success for drm/i915: Redo old gmch irq handling (rev2)
Date: Wed, 30 Aug 2017 20:13:21 +0300	[thread overview]
Message-ID: <20170830171321.GJ4914@intel.com> (raw)
In-Reply-To: <d62c4394-74b6-5b6a-91ba-80622a20cfac@intel.com>

On Mon, Aug 21, 2017 at 03:15:39PM +0300, Tomi Sarvela wrote:
> On 21/08/17 15:09, Ville Syrjälä wrote:
> > On Fri, Aug 18, 2017 at 09:19:23PM +0100, Chris Wilson wrote:
> >> Quoting Patchwork (2017-08-18 20:41:45)
> >>> == Series Details ==
> >>>
> >>> Series: drm/i915: Redo old gmch irq handling (rev2)
> >>> URL   : https://patchwork.freedesktop.org/series/26215/
> >>> State : success
> >>>
> >>> == Summary ==
> >>>
> >>> Series 26215v2 drm/i915: Redo old gmch irq handling
> >>> https://patchwork.freedesktop.org/api/1.0/series/26215/revisions/2/mbox/
> >>>
> >>> Test gem_exec_flush:
> >>>          Subgroup basic-batch-kernel-default-uc:
> >>>                  fail       -> PASS       (fi-snb-2600) fdo#100007
> >>> Test kms_flip:
> >>>          Subgroup basic-flip-vs-modeset:
> >>>                  skip       -> PASS       (fi-skl-x1585l) fdo#101781
> >>>
> >>> fdo#100007 https://bugs.freedesktop.org/show_bug.cgi?id=100007
> >>> fdo#101781 https://bugs.freedesktop.org/show_bug.cgi?id=101781
> >>>
> >>> fi-blb-e6850     total:279  pass:224  dwarn:1   dfail:0   fail:0   skip:54  time:365s
> >>> fi-ilk-650       total:279  pass:229  dwarn:0   dfail:0   fail:0   skip:50  time:419s
> >>> fi-pnv-d510      total:279  pass:223  dwarn:1   dfail:0   fail:0   skip:55  time:527s
> >>
> >> That's a reasonably intensive workout of the interrupt handler. Ironlake
> >> in particular is pretty bad at seqno coherency. Would like to have had
> >> the gdg and elk/ctg results, what happened to those?
> > 
> > That's a good question. bwr seems to be missing as well. Tomi?
> 
> For hang reasons, BWR and ELK haven't been part of the Patchwork runs. 
> Added tag to both of them now when the issue is fixed.
> 
> CTG is a laptop, and occasionally stops answering to AC boot. Causes 
> noise, so this hasn't been participating Trybot/Patchwork runs.
> 
> GDG is usually (=always) hanging to igt@drv_hangman@error-state-basic 
> which is one of the first tests run. There hasn't been a reason to keep 
> it in Patchwork/Trybot.
> 
> I can re-run the tests through Patchwork if you want, and you'll get 
> results to at least BWR and ELK.

Please do. More results on affected machines wouldn't hurt.

-- 
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:[~2017-08-30 17:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 18:36 [PATCH v2 00/16] drm/i915: Redo old gmch irq handling ville.syrjala
2017-08-18 18:36 ` [PATCH 01/16] drm/i915: Don't enable/unmask flip interrupts ville.syrjala
2017-09-14 12:09   ` Imre Deak
2017-08-18 18:36 ` [PATCH 02/16] drm/i915: Clear pipestat consistently ville.syrjala
2017-09-14 13:51   ` Imre Deak
2017-08-18 18:36 ` [PATCH v2 03/16] drm/i915: s/GEN5/GEN3/ ville.syrjala
2017-08-18 18:36 ` [PATCH 04/16] drm/i915: Use GEN3_IRQ_RESET/INIT on gen3/4 ville.syrjala
2017-08-18 19:16   ` Chris Wilson
2017-08-18 18:36 ` [PATCH 05/16] drm/i915: Introduce GEN2_IRQ_RESET/INIT ville.syrjala
2017-08-18 18:36 ` [PATCH 06/16] drm/i915: Setup EMR first on all gen2-4 ville.syrjala
2017-08-18 18:36 ` [PATCH 07/16] drm/i915: Eliminate PORT_HOTPLUG_EN setup from gen3/4 irq_postinstall ville.syrjala
2017-08-18 18:36 ` [PATCH 08/16] drm/i915: Unify the appearance of gen3/4 irq_postistall hooks ville.syrjala
2017-08-18 18:36 ` [PATCH 09/16] drm/i915: Remove NULL dev_priv checks from irq_uninstall ville.syrjala
2017-08-18 18:36 ` [PATCH 10/16] drm/i915: Extract PIPESTAT irq handling into separate functions ville.syrjala
2017-08-18 18:37 ` [PATCH v2 11/16] drm/i915: Rewrite GMCH irq handlers to avoid loops ville.syrjala
2017-08-18 19:20   ` Chris Wilson
2017-08-18 18:37 ` [PATCH 12/16] drm/i915: Mask everything in ring HWSTAM on gen6+ in ringbuffer mode ville.syrjala
2017-08-18 18:37 ` [PATCH 13/16] drm/i915: Gen3 HWSTAM is actually 32 bits ville.syrjala
2017-08-18 18:37 ` [PATCH 14/16] drm/i915: Clean up the HWSTAM mess ville.syrjala
2017-08-18 18:37 ` [PATCH 15/16] drm/i915: Remove duplicated irq_preinstall/uninstall hooks ville.syrjala
2017-08-18 18:37 ` [PATCH 16/16] drm/i915: Reinstate GMBUS and AUX interrupts on gen4/g4x ville.syrjala
2017-08-18 18:44   ` Jiri Kosina
2017-08-18 19:41 ` ✓ Fi.CI.BAT: success for drm/i915: Redo old gmch irq handling (rev2) Patchwork
2017-08-18 20:19   ` Chris Wilson
2017-08-21 12:09     ` Ville Syrjälä
2017-08-21 12:15       ` Tomi Sarvela
2017-08-30 17:13         ` Ville Syrjälä [this message]
2017-09-01 10:06 ` Patchwork
2017-09-01 10:23 ` Patchwork
2017-09-01 11:13 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-01 12:03 ` Patchwork
2017-09-14 14:50 ` [PATCH v2 00/16] drm/i915: Redo old gmch irq handling Ville Syrjälä
2017-09-14 14:54   ` Chris Wilson
2017-09-14 14:55     ` Chris Wilson
2017-09-15 11:46       ` Ville Syrjälä

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=20170830171321.GJ4914@intel.com \
    --to=ville.syrjala@linux.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