From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73274] New: NV44A (PCI) 3D screensaver CACHE_ERROR
Date: Sat, 04 Jan 2014 07:56:53 +0000 [thread overview]
Message-ID: <bug-73274-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2377 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73274
Priority: medium
Bug ID: 73274
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: NV44A (PCI) 3D screensaver CACHE_ERROR
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: freedesktop-bmuJXYsvn0ihgqps0qF2+Q@public.gmane.org
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.
[-- Attachment #1.2: Type: text/html, Size: 3911 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-01-04 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 7:56 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-73274-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-04 8:06 ` [Bug 73274] NV44A (PCI) 3D screensaver CACHE_ERROR bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-73274-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.