[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Nov 8 10:58:21 UTC 2017


--- Comment #7 from EoD <EoD at xmw.de> ---
(In reply to Michel Dänzer from comment #6)
> (In reply to EoD from comment #5)
> > The patch avoids the crash, but the 2ndary screen does not change. It just
> > stays active (power LED is on) with a blank screen.
> Does that only happen when using xf86-video-intel for the Intel GPU, or also
> when using modesetting? If the former, it sounds like a separate issue in
> xf86-video-intel.

With and w/o the patch, there no problems when I use modesetting instead of

Does this mean it's clearly an Intel issue now? Even w/o the patch?

I also asked on IRC and more or less these lines were the last ones regarding
the issue:
20:55 ickle: I wasn't expecting 0  
21:21 ickle: more perplexing, we don't use screen->devPrivates 
21:22 ickle: amdgpu_glamor_flush() is flushing the wrong pScrn 
21:23 ickle: amdgpu's screen/scrn is 0xd66150/0xbfad60, the one it pasted to
glamor is 0xbfc650/0xd4fa10

I think the "expecting 0" is a "expecting 0 for glamor_priv".

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x.org/archives/xorg-driver-ati/attachments/20171108/b67bad7b/attachment.html>

More information about the xorg-driver-ati mailing list