Nouveau - Aug 2015 - [Bug 91632] New: Crash in nouveau

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

            Bug ID: 91632
           Summary: Crash in nouveau
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: kde at carewolf.com
        QA Contact: nouveau at lists.freedesktop.org

I have been looking into why QtWebEngine crashes with the nouveau driver, but
the crashes appears asserts in the driver and not our code.

Any idea about what could trigger it:


#3  0x00007ffff0f032d2 in __GI___assert_fail
(assertion=assertion at entry=0x7fffe1d77aa9 "kref", 
    file=file at entry=0x7fffe1d77a8a "../../nouveau/pushbuf.c",
line=line at entry=726, 
    function=function at entry=0x7fffe1d77ad0 <__PRETTY_FUNCTION__.6213>
"nouveau_pushbuf_data") at assert.c:101
#4  0x00007fffe1d76284 in nouveau_pushbuf_data (push=push at entry=0x598d40,
bo=0x5ace30, offset=115624, length=20)
    at ../../nouveau/pushbuf.c:726
#5  0x00007fffe1d761cb in nouveau_pushbuf_data (push=push at entry=0x598d40,
bo=bo at entry=0x0, offset=offset at entry=0, 
    length=length at entry=0) at ../../nouveau/pushbuf.c:718
#6  0x00007fffe1d762ea in pushbuf_submit (push=push at entry=0x598d40,
chan=<optimized out>, chan=<optimized out>)
    at ../../nouveau/pushbuf.c:329
#7  0x00007fffe1d7656e in pushbuf_flush (push=push at entry=0x598d40) at
../../nouveau/pushbuf.c:404
#8  0x00007fffe1d77180 in nouveau_pushbuf_kick (push=0x598d40,
chan=<optimized
out>) at ../../nouveau/pushbuf.c:778
#9  0x00007fffe246d766 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#10 0x00007fffe2182024 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
<snip>
#15 0x00007ffff1cda345 in glXMakeCurrentReadSGI () from
/usr/lib/x86_64-linux-gnu/libGL.so.1

-- 
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:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150814/0a40d854/attachment.html>

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

Allan Sandfeld <kde at carewolf.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Crash in nouveau            |Assert in
                   |                            |nouveau_pushbuf_data

-- 
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:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150814/c1b26e61/attachment.html>

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

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
I've seen that a few times... My analysis was that there's a fixed
number of
GEM objects and we're running out of them. Which means that the GPU is
either
locked up or way way WAY behind. However I haven't confirmed any part of
this... just based on reading the code. In my case, the GPU was, in fact,
locking up.

-- 
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:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150824/f9e1374a/attachment.html>

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

--- Comment #2 from Allan Sandfeld <kde at carewolf.com> ---
The original qtwebengine bug is at https://bugreports.qt.io/browse/QTBUG-41242

One interesting thing I discovered was that using the EGL/GLES mode instead of
GLX/GL solved the issue. I assume at your level it shouldn't be that
different.
So it could be a difference in how EGL vs GLX acts.

-- 
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:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150824/ace60b21/attachment.html>

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

--- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Allan Sandfeld from comment #2)
> The original qtwebengine bug is at
> https://bugreports.qt.io/browse/QTBUG-41242
> 
> One interesting thing I discovered was that using the EGL/GLES mode instead
> of GLX/GL solved the issue. I assume at your level it shouldn't be that
> different. So it could be a difference in how EGL vs GLX acts.
The issue was happening for me with Unigine Heaven run with DRI3 + DRI_PRIME=1.
Then I started running it with vblank_mode=0 and all my problems disappeared. I
haven't checked whether removing vblank_mode=0 would cause the issues to
reappear. I was happy to blame it on the DRI3 boogeyman and moved on (I tend
not to have a good grasp on these types of issues in the first place...
normally I wouldn't touch DRI3 but it really makes nouveau dev quite a bit
easier with a primary non-nvidia adapter since I can load/unload nouveau/nvidia
at will and still have things display on my regular screen).

Not sure how vsync would cause the problems, but I was getting actual shader
traps reported in dmesg. Do you (or whoever is having the issue) have that 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:
<http://lists.freedesktop.org/archives/nouveau/attachments/20150824/99ec2237/attachment.html>

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

--- Comment #4 from Tomasz Paweł Gajc <tpgxyz at gmail.com> ---
Hi,

any news on this issue ?

I'm running quite fresh system (OpenMandriva Lx 3.0) with:
Qt 5.6.1
Mesa 12.0-rc4
libdrm 2.4.68
kernel 4.62

gfx card nv92

and Qupzilla 2.01 crashes for me with this error 


