public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: i915 issues with 4.6
Date: Tue, 31 May 2016 13:10:01 -0500	[thread overview]
Message-ID: <bd8da15f-3a14-c9fc-3ce7-c864de183709@linux.intel.com> (raw)
In-Reply-To: <26938bc0-0c1e-a60c-43ba-d3e2e4d54a1b@linux.intel.com>

On 5/18/16 3:53 PM, Pierre-Louis Bossart wrote:
> On 5/18/16 2:08 AM, Ville Syrjälä wrote:
>> On Tue, May 17, 2016 at 07:09:58PM -0500, Pierre-Louis Bossart wrote:
>>>
>>>
>>> On 05/17/2016 01:16 PM, Ville Syrjälä wrote:
>>>> On Tue, May 17, 2016 at 01:00:13PM -0500, Pierre-Louis Bossart wrote:
>>>>> Hi,
>>>>> I was porting the HDMI audio patch to 4.6 as a service to several
>>>>> folks
>>>>> who need them before we finally upstream the reworked code, and I
>>>>> notice
>>>>> that the UI would freeze within 2s to 5mn, with all sorts of GPU hangs
>>>>> and issues reported in dmesg and /sys/calls/drm/card0/error
>>>>> Things work fine with the latest drm-intel-nightly branch from last
>>>>> night
>>>>> Known issue or should I file a bug?
>>>> One GPU hang generally looks like any other from the symptom POV.
>>>> Without the error state it's pretty much impossible to speculate.
>>>> Just filing a new bug is usually the best policy.
>>>>
>>>> If it's indeed a kernel regression a bisect would also be helpful.
>>>> Or in this case perhaps a reverse bisect since you say nightly is
>>>> fine, so we might want to know what fixed it.
>>>
>>> bug filed at https://bugs.freedesktop.org/show_bug.cgi?id=95467
>>>
>>> V4.5 works fine
>>> v4.6 is broken in less than 20s when moving windows around (can still
>>> get to virtual console)
>>> drm-intel-nightly works fine
>>>
>>> git bisect says this commit fixes the issue:
>>>
>>> commit a5e485a95c9c4cdd93b4c6dc53eee3bd1e50de11
>>> Author: Ville Syrjälä <ville.syrjala@linux.intel.com
>>> <mailto:ville.syrjala@linux.intel.com>>
>>> Date:   Wed Apr 13 21:19:51 2016 +0300
>>>
>>>      drm/i915: Clear VLV_IER around irq processing
>>
>> Argh. So somehow the broken commit [1] got into 4.6. We'll need to get
>> it reverted.
>>
>> [1] 9dbaab56ac09 ("drm/i915: Exit cherryview_irq_handler() after one
>> pass")
>
> git revert 9dbaab56ac09 works fine on my Ara X5 Plus.

I see patches being submitted to 4.6 stable now, is anyone on the 
graphics team planning to send a patch for this one or should I go ahead 
and do it?

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-05-31 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9066d799-b6d4-f0df-aa6f-4947bc47c5b1@linux.intel.com>
     [not found] ` <20160517181638.GR4329@intel.com>
     [not found]   ` <573BB2D6.2050507@linux.intel.com>
2016-05-18  7:08     ` i915 issues with 4.6 Ville Syrjälä
2016-05-18 20:53       ` Pierre-Louis Bossart
2016-05-31 18:10         ` Pierre-Louis Bossart [this message]

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=bd8da15f-3a14-c9fc-3ce7-c864de183709@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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