From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Silence debugging DRM_ERROR for failing to suspend vlv powerwells
Date: Thu, 03 May 2018 11:58:17 +0300 [thread overview]
Message-ID: <87in8586ae.fsf@intel.com> (raw)
In-Reply-To: <152529675655.13018.8943601942667749623@mail.alporthouse.com>
On Wed, 02 May 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Chris Wilson (2018-04-09 10:54:46)
>> Quoting Chris Wilson (2018-04-09 10:49:05)
>> > If we try to suspend a wedged device following a GPU reset failure, we
>> > will also fail to turn off the rc6 powerwells (on vlv), leading to a
>> > *ERROR*. This is quite expected in this case, so the best we can do is
>> > shake our heads and reduce the *ERROR* to a debug so CI stops
>> > complaining.
>> >
>> > Testcase: igt/gem_eio/in-flight-suspend #vlv
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105583
>
> Does anyone want to keep this *ERROR* that we can trigger at will?
No strong feelings. I guess my question is, can this happen when there's
no GPU reset failures, and the change would silence that?
Anyway, if it makes CI less noisy,
Acked-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-03 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 9:49 [PATCH] drm/i915: Silence debugging DRM_ERROR for failing to suspend vlv powerwells Chris Wilson
2018-04-09 9:54 ` Chris Wilson
2018-05-02 21:32 ` Chris Wilson
2018-05-03 8:58 ` Jani Nikula [this message]
2018-05-03 9:06 ` Chris Wilson
2018-04-09 10:20 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-04-09 11:20 ` ✓ Fi.CI.IGT: " 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=87in8586ae.fsf@intel.com \
--to=jani.nikula@linux.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.