From: Jim Rees <rees@umich.edu>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm: refernce count event->completion
Date: Thu, 9 Feb 2017 14:09:41 -0500 [thread overview]
Message-ID: <20170209190941.GA11649@rees.org> (raw)
In-Reply-To: <20170209172029.fkmco4meu5q2ydfw@phenom.ffwll.local>
Daniel Vetter wrote:
Latest report just says that the revert isn't helping either. I suspect
the report is a giantic conflagration of everything ever that kills
various reporters boxes. I still believe that the patch here fixes the
original bug, but there might be a lot more hiding.
It's at least seen quite a pile of testing, so I think it's sounds, and we
could cherry-pick it to dinf with cc: stable for 4.9+. Worst case it's not
going to help for the other problems.
No, that's not what the latest report says. It says, "running for 2 weeks
... This is certainly way, way better than the current stock experience,
which results in my T460s entirely locking up daily." and "Less than a day
after I made that comment I got a hard lockup". So reverting the buggy
helper nonblock tracking commit took this reporter from locking up daily to
locking up once in two weeks. For everyone else, reverting the buggy commit
fixes all bugs. Also note that this most recent lockup appears to be a
different bug ("GPU HANG: ecode").
So we have a commit that is causing hard lockups and flip_done timeouts for
multiple users. Reverting this commit fixes the problem. But we did not push
the revert up for 4.9, and it looks like we're not going to push it up for
4.10 either.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-09 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 10:23 [PATCH 1/2] drm: refernce count event->completion Daniel Vetter
2016-12-21 10:23 ` [PATCH 2/2] drm: Add kernel-doc for drm_crtc_commit_get/put Daniel Vetter
2016-12-21 13:03 ` [PATCH] " Daniel Vetter
2017-01-04 16:11 ` Daniel Vetter
2017-01-04 20:26 ` Alex Deucher
2017-01-05 7:55 ` Daniel Vetter
2016-12-22 3:11 ` [Intel-gfx] [PATCH 2/2] " kbuild test robot
2016-12-21 10:36 ` [PATCH 1/2] drm: refernce count event->completion Chris Wilson
2016-12-21 11:08 ` Maarten Lankhorst
2017-01-04 10:05 ` Daniel Vetter
2017-02-09 14:39 ` Jani Nikula
2017-02-09 17:20 ` Daniel Vetter
2017-02-09 19:09 ` Jim Rees [this message]
2016-12-21 12:18 ` Daniel Vetter
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=20170209190941.GA11649@rees.org \
--to=rees@umich.edu \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).