http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c1 --- Comment #1 from Ludwig Nussel --- Created attachment 764848 --> http://bugzilla.opensuse.org/attachment.cgi?id=764848&action=edit error with drm-kmp-default -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c3 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt@suse.com --- Comment #3 from Max Staudt --- Hi Ludwig, Have you rebooted after removing drm-kmp-default? Can you please submit your dmesg and Xorg.0.log? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c5 --- Comment #5 from Ludwig Nussel --- due to the lockup the machine was rebooted several times, yes :) I'll try to get the logs (it's not my machine). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c7 --- Comment #7 from Stefan Dirsch --- (In reply to Max Staudt from comment #6)

It's a Gen4 machine, and IIRC there was a point before which resetting an Intel GPU didn't really work due to a hardware bug or something.

(adding Stefan in case he remembers more)

Yes, GPU hardware resets never worked. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c8 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com Flags| |needinfo?(lnussel@suse.com) --- Comment #8 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #7)

(In reply to Max Staudt from comment #6)

...

It's a Gen4 machine, and IIRC there was a point before which resetting an Intel GPU didn't really work due to a hardware bug or something.

(adding Stefan in case he remembers more)

Yes, GPU hardware resets never worked. ;-)

I mean GPU resets on older Intel GPUs. Ludwig, is this a desktop machine? Maybe a development machine even we received from Intel directly? It could be a machine with beta/alpha CPU/GPU revision still. In that case I would like to close this bugreport as INVALID. Seriously. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c10 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lnussel@suse.com) | --- Comment #10 from Stefan Dirsch --- Ok. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c12 --- Comment #12 from Ludwig Nussel --- Created attachment 765324 --> http://bugzilla.opensuse.org/attachment.cgi?id=765324&action=edit /var/log/gdm/:0.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c14 --- Comment #14 from Ludwig Nussel --- the logs are from the freshly booted system with no user logged in. The GPU only crashes when logging in (XFCE in this case). -- You are receiving this mail because: You are on the CC list for the bug.

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

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c16 --- Comment #16 from Max Staudt --- I've reproduced this, and both solutions that I've suggested resolve the issue when I try to start an X server manually. What may still be a problem is that GNOME, and maybe also KDE (?) are now Wayland sessions - and Wayland has similar requirements as the modsesetting DDX's acceleration. Thus, some Wayland sessions may fail to start your machine (though Weston works). My test system currently has GNOME on it, and thus it uses GDM as the login manager. Since GDM itself is already a Wayland application, it can't work. :( I've seen that you're trying to use KDE, and I don't know whether its SDDM login manager uses the Wayland model. I'll have to investigate. What should definitely work, after applying either of the fixes I suggested, is to change your display manager to lightdm at the bottom of /etc/sysconfig/displaymanager as well as start an XFCE session. Of course, this requires installing the XFCE stuff: zypper install lightdm xfce4-session Or, re-install Tumbleweed completely, and instead of selecting the KDE or GNOME desktop, pick XFCE in the advanced package selection. I'll check more in-depth once I'm back in a little over a week. (Note to other developers: If only everyone stuck to the reference Wayland compositor, which can render even to fbdev, instead of reinventing the wheel...) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c18 --- Comment #18 from Max Staudt --- Oh no, Comment 16 was actually meant to go into boo#1087063 - it's related to Gen3, not Gen4. I'm afraid I haven't reproduced *this* bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c20 --- Comment #20 from Max Staudt --- Actually, bringing in the machine would be very helpful. We're very short on Gen4 machines, and they definitely don't have your chip. Without a reproducer, there's nothing we can do. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086747 http://bugzilla.opensuse.org/show_bug.cgi?id=1086747#c24 --- Comment #24 from Ludwig Nussel --- I swear I saw this problem also without drm-kmp but can't reproduce currently anymore. Thanks anyways! -- You are receiving this mail because: You are on the CC list for the bug.