[tpg at lazur ~]$ LC_ALL=C qupzilla
QupZilla: 0 extensions loaded
Uncaught TypeError: Cannot read property 'restoreData' of null
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch10: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch10: buf 00000000 00000002 00000004 00000004 00000000
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch10: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch10: buf 00000000 00000002 00000004 00000004 00000000
ATTENTION: default value of option force_s3tc_enable overridden by environment.
QupZilla: Starting with profile 'default'
QupZilla: 0 extensions loaded
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch11: krec 0 pushes 0 bufs 2 relocs 0
nouveau: ch11: buf 00000000 00000002 00000004 00000004 00000000
nouveau: ch11: buf 00000001 00000006 00000004 00000000 00000004
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch11: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch11: buf 00000000 00000002 00000004 00000004 00000000
qupzilla: pushbuf.c:727: void nouveau_pushbuf_data(struct nouveau_pushbuf *,
struct nouveau_bo *, uint64_t, uint64_t): Warunek zapewnienia `kref' nie
został
spełniony.

-- 
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/20160628/b5d7b86e/attachment.html>

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

--- Comment #5 from Francesco Turco <fturco at fastmail.fm> ---
I can't start the Qupzilla web browser because of a crash, and the problem
seems to be related to nouveau. I can run qupzilla just file if I use the
--disable-gpu commandline option. Please see
https://github.com/QupZilla/qupzilla/issues/2046 for the original bug I
submitted. I'm going to attach the qupzilla gdb backtrace. I'm using
mesa-12.0.1-5 on a Parabola GNU/Linux-libre system.

-- 
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/20160730/d87aeebe/attachment.html>

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

--- Comment #6 from Francesco Turco <fturco at fastmail.fm> ---
Created attachment 125441
  --> https://bugs.freedesktop.org/attachment.cgi?id=125441&action=edit
gdb backtrace for qupzilla

-- 
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/20160730/1afac579/attachment.html>

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

--- Comment #7 from Andrés Becerra Sandoval <andres.becerra at gmail.com>
---
Created attachment 125493
  --> https://bugs.freedesktop.org/attachment.cgi?id=125493&action=edit
backtrace with symbol tables

- Made with gdb with the command: thread apply all bt full
- Packages versions (on a Gentoo system):
www-client/qupzilla-2.0.1
x11-drivers/xf86-video-nouveau-1.0.12
media-libs/mesa-12.0.1
x11-libs/libdrm-2.4.70
dev-qt/qtwebengine-5.6.1

-- 
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/20160802/23163564/attachment.html>

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

--- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Unfortunately "this" issue is a lot of potential issues. The current
leading
cause of such errors, assuming an up-to-date libdrm/etc, is multithreading in
the application. Nouveau does not handle this well.

I have a branch which tries to address this:

https://github.com/imirkin/mesa/commits/locking

However it's not quite there yet (although it's a good part of the way
there),
and needs a rethink on some of the core mechanisms used. Unfortunately the
libdrm_nouveau api is really not well-suited to multithreading, kicks can end
up resulting implicitly from all kinds of seemingly innocuous actions.

-- 
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/20160802/e07a49b6/attachment.html>

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

--- Comment #9 from Reuben <reuben.m at gmail.com> ---
(In reply to Ilia Mirkin from comment #8)
> Unfortunately "this" issue is a lot of potential issues. The
current leading
> cause of such errors, assuming an up-to-date libdrm/etc, is multithreading
> in the application. Nouveau does not handle this well.
> 
This may not be "all the way there", but I can confirm a significantly
more
stable experience with qtwebengine.

-- 
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/20160803/0896bf09/attachment.html>

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

--- Comment #10 from Allan Sandfeld <kde at carewolf.com> ---
As a matter of fact QtWebEngine does use multithreading. Chromium renders in
one thread, and Qt composites in another.

-- 
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/20160803/e97059a7/attachment.html>

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

Tomasz Paweł Gajc <tpgxyz at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |98039

--- Comment #11 from Tomasz Paweł Gajc <tpgxyz at gmail.com> ---
Looks like this is a well known issue, see related bug for more info.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=98039
[Bug 98039] KMail crash on starting (nouveau-related)
-- 
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/20161210/7533d591/attachment.html>

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

Ilia Mirkin <imirkin at alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|98039                       |


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=98039
[Bug 98039] KMail crash on starting (nouveau-related)
-- 
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/20161211/16bca470/attachment.html>

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

--- Comment #12 from Andrey <andrey.aleksandrovich at googlemail.com> ---
Same here with qupzilla. But Chromium is working fine.

-- 
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/20170501/cc2b4da5/attachment.html>

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

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

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

--- Comment #13 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/1080.

-- 
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/da7bc2e6/attachment-0001.html>