[Bug 98810] [g4x] Desktop hang with drm:drm_atomic_helper_commit_cleanup_done "flip_done timed out"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=98810

--- Comment #27 from Carey Underwood <cwillu at cwillu.com> ---
Okay, thanks for finding that commit, I'll check it later today.  (got a
discrete card to work around this a while ago as it was my main work
machine at the time.)

On Mon, Apr 23, 2018, 07:03 <bugzilla-daemon at freedesktop.org> wrote:

> Ville Syrjala <ville.syrjala at linux.intel.com> changed bug 98810
> <https://bugs.freedesktop.org/show_bug.cgi?id=98810>
> What Removed Added
> Resolution --- FIXED
> Status REOPENED RESOLVED
>
> *Comment # 26 <https://bugs.freedesktop.org/show_bug.cgi?id=98810#c26> on
> bug 98810 <https://bugs.freedesktop.org/show_bug.cgi?id=98810> from Ville
> Syrjala <ville.syrjala at linux.intel.com> *
>
> (In reply to Leho Kraav (:macmaN :lkraav) from comment #22 <https://bugs.freedesktop.org/show_bug.cgi?id=98810#c22>)> (Dell 7480, Intel HD 620 rev 02)
> > ```
> > apr   21 10:55:54 papaya kernel: [drm:drm_atomic_helper_wait_for_flip_done
> > [drm_kms_helper]] *ERROR* [CRTC:37:pipe A] flip_done timed out
> > ```
> >
> > It does seem like REOPENED is the correct status here?
>
> That's totally different hw than the orignal bug report. So please open a new
> bug for that if you're still seeing the problem with current kernels.
>
> As for the original problem I suspect it was fixed by:
>
> commit e38c2da01f76cca82b59ca612529b81df82a7cc7
> Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
> Date:   Mon Jun 26 23:30:51 2017 +0300
>
>     drm/i915: Disable MSI for all pre-gen5
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180423/0ea8de0f/attachment.html>