From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] HAX drm/i915: Disable CSR (DMC) for Kabylake
Date: Thu, 12 Oct 2017 13:55:24 -0700 [thread overview]
Message-ID: <20171012205524.vjijbc4esmhxqq45@intel.com> (raw)
In-Reply-To: <150783738499.17631.7508970612220933145@mail.alporthouse.com>
On Thu, Oct 12, 2017 at 07:43:04PM +0000, Chris Wilson wrote:
> Quoting Rodrigo Vivi (2017-10-12 19:04:45)
> > On Thu, Oct 12, 2017 at 10:18:13AM +0000, Chris Wilson wrote:
> > > ---
> >
> > Why?
>
> Have you looked at the random but frequent mmio death on Kabylake?
> Seems rather reminiscent of earlier DMC bugs.
hm... Could you please give us an example?
a link?
and why do you think that would be dmc?
I've seen many bugs there on kbl, but mostly associated to LSPCON
and link trainings, and gpu hangs... and the ones I looked now
seemed that DC state was blocked.
But well... yeap... it is a black box right?! so the
experiment is valid for sure.
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-12 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 10:18 [PATCH] HAX drm/i915: Disable CSR (DMC) for Kabylake Chris Wilson
2017-10-12 11:10 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-10-12 15:49 ` ✓ Fi.CI.IGT: success " Patchwork
2017-10-12 15:54 ` Chris Wilson
2017-10-12 18:04 ` [PATCH] " Rodrigo Vivi
2017-10-12 19:43 ` Chris Wilson
2017-10-12 20:55 ` Rodrigo Vivi [this message]
2017-10-12 21:07 ` Chris Wilson
2017-10-20 11:33 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-10-20 13:39 ` ✓ Fi.CI.IGT: success " Patchwork
2017-10-20 14:31 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-10-20 15:59 ` ✓ Fi.CI.IGT: success " 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=20171012205524.vjijbc4esmhxqq45@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chris@chris-wilson.co.uk \
--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.