From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 55227] New: GeForce GTX 560 Ti fails to resume
Date: Sat, 22 Sep 2012 23:47:21 +0000 [thread overview]
Message-ID: <bug-55227-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=55227
Bug #: 55227
Summary: GeForce GTX 560 Ti fails to resume
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: brgerst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 67563
--> https://bugs.freedesktop.org/attachment.cgi?id=67563
Nouveau kernel log
Linux 3.6.0-rc6
Fedora 17
GeForce GTX 560 Ti
After a suspend/resume cycle, the screen comes back with random pixels in the
framebuffer, and these messages in the kernel log:
[drm] nouveau 0000:04:00.0: PFIFO: read fault at 0x00085b1000
[PAGE_NOT_PRESENT] from PCOPY0/PCOPY0 on channel 0x00000c8000
[drm] nouveau 0000:04:00.0: PFIFO: unknown status 0x40000000
[drm] nouveau 0000:04:00.0: nv50cal_space: -16
The last message repeats indefinitely. The cursor appears as normal, and moves
with the mouse, so the X server doesn't appear to be locked up.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-09-22 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 23:47 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-55227-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-10-05 2:23 ` [Bug 55227] GeForce GTX 560 Ti fails to resume bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-20 14:02 ` 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-55227-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.