Nouveau - Jan 2014 - [Bug 73274] New: NV44A (PCI) 3D screensaver CACHE_ERROR

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

          Priority: medium
            Bug ID: 73274
          Assignee: nouveau at lists.freedesktop.org
           Summary: NV44A (PCI) 3D screensaver CACHE_ERROR
        QA Contact: xorg-team at lists.x.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: freedesktop at phillipsjk.ca
          Hardware: x86 (IA32)
            Status: NEW
           Version: 7.7 (2011)
         Component: Driver/nouveau
           Product: xorg

Created attachment 91478
  --> https://bugs.freedesktop.org/attachment.cgi?id=91478&action=edit
dmesg output with bubble3d running ~16 hours (with one interruption)

Computer failed second-stage burn-in testing. Was able to run mprime with
blended tests overnight. Running the 3D screensaver (initially pinion) with
mprime doing "in place FFTs" (loads CPU, cache, little memory): caused
X to
crash. Lightdm restarted it automatically, but I had no mouse pointer.

I then upgraded all of the relevant software to newer versions:
Package: xorg Version: 1:7.7+5
Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1
Package: libdrm-nouveau2 Version: 2.4.50-1
Package: libgl1-mesa-dri Version: 9.2.2-1
Package: xscreensaver-gl Version: 5.23-1

 uname -a
Linux torchlight 3.11-2-686-pae #1 SMP Debian 3.11.10-1 (2013-12-04) i686
GNU/Linux

Running bubble3d with mprime doing "in place FFTs", I get a soft
lock-up within
about 30 minutes. I switched to bubble3d because the screen with the mouse
pointer was experiencing ~50% slow-downs even if the pointer was not drawn (it
gives info about the gear under the pointer). All the GL screen savers also
seem to suffer significant slow-downs with the option to display the frame-rate
enabled. On the order of 20->5 fps. This slowdown was not as evident prior to
the upgrade (so may be a regression).

When running bubble3d for about 16 hours, with the computer otherwise idle, I
logged two sets of Cache errors. However, without the soft lock-up. I plan to
test with an ATI card to see the problems may be related to power stability
rather than software. The motherboard is now about 10 years old, so the
capacitors may be drying out.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140104/f22b3e90/attachment.html>

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

--- Comment #1 from James Phillips <freedesktop at phillipsjk.ca> ---
Created attachment 91479
  --> https://bugs.freedesktop.org/attachment.cgi?id=91479&action=edit
reconstructed dmesg from kern.log after soft lock-up.

Not only was this too long for dmesg, but I accidentally hit the power button
on the keyboard. I trimmed the relevant kern.log to capture the relevant data.

The soft-lock up happened within about 30 minutes (based on saved IRC logs). I
did not intervene for hours (explaining the repeated messages).

There really were two instances of bubble3d running: one for each display. One
appears to complain about the cache error, while the other complains about the
resulting CPU lock-up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140104/50a96d1c/attachment.html>

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

Martin Peres <martin.peres at free.fr> changed:

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

--- Comment #2 from Martin Peres <martin.peres at free.fr> ---
-- 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/xorg/driver/xf86-video-nouveau/issues/84.

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