Nouveau - Jan 2019 - [Bug 109341] New: Plasma Wayland locks up immediately on sign in

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 at lists.freedesktop.org
          Reporter: etna at linuxmail.org
        QA Contact: nouveau at lists.freedesktop.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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/d0b68fe5/attachment.html>

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

etna at linuxmail.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |etna at linuxmail.org

--- Comment #1 from etna at linuxmail.org ---
Created attachment 143095
  --> https://bugs.freedesktop.org/attachment.cgi?id=143095&action=edit
wayland-session.log immediately after the lockup

wayland-session.log immediately after the lockup

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/ff94452a/attachment-0001.html>

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

--- Comment #2 from etna at linuxmail.org ---
Created attachment 143096
  --> https://bugs.freedesktop.org/attachment.cgi?id=143096&action=edit
Attempted a backtrace. Not sure of its usefullness.

Attempted a backtrace. Not sure of its usefullness.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/da76fc9f/attachment.html>

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

--- Comment #3 from etna at linuxmail.org ---
By the way, this happens with the bundled Mesa 18.0.2 and my self-built Mesa
18.0.5.

I cannot use any version of Mesa above 18.0.x due to OpenSUSE's Wayland
being
too old.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/3360a971/attachment.html>

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

etna at linuxmail.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|blocker                     |major

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/2b7e0cac/attachment.html>

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

--- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Unfortunately nouveau doesn't do well with concurrent multi-threaded GL
usage.
The PBDMA errors, I believe, may be indicators of something like that.

I believe plasma added some logic to avoid doing that, at least on top of
nouveau (or perhaps that was Qt).

There's also some pending work to improve the multi-threaded situation for
nouveau, but that won't do you much good on a year-old version of mesa.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190114/9e8b8a36/attachment.html>

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

--- Comment #5 from etna at linuxmail.org ---
Do you mean to say that this issue 'should' not appear on newer releases
of
Mesa?

Reason being on my current setup Gnome Wayland and Weston are working fine
under Mesa 18.0.5. It's just Plasma Wayland causing the lockups.

I also tested running a nested Wayland session in Weston and then starting a
Plasma Wayland session in that nested session. No dice; locks up the system as
well. :(

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190115/68eaa4aa/attachment.html>

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

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to etna from comment #5)
> Do you mean to say that this issue 'should' not appear on newer
releases of
> Mesa?
> 
> Reason being on my current setup Gnome Wayland and Weston are working fine
> under Mesa 18.0.5. It's just Plasma Wayland causing the lockups.
> 
> I also tested running a nested Wayland session in Weston and then starting
a
> Plasma Wayland session in that nested session. No dice; locks up the system
> as well. :(
No. I'm saying that there are patches that improve nouveau's handling of
multi-threaded GL usage, but they're against latest mesa version, not
something
older.

Plasma + nouveau have, generally, not played very well together.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190115/decfa935/attachment.html>

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

--- Comment #7 from etna at linuxmail.org ---
That's unfortunate. 

As I cannot just up and change my installation, do you have any information on
what combination of Mesa + Plasma Wayland is known to successfully work?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190115/09c4d64c/attachment.html>

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

GitLab Migration User <gitlab-migration at fdo.invalid> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |MOVED

--- Comment #8 from GitLab Migration User <gitlab-migration at
fdo.invalid> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1166.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190918/309385ae/attachment-0001.html>