| Priority | medium |
|---|---|
| Bug ID | 79074 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | PRIME with compositing rednering hangs and other rendering issues |
| Severity | normal |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | haagch.christoph@googlemail.com |
| Hardware | Other |
| Status | NEW |
| Version | git |
| Component | Drivers/Gallium/radeonsi |
| Product | Mesa |
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) xorg server 1.15.1 stable, mesa, glamor, xf86-video-intel and xf86-video-ati from very recent git. I am "testing" with mass effect 1 in a 1920x1080 wine virtual desktop. The trouble is mainly with minimizing and restoring windows. OpenGL/GLX Compositing (kwin): I have still this issue https://bugs.freedesktop.org/show_bug.cgi?id=69101 So on the first start of the game the graphical output is (almost?) always stuck at the splash screen and I have to press the ctrl+alt+f12 hotkey to disable and re-enable compositing. When minimizing and restoring the window it has about 2/3 chance or so that it will not render and I have to minimize or disable/re-enable etc. Xrender Compositing with both compton --backend xrender and kwin: The above problem with not rendering does not happen with xrender compositing. Instead: When minimizing the wine window, the game will render over everything on all workspaces while minimized. I can provoke a graphical output hang when: 1. Use kwin with opengl compositing. 2. Minimize and restore until it hangs. 3. While it hangs, switch to compton --xrender. Then the graphical output and does *not* recover with disabling/reenabling compositing or minimizing/restoring multiple times, I have to kill it... The game itself doesn't hang, I can hear the results of input etc. It's just the graphical output. I have no idea how to try to debug this, but I will see if it is possible for me to find out more about why this happens.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
