From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 83168] New: No display after suspend to RAM
Date: Thu, 28 Aug 2014 00:19:27 +0000 [thread overview]
Message-ID: <bug-83168-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1967 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83168
Priority: medium
Bug ID: 83168
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: No display after suspend to RAM
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: nsajko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 105362
--> https://bugs.freedesktop.org/attachment.cgi?id=105362&action=edit
the kernel log
When Linux resumes after suspension to RAM, I get no display until next
boot, but the backlight is on. I think this was true since I started
using this distro, but I rarely tried to use suspend.
This happens invariantly to Xorg.
Although my hardware is 64-bit, I use a 32-bit Linux.
Software versions:
* Linux 3.16.1
* libdrm 2.4.56
* mesa 10.2.6
* xf86-video-nouveau 1.0.10
nouveau reports errors like these to kernel log when the display should
turn back on:
[ 153.783362] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00001e00 FAULT
at 0x6813c8
[ 153.788735] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00002e00 FAULT
at 0x6813c8
[ 153.791840] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0xf5153d80 FAULT
at 0x6813c8
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3361 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:[~2014-08-28 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 0:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-83168-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-08-28 0:27 ` [Bug 83168] No display after suspend to RAM bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 0:31 ` [Bug 83168] [NV46] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 2:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 2:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 17:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 17:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-28 18:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-31 22:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-31 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:48 ` 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-83168-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.