On Thu, 2014-07-31 at 23:47 +0200, Ian Kumlien wrote:
On tor, 2014-07-31 at 14:39 +0300, Imre Deak wrote:
On Wed, 2014-07-30 at 22:52 +0200, Ian Kumlien wrote:
Sorry for the delay, it's been damned hot - vacation is over and
overtime has been all the rage at work...
No problem,
On Fri, Aug 1, 2014 at 3:16 PM, Imre Deak imre.d...@intel.com wrote:
[--8--]
Ok, I see the trace of suspend/resume now, but the bug has vanished.. I
can't see the WARN backtrace in your original report, nor the debug
message from the above fix, that would indicate that it had fixed
anything
On Wed, 2014-07-30 at 22:52 +0200, Ian Kumlien wrote:
Sorry for the delay, it's been damned hot - vacation is over and
overtime has been all the rage at work...
No problem, thanks for the feedback.
On fre, 2014-07-25 at 12:28 +0300, Imre Deak wrote:
On Thu, 2014-07-24 at 01:33 +0200, Ian
On Thu, 2014-07-24 at 01:33 +0200, Ian Kumlien wrote:
Try four, now including CC lists for the intel driver...
Could you give a try to the 2 patches at:
https://patchwork.kernel.org/patch/4437061/
If these don't fix the issue, could you send a full dmesg log with the
drm.debug=14 kernel option
On fre, 2014-07-25 at 12:28 +0300, Imre Deak wrote:
On Thu, 2014-07-24 at 01:33 +0200, Ian Kumlien wrote:
Try four, now including CC lists for the intel driver...
Could you give a try to the 2 patches at:
https://patchwork.kernel.org/patch/4437061/
If these don't fix the issue, could you
