[Bug 104975] Delay in skl_disable_plane() causes a system freeze

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 23 20:58:54 UTC 2018


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

--- Comment #63 from Azhar <azhar.shaikh at intel.com> ---
(In reply to Ville Syrjala from comment #62)
> (In reply to Ville Syrjala from comment #61)
> > (In reply to Ville Syrjala from comment #60)
> > > (In reply to Azhar from comment #59)
> > > > (In reply to Ville Syrjala from comment #58)
> > > > > It looks like I managed to avoid the planes staying on past their bedtime
> > > > > with the following branch:
> > > > > git://github.com/vsyrjala/linux.git double_buffer_ctl_ddb_wa
> > > > > 
> > > > > I hope it will also prevent the hard hangs. Please test.
> > > > 
> > > > 
> > > > With this patch on Linux-stable 4.15.18 without the support of IPC on BXT+,
> > > > still causes hard hangs.
> > > 
> > > Argh. OK, so looks like what I had there is only sufficient for linear
> > > buffers for some unknown reason. To make the planes appear to work correctly
> > > with tiled buffers I had to frob the double buffer disable bits some more
> > > between the ddb/wm and plane programming steps.
> > > 
> > > I pushed an additional commit to the same branch:
> > > git://github.com/vsyrjala/linux.git double_buffer_ctl_ddb_wa
> > > 
> > > Please test again.
> > 
> > Actually never mind. I still seems to fail here. Just makes a bit harder to
> > hit :(
> 
> OK, yet another commit pushed. So far this is showing a bit more promise
> here. I'll leave it running overnight to see if it ends up tripping over
> later.


With the patches on the double_buffer_ctl_ddb_wa branhc, on Linux-stable
4.15.18 and without the support of IPC on BXT+, still causes hard hangs.

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


More information about the intel-gfx-bugs mailing list