From: Chris <chrisengel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [Bug 53101] Fedora 17 "PFIFO - playlist update failed" on boot
Date: Thu, 9 Aug 2012 14:09:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20120809T160601-338@post.gmane.org> (raw)
In-Reply-To: bug-53101-8800-7hZx4f3xT8@http.bugs.freedesktop.org/
<bugzilla-daemon@...> writes:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=53101
>
> --- Comment #1 from mog55356@... 2012-08-03
> 18:54:38 UTC ---
> I was asked to try booting with option nouveau.noaccel=1. Grub didn't complain
> when I added it to the boot instructions, but the results were identical so I'm
> not sure whether or not the command "took." Below is a pastebin link to the new
> /var/log/messages. I hope it is useful.
>
> http://pastebin.com/t39ZHCwP
>
I'm hitting similar failures with the latest updates to F17 but only when I
attempt to come out of suspend. The initial boot works fine.
Aug 9 08:59:10 cengel kernel: [33296.674903] [drm] nouveau 0000:01:00.0: Failed
to idle channel 1.
Aug 9 08:59:12 cengel kernel: [33298.674948] [drm] nouveau 0000:01:00.0: 0x2634
!= chid: 0x00100001
Aug 9 08:59:14 cengel kernel: [33300.674816] [drm] nouveau 0000:01:00.0: PFIFO
- playlist update failed
Aug 9 08:59:17 cengel kernel: [33303.674113] [drm] nouveau 0000:01:00.0: Failed
to idle channel 2.
Aug 9 08:59:19 cengel kernel: [33305.674063] [drm] nouveau 0000:01:00.0: 0x2634
!= chid: 0x00100002
Aug 9 08:59:21 cengel kernel: [33307.673952] [drm] nouveau 0000:01:00.0: PFIFO
- playlist update failed
next prev parent reply other threads:[~2012-08-09 14:09 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 [this message]
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
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=loom.20120809T160601-338@post.gmane.org \
--to=chrisengel-re5jqeeqqe8avxtiumwx3w@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.