From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 83550] New: [NVA5] Monitor not restored after resume [regression]
Date: Sat, 06 Sep 2014 02:07:33 +0000 [thread overview]
Message-ID: <bug-83550-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1842 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83550
Priority: medium
Bug ID: 83550
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [NVA5] Monitor not restored after resume [regression]
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: anka.213.bacn+freedesktop-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 105823
--> https://bugs.freedesktop.org/attachment.cgi?id=105823&action=edit
vbios.rom
I have a GT216 [GeForce 210] (rev a2). I have two monitors, one connected with
DVI, the other with VGA. In revisions after 415f12efc1b only the one connected
to VGA will restore after suspend.
I need to apply
[ba5e01b0d0146c2d2bb5475cf1d6efec51bf2669] drm/nv50/disp: fix a potential oops
in supervisor handling
to make it restore at all in 415f12efc1b..ba5e01b0d^. Otherwise the computer
completely fails to resume. (The computer wakes up but is completely
unresponsive. Both monitors are off. Pressing the keyboard makes the num-lock
key blink once and nothing more. This is the same behaviour it has when the
computer is suspended. The only difference is that the power light is not
blinking.)
xrandr seems to think that the screen was restored properly.
> lspci
01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce 210] (rev
a2)
> git bisect log
# first bad commit: [415f12efc1b2308411b2cbc3e82666b3db8a7758] drm/nv50/disp:
start removing direct vbios parsing from supervisor
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3310 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-09-06 2:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 2:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-83550-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-09-06 2:39 ` [Bug 83550] [NVA5] Monitor not restored after resume [regression] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-06 2:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-06 3:20 ` [Bug 83550] [NVA5] Monitor not restored after resume [regression] [bisected] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 16:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 16:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-19 16:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-19 16:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-22 9:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-22 9:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-22 9:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-30 1:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-30 22:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-30 22:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-01 23:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-01 23:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 18:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-06 16:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-06 16:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 4:26 ` 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-83550-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.