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

            Bug ID: 109341
           Summary: Plasma Wayland locks up immediately on sign in
           Product: Mesa
           Version: 18.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: blocker
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: etna-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 143094
  --> https://bugs.freedesktop.org/attachment.cgi?id=143094&action=edit
dmesg immediately after lockup

Hello Nouveau devs:

I'm facing an issue where attempting to sign into a Wayland Plasma session
causes the entire GUI to lock up immediately. Under some circumstances, I can
still SSH into the unit, but i usually can't do much before even the SSH
session locks up as well.

STEPS TO REPRODUCE
1. Boot computer
2. Sign in to Plasma (Wayland) at SDDM

OBSERVED RESULT
Machine instantly locks up. Sometimes, I might be able to SSH in, but dmesg
only prints a bunch of Nouveau FIFO engine fault errors 

EXPECTED RESULT
PLasma Wayland session starts normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Leap 15.0
(available in About System)
KDE Plasma Version: 5.12

ADDITIONAL INFORMATION
I have done the following as well:

- Upgrade the default OpenSUSE kernel to a vanilla 4.18 kernel from kernel.org.
Lockup still occurs upon sign in
- Upgrade the default 
- Tested a Wayland session with Gnome successfully
- Upgraded Plasma to 5.14 with the repo recommended by OpenSUSE here and lockup
still occurs
- Booted with nouveau.noaccel=1 and Plasma Wayland successfully loads but with
terrible performance

This issue was reported to the Plasma bug tracker and they closed it on the
grounds that anything which causes a system lockup is operates much lower than
the DE and should thus be filed with Nouveau.

Attached dmesg and session logs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.