dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42960] Display does not work when resuming from suspend
Date: Tue, 18 Mar 2014 18:55:03 +0000	[thread overview]
Message-ID: <bug-42960-502-D26KSDOCY3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42960-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 518 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=42960

--- Comment #9 from Sandeep <sandy.8925@gmail.com> ---
I booted Linux 3.13.6 with the drm.debug=4 parameter - it looks like the
internal LVDS output is set to use a different CRTC than the HDMI output, even
in clone mode.

The LVDS monitor's backlight is also off, it does not switch on at all or get
enabled after suspend and resume. Only a full system restart will bring it back
to life.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1285 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-03-18 18:55 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 22:40 [Bug 42960] New: Display does not work when resuming from suspend bugzilla-daemon
2011-11-16 20:01 ` [Bug 42960] " bugzilla-daemon
2011-11-17  4:02 ` bugzilla-daemon
2011-11-17 14:16 ` bugzilla-daemon
2012-01-11 23:48 ` bugzilla-daemon
2012-01-29 14:27 ` bugzilla-daemon
2013-03-14 18:30 ` bugzilla-daemon
2014-02-18  1:24 ` bugzilla-daemon
2014-02-21 14:28 ` bugzilla-daemon
2014-03-18 18:55 ` bugzilla-daemon [this message]
2014-03-18 19:32 ` bugzilla-daemon
2014-03-20 21:50 ` bugzilla-daemon
2014-03-20 21:53 ` bugzilla-daemon
2014-03-28  2:58 ` bugzilla-daemon
2014-04-02  5:12 ` bugzilla-daemon
2014-04-03  2:24 ` bugzilla-daemon
2014-04-03  4:55 ` bugzilla-daemon
2014-04-03  5:36 ` bugzilla-daemon
2014-04-03  7:50 ` bugzilla-daemon
2014-04-03  7:55 ` bugzilla-daemon
2014-04-03  8:17 ` bugzilla-daemon
2014-04-03 20:01 ` bugzilla-daemon
2014-04-03 20:30 ` bugzilla-daemon
2014-04-03 21:42 ` bugzilla-daemon
2014-04-04  3:10 ` bugzilla-daemon
2014-04-04  4:06 ` bugzilla-daemon
2014-04-04  5:24 ` bugzilla-daemon
2014-04-04  6:45 ` bugzilla-daemon
2014-04-04 12:53 ` bugzilla-daemon
2014-04-04 16:09 ` bugzilla-daemon
2014-04-07  1:25 ` bugzilla-daemon
2014-04-07  2:06 ` bugzilla-daemon
2014-04-07 18:38 ` bugzilla-daemon
2014-04-09  6:06 ` bugzilla-daemon
2014-04-10 22:30 ` bugzilla-daemon
2014-04-10 22:44 ` bugzilla-daemon
2014-04-10 22:47 ` bugzilla-daemon
2014-04-12 17:15 ` bugzilla-daemon
2014-04-14 20:52 ` bugzilla-daemon
2014-04-17 12:49 ` bugzilla-daemon
2014-04-18 14:48 ` bugzilla-daemon
2014-04-18 23:16 ` bugzilla-daemon
2014-04-20 17:39 ` bugzilla-daemon
2014-04-21  5:26 ` bugzilla-daemon
2014-04-21 23:18 ` bugzilla-daemon
2014-04-24 16:41 ` bugzilla-daemon
2014-04-24 20:09 ` bugzilla-daemon
2014-04-25 13:55 ` bugzilla-daemon
2014-08-10 16:50 ` bugzilla-daemon
2014-09-13 10:05 ` bugzilla-daemon
2014-09-13 16:25 ` bugzilla-daemon
2014-09-16 10:49 ` bugzilla-daemon
2014-09-20  4:15 ` bugzilla-daemon
2014-09-22  4:09 ` bugzilla-daemon
2014-09-22  4:21 ` bugzilla-daemon
2014-11-04 18:03 ` bugzilla-daemon
2014-11-11 14:24 ` bugzilla-daemon
2014-12-18 10:11 ` bugzilla-daemon
2014-12-18 10:12 ` bugzilla-daemon
2015-02-11 23:40 ` bugzilla-daemon
2015-02-13  1:26 ` bugzilla-daemon
2015-02-13  1:34 ` bugzilla-daemon
2015-02-13  8:40 ` bugzilla-daemon
2015-02-13 17:45 ` bugzilla-daemon
2015-02-17  9:59 ` bugzilla-daemon
2015-02-17 14:43 ` bugzilla-daemon
2015-02-22  2:20 ` bugzilla-daemon

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-42960-502-D26KSDOCY3@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).