From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 20341] NV31 lockup
Date: Sun, 25 Aug 2013 03:56:55 +0000 [thread overview]
Message-ID: <bug-20341-8800-OcykYYl303@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-20341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=20341
--- Comment #16 from Jason Detring <detringj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Created attachment 84575
--> https://bugs.freedesktop.org/attachment.cgi?id=84575&action=edit
Valgrind mmap trace log
Attaching valgrind mmap trace log.
Notes:
- Prior to testing the kernel was upgraded to nouveau/linux-2.6 master @
3b56bba6abaa70d629fccdcf8490e087ea3a1ab4 "drm/nv04/disp: fix framebuffer pin
refcounting" 2013-08-21 01:37:09 (GMT)
- The agpmode=0 noveau.ko parameter was removed.
- X was especially slow during the test, as expected. This corresponds to the
note on valgrind-mmt's wiki page: "tracing slows down Xorg considerably - ~20x"
- X did not crash during this test. The test procedure was conducted 5 times
to ensure the system didn't have a spurious nonfailure.
- This is a huge logfile. It will expand to ~220 MB when decompressed. This
log covers only the first test instance.
- Rerunning the test without valgrind caused the usual lockup.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1949 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 prev parent reply other threads:[~2013-08-25 3:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 1:51 [Bug 20341] New: NV31 lockup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-20341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-02-27 1:51 ` [Bug 20341] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-27 1:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 3:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 4:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 4:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 4:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 17:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-20 4:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 7:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 4:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-17 15:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 5:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 8:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 15:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 3:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-25 4:04 ` [Bug 20341] [NV31] lockup when using AGP. agpmode=0 fixes it bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 15:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 15:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-26 23:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 5:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-19 15:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-21 1:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 7:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09 0:23 ` 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-20341-8800-OcykYYl303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox