Nouveau - Feb 2017 - [Bug 99968] New: [NV4C] System crashes reliably with glxinfo

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

            Bug ID: 99968
           Summary: [NV4C] System crashes reliably with glxinfo
           Product: Mesa
           Version: 12.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: dmo2118 at gmail.com
        QA Contact: nouveau at lists.freedesktop.org
                CC: laurent.riffard+freedesktop at free.fr,
                    nouveau at lists.freedesktop.org
        Depends on: 91992

Created attachment 129920
  --> https://bugs.freedesktop.org/attachment.cgi?id=129920&action=edit
Example display corruption

+++ This bug was initially created as a clone of Bug #91992 +++

Hardware is NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) on an
old Dell Inspiron 531. Integrated graphics.

The system boots OK (with high-resolution console) into X11. I can log in to a
Lubuntu desktop (2D, no OpenGL, AFAIK). Then, from a terminal window I run:

$ while true; do nice -n19 glxinfo > /dev/null; done

Then I drag the window around for a few seconds. Then the entire system
crashes: total system lockup, followed by display corruption a second or two
later. (I've attached a photograph, because I can't take a normal screen
shot.)
No Ctrl-Alt-F1, no magic SysRq, no ping response.

Other OpenGL apps (i.e. glxgears) can run...sometimes. Other times, they crash
the same way. It seems to happen on GL init.

Ubuntu 16.10 (with Lubuntu Desktop)
Linux kernel        4.10.0          (freshly compiled)
libdrm              2.4.70-1        (from distro)
Mesa                12.0.3-1ubuntu2 (from distro)
xf86-video-nouveau  1:1.0.12-2      (from distro)

This seems a lot like bug 91992, but I've got my video memory cranked up to
256
MB in the BIOS settings, and it still happens.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=91992
[Bug 91992] [NV4C] computer hangs after few minutes of use
-- 
You are receiving this mail because:
You are on the CC list for the bug.
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/20170226/6af4f41f/attachment.html>

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

--- Comment #1 from Dave Odell <dmo2118 at gmail.com> ---
Created attachment 129921
  --> https://bugs.freedesktop.org/attachment.cgi?id=129921&action=edit
dmesg

Kernel messages, partially from dmesg, and partially from netconsole.

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

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

--- Comment #2 from Dave Odell <dmo2118 at gmail.com> ---
Created attachment 129922
  --> https://bugs.freedesktop.org/attachment.cgi?id=129922&action=edit
Xorg.0.log

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

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

--- Comment #3 from Dave Odell <dmo2118 at gmail.com> ---
Created attachment 129923
  --> https://bugs.freedesktop.org/attachment.cgi?id=129923&action=edit
VBIOS

Obtained via /sys/bus/pci/devices/0000:00:04.0/rom, as described in
<https://nouveau.freedesktop.org/wiki/DumpingVideoBios/>.

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

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

--- Comment #4 from Stewart Martin <stewartjmartin at gmail.com> ---
Same, or similar, problem on Linux Mint 19.1 Cinnamon, with the same graphics
chipset.  The method I was using to reliably recreate the crash was to run
glxdemo and then resize the window.

However, the symptoms did occur at other times.  I turned off hardware
acceleration in chrome in an attempt to prevent it.  

Using "nouveau.config=NvMSI=0" as suggested here
https://bugs.freedesktop.org/show_bug.cgi?id=61321 made no difference.

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

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

--- Comment #5 from Dave Odell <dmo2118 at gmail.com> ---
Tried again on the same hardware with Linux 5.0-rc8, and it's not any
better.
But now on top of that I've got intermittent system pauses, probably
associated
with "rcu_sched detected stalls on CPUs/tasks" that I see in dmesg.
That's
probably unrelated to the problem at hand.

Resizing the glxdemo window repeatedly does it for me, too.

nouveau.config=NvMSI=0 didn't help me, either.

A twist: I normally run this machine with modprobe.blacklist=nouveau, but it
still happened (while running Linux 4.15.0-20 from Ubuntu)...except this time
the system hadn't crashed, and CTRL-ALT-F1 (to get to tty1) followed by
CTRL-ALT-F7 (to get back to X11) restored video.

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

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

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

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

--- Comment #6 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/1128.

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