From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91954] New: "link training failed": nouveau does not recover from monitor suspend
Date: Thu, 10 Sep 2015 03:07:55 +0000 [thread overview]
Message-ID: <bug-91954-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2332 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91954
Bug ID: 91954
Summary: "link training failed": nouveau does not recover from
monitor suspend
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: djc-vNUPr3c+39GHXe+LvDLADg@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
When my monitor wakes up from "power save mode" (DPMS suspend) nouveau does not
display any output and the monitor goes back to power save after a few seconds.
The kernel says:
kernel: nouveau E[ PDISP][0000:03:00.0][0x00000006] 02:0006:0f42: link
training failed
The behaviour of the monitor might be a bit dodgy. When booting the machine I
have to mash buttons on the monitor to keep it awake until the firmware starts
displaying an image, otherwise I will get no output from the firmware at all.
When the monitor goes into power save mode, it stays awake showing a message
"Power save mode" for about 3 seconds, then it actually powers down (its LED
turns orange). I have noticed that nouveau can recover if I shake the mouse
during those three seconds, but it can't recover if I let the monitor power all
the way down.
Complete logs to follow.
Hardware:
Lenovo Thinkstation P500, all legacy/CSM features disabled ("pure UEFI")
Nvidia Quadro K620 (GM107/NV117)
Thinkvision 2840m connected via Displayport
Software:
xorg-x11-server-Xorg-1.17.2-2.fc22.x86_64
xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64
Kernel is 4.2.0 plus Fedora patches plus these four commits suggested by Ben
Skeggs:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-4.3&id=7c11c99b3c66a8e03494e56ce6e6c5303ee85934
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-4.3&id=f10956d4455fcb24ecbdca30e6d9d88c95dc2588
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-4.3&id=fe0f5d08806dcf7fd51092dfc6ea666ea2392692
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-4.3&id=2a89359415da2fc1250b4c205de3c384bd781f54
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4125 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-09-10 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 3:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-91954-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-09-10 3:10 ` [Bug 91954] "link training failed": nouveau does not recover from monitor suspend bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-10 5:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-20 16:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-17 13:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-04 13:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-24 9:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-26 10:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-03-02 21:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-08 20:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-17 22:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-06 12:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-27 2:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:03 ` 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-91954-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.