From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 53101] Fedora 17 "PFIFO - playlist update failed" on boot
Date: Fri, 24 Aug 2012 02:34:33 +0000 [thread overview]
Message-ID: <bug-53101-8800-cbLx61uSmo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-53101-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=53101
--- Comment #11 from Kelly Doran <kel.p.doran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2012-08-24 02:34:33 UTC ---
I have been playing around with this a bit and made some progress. It seems to
affect any nvc0 card (I have a GTX 580). I went through the commits between
3.4.0 and 3.5.0-rc1 and determined that the cause of the error is
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=1a46098e910b96337f0fe3838223db43b923bad4
The cards work fine with the latest nouveau git tree if you comment out:
{ "COPY1", 5, 0x90b8, nvc0_bo_move_copy, nvc0_bo_move_init },
{ "COPY0", 4, 0x90b5, nvc0_bo_move_copy, nvc0_bo_move_init },
which seems to imply that the nvc0_bo_move_copy function is not working
correctly. I don't know nearly enough about nouveau to try to fix this
function or know what consequence commenting out these lines has, but hopefully
this helps.
On a possibly related note, running glxinfo seems to crash xorg and produce
some more PFIFO errors in dmesg, I have no idea if this is related to those
lines being commented out or not (this is the first time I have ever gotten
nouveau working on this computer). Everything else seems stable... so far...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-08-24 2:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 17:53 [Bug 53101] New: Fedora 17 "PFIFO - playlist update failed" on boot bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-53101-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-08-03 18:54 ` [Bug 53101] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-09 14:09 ` Chris
2012-08-15 17:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-15 17:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-18 23:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-21 19:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-21 19:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-21 19:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-21 22:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-22 5:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-22 6:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-24 2:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-08-25 17:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-25 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-25 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-25 18:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-25 20:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-17 16:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-28 11:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-28 11:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 7:16 ` [Bug 53101] [NVC0+] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-12 6:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-29 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-29 16:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-16 23:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:28 ` 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-53101-8800-cbLx61uSmo@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.