Nouveau - May 2019 - [Bug 110669] New: iMac with GK107M unstable - hangs with xorg / crashes with xwayland

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

            Bug ID: 110669
           Summary: iMac with GK107M unstable - hangs with xorg / crashes
                    with xwayland
           Product: Mesa
           Version: 19.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: sjon at hortensius.net
        QA Contact: nouveau at lists.freedesktop.org

I'd like to start with noting this issue has been occurring for years on
most
of our iMacs and I strongly suspect this isn't necessarily
"caused" by nouveau
but rather by an implementation detail NVidia forgot to document (please remind
me why I keep buying their hardware?)

Hardware: Apple Inc. iMac13,2/Mac-FC02E91DDD3FA6A4, BIOS
IM131.88Z.010A.B05.1211151146 11/15/2012
Software: Archlinux / any nouveau release, currenty running xf86-video-nouveau
1.0.16-1

Using Xorg this iMac hangs maybe 2 or 3 times a day, using Xwayland (using
sway, a native wayland implementation) there actually is a backtrace and I have
a chance to reboot instead of kill the power. I'd love to help debug this
since
I assume it only happens when using this specific hardware. To start with -
here is a backtrace:

Stack trace of thread 765:
#0  0x00007f9374fe282f raise (libc.so.6)
#1  0x00007f9374fcd672 abort (libc.so.6)
#2  0x000055ef04386f6a n/a (Xwayland)
#3  0x000055ef0437f645 n/a (Xwayland)
#4  0x000055ef0438a7a6 n/a (Xwayland)
#5  0x00007f9374fe28b0 __restore_rt (libc.so.6)
#6  0x00007f9374fe282f raise (libc.so.6)
#7  0x00007f9374fcd672 abort (libc.so.6)
#8  0x00007f9375024e78 __libc_message (libc.so.6)
#9  0x00007f937502b78a malloc_printerr (libc.so.6)
#10 0x00007f937502d007 _int_free (libc.so.6)
#11 0x00007f936e02b7da nouveau_bo_ref (libdrm_nouveau.so.2)
#12 0x00007f9372866894 n/a (nouveau_dri.so)
#13 0x00007f9372a14c87 n/a (nouveau_dri.so)
#14 0x00007f93729d6604 n/a (nouveau_dri.so)
#15 0x00007f93729d9031 n/a (nouveau_dri.so)
#16 0x00007f93729dc5c8 n/a (nouveau_dri.so)
#17 0x000055ef0448d8d4 n/a (Xwayland)
#18 0x000055ef0449963d n/a (Xwayland)
#19 0x000055ef04404ec1 n/a (Xwayland)
#20 0x000055ef043e53c8 n/a (Xwayland)
#21 0x000055ef043e5933 n/a (Xwayland)
#22 0x000055ef04451270 n/a (Xwayland)
#23 0x000055ef0434b11d n/a (Xwayland)
#24 0x00007f9374fcece3 __libc_start_main (libc.so.6)
#25 0x000055ef0434c14e n/a (Xwayland)

Stack trace of thread 769:
#0  0x00007f93746f2bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f9372687474 n/a (nouveau_dri.so)
#2  0x00007f93726872c8 n/a (nouveau_dri.so)
#3  0x00007f93746eca92 start_thread (libpthread.so.0)
#4  0x00007f93750a5cd3 __clone (libc.so.6)

Stack trace of thread 771:
#0  0x00007f93746f2bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f9372687474 n/a (nouveau_dri.so)
#2  0x00007f93726872c8 n/a (nouveau_dri.so)
#3  0x00007f93746eca92 start_thread (libpthread.so.0)
#4  0x00007f93750a5cd3 __clone (libc.so.6)

Stack trace of thread 772:
#0  0x00007f93746f2bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f9372687474 n/a (nouveau_dri.so)
#2  0x00007f93726872c8 n/a (nouveau_dri.so)
#3  0x00007f93746eca92 start_thread (libpthread.so.0)
#4  0x00007f93750a5cd3 __clone (libc.so.6)

Stack trace of thread 768:
#0  0x00007f93746f2bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f9372cc81e4 n/a (nouveau_dri.so)
#2  0x00007f9372cc7f08 n/a (nouveau_dri.so)
#3  0x00007f93746eca92 start_thread (libpthread.so.0)
#4  0x00007f93750a5cd3 __clone (libc.so.6)

Stack trace of thread 770:
#0  0x00007f93746f2bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f9372687474 n/a (nouveau_dri.so)
#2  0x00007f93726872c8 n/a (nouveau_dri.so)
#3  0x00007f93746eca92 start_thread (libpthread.so.0)
#4  0x00007f93750a5cd3 __clone (libc.so.6)

-- 
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/20190513/474f57bd/attachment-0001.html>

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

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

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

--- Comment #1 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/1178.

-- 
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/20190918/bce30432/attachment.html>