http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c2 --- Comment #2 from Martin Caj --- Created attachment 662040 --> http://bugzilla.suse.com/attachment.cgi?id=662040&action=edit the /var/log/Xorg.0.log file from time of the crash -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #662039|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c5 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mcaj@suse.com) | --- Comment #5 from Egbert Eich --- Ok, found it. There is actually an upstram patch for this: commit 90db5edf119187f8b1b9207c8c384d6cd7ef9edc Author: Dave Airlie Date: Tue Jun 30 14:54:42 2015 +1000 prime: add rotation support for offloaded outputs (v2) One of the lacking features with output offloading was that screen rotation didn't work at all. The bad new is, that this will break the ABI. Therefore this won't happen for any released openSUSE. In TW this is already fixed. I will however submit a patch which disables rotation for GPU screens. This will keep things from accidentally crashing. Hint: If you switch the screens around, the other one should rotate without any issues. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c10 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msrb@suse.com) | --- Comment #10 from Michal Srb --- (In reply to Egbert Eich from comment #9)

@Michal, you had an issue with prime before and were positive that rotating the GPU screen on anything past 13.2 would not cause a crash. Can you check, why it didn't crash for you? Did the driver provide rotation in this case?

I am not sure why it doesn't crash, but driver rotation doesn't seem to be the case. I retested with what I have available right now: * 13.2: nouveau as master and intel as slave - rotation doesn't crash, some rendering artifacts visible * 13.2: nouveau as master and modesetting (udl) as slave - rotation doesn't crash, some rendering artifacts visible * 42: nouveau as master and modesetting (udl) as slave - rotation crashes exactly as described in this bug So something got (more) broken from 13.2 to 42. Good that it's already fixed in TW at least. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c21 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(strzol@gmail.com) --- Comment #21 from Egbert Eich --- (In reply to Stratos Zolotas from comment #20)

Hello,

Applying this patch created a new regression for me. I'm using a setup with 2 monitors connected on a radeon VGA and a third one connected on an additional radeon vga.

Applying this patch disabled the third monitor (on the second radeon vga). Although the monitor is activated during boot as soon as I login to KDE it stays black.

Reverting to the previous xorg version fixes the issue immediately.

I can provide any log that maybe is useful to pinpoint this issue but you have to guide me on what exactly will help.

I bet this just needs to be fixed in the KDE display setup tool. At least provide some useful information. Provide the output of 'xrandr -q'. Try activating the 3rd display using xrandr and provide the output of 'xrandr -q' again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c24 --- Comment #24 from Stratos Zolotas --- I'm not spotting any difference between the "working" output from xrandr (when running with the previous xorg version) and the new where the monitor stays black (with the new xorg version). It seems that the monitor is enabled but stays black. I can even move windows to it and it is displayed correctly on the KDE settings where I have configured the layout of the three monitors. Can you please provide the command to force enable it with xrandr? I'm attaching the output of xrandr -q, the monitor that stays black is the VGA-1-1. Stratos. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c26 --- Comment #26 from Egbert Eich --- (In reply to Stratos Zolotas from comment #24)

I'm not spotting any difference between the "working" output from xrandr (when running with the previous xorg version) and the new where the monitor stays black (with the new xorg version).

It seems that the monitor is enabled but stays black. I can even move windows to it and it is displayed correctly on the KDE settings where I have configured the layout of the three monitors.

Can you please provide the command to force enable it with xrandr?

I'm attaching the output of xrandr -q, the monitor that stays black is the VGA-1-1.

Stratos.

You're right. Everything looks ok, but it is not lit. Should be fixed now, though. Until there is an official release, you can find it at: http://download.opensuse.org/repositories/home:/eeich:/branches:/OBS_Maintai... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=962295 http://bugzilla.suse.com/show_bug.cgi?id=962295#c29 --- Comment #29 from Egbert Eich --- (In reply to Stratos Zolotas from comment #28)

I confirm!

New package solves the issue. Kudos for the great job Egbert.

Thank you - and thank you for pointing this out and verifying the fix afterwards! -- You are receiving this mail because: You are on the CC list for the bug.