[Bug 92826] [BSW] Using multiple DP, can cause second output to blank until reboot by quickly transition cursor across screen border

[bugzilla-daemon at freedesktop.org]

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

--- Comment #8 from Jani Nikula <jani.nikula at intel.com> ---
(In reply to Jason Plum from comment #6)
> (In reply to Jani Nikula from comment #4)
> > Please try current drm-intel-nightly, add drm.debug=14 module parameter, and
> > attach the (plain text!) dmesg all the way from boot to reproducing the
> > problem. If the early boot doesn't fit in the buffer, please add
> > log_buf_len=4M (or larger) and try again.
> 
> I will rebuild and re-test.

Thanks.

> I will not pre-compress them this time. Might I ask why drm.debug=14 vs the
> drm.debug=0x1e that I have? (documentation purposes for my team)

It's a bit mask; see include/drm/drmP.h in the kernel tree for the bit
definitions. 0x10 is atomic modeset debugging; it's pretty verbose, I
personally prefer to not include that unless I think it's needed. Makes it
easier to read the logs without it, but others may have different
preferences...

> > (In reply to Jason Plum from comment #3)
> > > Bumped to high. This is blocking a product release
> > 
> > This bugzilla is best-effort only. If you have a support contract with
> > Intel, please escalate through your normal support channels.
> 
> Understood. I have sent my manufacturer this bug and they are going through
> said channels.

Thanks.

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