From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 59057] New: Black screen after resume from s2ram
Date: Sat, 05 Jan 2013 15:06:28 +0000 [thread overview]
Message-ID: <bug-59057-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1430 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59057
Priority: medium
Bug ID: 59057
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Black screen after resume from s2ram
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: pontus.fuchs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Driver/nouveau
Product: xorg
Starting with 3.8rc1 I get a black screen when resuming after suspend.
The kernel is alive because I can switch to VT1 and reboot with
ctrl-alt-delete.
I bisected the problem down to this commit:
186ecad21: drm/nv50/disp: move remaining interrupt handling into core
Hardware is 8400M GS (10de:0427) in a Dell XPS M1330.
I see this in my kernel log after resume:
nouveau E[ PFB][0000:01:00.0] trapped read at 0x002001a020 on
channel 0x00007b23 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
nouveau E[ 1177] failed to idle channel 0xcccc0000
[TTM] Failed to expire sync object before buffer eviction
[TTM] Failed to expire sync object before buffer eviction
[TTM] Failed to expire sync object before buffer eviction
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2708 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 reply other threads:[~2013-01-05 15:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 15:06 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-59057-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-01-05 15:13 ` [Bug 59057] Black screen after resume from s2ram bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 19:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 19:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 20:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 20:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 20:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 20:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 20:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 22:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-05 23:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-06 20:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-06 20:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-06 20:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-06 21:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-06 23:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-07 19:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-07 19:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-07 21:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-10 19:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-10 20:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-10 20:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-12 15:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-13 9:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-23 16:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-20 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21 11:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21 11:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21 17:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-21 20:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 3:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-24 19:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-24 20:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-26 8:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-26 8:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-26 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-04 18:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-11 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-07 22:30 ` 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-59057-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.