From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 71659] [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000
Date: Thu, 09 Jan 2014 21:25:51 +0000 [thread overview]
Message-ID: <bug-71659-8800-flZDK7FvTM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71659-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 722 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71659
--- Comment #10 from Rebecca Palmer <R.Palmer-mHdZ94l+r7K1Qrn1Bg8BZw@public.gmane.org> ---
Created attachment 91782
--> https://bugs.freedesktop.org/attachment.cgi?id=91782&action=edit
Ubuntu 14.04 (Linux 3.13.0) log
This bug is easier to trigger in Ubuntu Trusty (kernel 3.13.0, libdrm-nouveau2
2.4.50, xserver-xorg-video-nouveau 1.0.10, mesa 10.0.1), occurring immediately
on heavy graphics load and within a few minutes even in ordinary use.
The attached log contains more instances of the warning than were normal in
13.10, but not the final error (I suspect it wasn't synced to disk).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1684 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:[~2014-01-09 21:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 20:14 [Bug 71659] New: [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-71659-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-15 20:16 ` [Bug 71659] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 23:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-27 5:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09 21:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-01-09 21:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 20:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 20:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-13 23:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 3:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 9:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 9:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 19:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-29 21:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 20:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 20:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 23:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-20 22:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-20 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-22 4:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 10:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-02 22:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-12 21:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-22 14:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-01 23:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:40 ` 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-71659-8800-flZDK7FvTM@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