All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Dorsch <ml@bokomoko.de>
To: intel-gfx@lists.freedesktop.org
Subject: CRT not detected via hotplug on resume
Date: Wed, 21 Sep 2011 14:23:01 +0200	[thread overview]
Message-ID: <201109211423.01278.ml@bokomoko.de> (raw)

Hello,

after resuming my graphics card sometimes does not come up (see my post 
yesterday).

Comparing drm outputs with drm.debug=6 in syslog reveals among others 

	[drm:intel_crt_detect], CRT not detected via hotplug hotplug"

Does that mean that the monitor (EIZO FlexScan L767) is not reliably detected?

Is that a know problem? Does it make sense to open a bug report?

As a workaround can I enforce that a signal is always driven (it is a desktop, 
the monitor is always there!). Or can enforce that the check is repeated once 
or twice, if it fails (that should bring the probability down)?

Here the full diff (for *1303* the resume was not working):

rd@blackbox:~/tmp.nobackup$ diff -u syslog-intel.drm-1303.part syslog-
intel.drm-1340.part 
--- syslog-intel.drm-1303.part  2011-09-21 13:52:26.103280388 +0200
+++ syslog-intel.drm-1340.part  2011-09-21 13:54:31.949381096 +0200
@@ -9,14 +9,6 @@
 [drm:drm_crtc_helper_set_config], 
 [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:17] #connectors=1 (x y) (0 0)
 [drm:drm_crtc_helper_set_config], [CONNECTOR:8:HDMI-A-1] to [CRTC:3]
-[drm:intel_crt_detect], CRT not detected via hotplug
-[drm:output_poll_execute], [CONNECTOR:5:VGA-1] status updated from 2 to 2
-[drm:intel_sdvo_debug_write], SDVOB: W: 0B                         
(SDVO_CMD_GET_ATTACHED_DISPLAYS)
-[drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
-[drm:intel_sdvo_detect], SDVO response 1 0 [1]
-[drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      
(SDVO_CMD_SET_CONTROL_BUS_SWITCH)
-[drm:intel_sdvo_debug_write], SDVOB: W: 7A 02                      
(SDVO_CMD_SET_CONTROL_BUS_SWITCH)
-[drm:output_poll_execute], [CONNECTOR:8:HDMI-A-1] status updated from 1 to 1
 [drm:i915_get_vblank_counter], trying to get vblank count for disabled pipe B
 [drm:intel_opregion_setup], graphic opregion physical addr: 0xcf78e0f4
 [drm:intel_opregion_setup], Public ACPI methods supported
@@ -97,10 +89,8 @@
 [drm:drm_mode_debug_printmodeline], Modeline 13:"640x480" 60 25200 640 656 
752 800 480 490 492 525 0x40 0xa
 [drm:drm_mode_debug_printmodeline], Modeline 14:"720x400" 70 28320 720 738 
846 900 400 412 414 449 0x40 0x6
 [drm:drm_mode_getconnector], [CONNECTOR:8:?]
-[drm:drm_mode_addfb], [FB:24]
 [drm:intel_crtc_cursor_set], 
-[drm:drm_mode_addfb], [FB:21]
-[drm:drm_mode_addfb], [FB:24]
+[drm:drm_mode_addfb], [FB:25]
 [drm:intel_crt_detect], CRT not detected via hotplug
 [drm:output_poll_execute], [CONNECTOR:5:VGA-1] status updated from 2 to 2
 [drm:intel_sdvo_debug_write], SDVOB: W: 0B                         
(SDVO_CMD_GET_ATTACHED_DISPLAYS)
rd@blackbox:~/tmp.nobackup$ man diff
rd@blackbox:~/tmp.nobackup$ man diff
rd@blackbox:~/tmp.nobackup$ man diff
rd@blackbox:~/tmp.nobackup$ scp  syslog-intel
syslog-intel~                syslog-intel.drm             syslog-
intel.drm-1303.part   syslog-intel.drm-1340.part   
syslog-intel                 syslog-intel.drm-1303        syslog-
intel.drm.1340        
rd@blackbox:~/tmp.nobackup$

Full log is here

        http://bokomoko.de/~rd/syslog-drm.6

around 13:03 the resume was not detecting the monitor, around 13:40 the resume 
was detecting the monitor.


Thanks,
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

             reply	other threads:[~2011-09-21 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 12:23 Rainer Dorsch [this message]
2011-09-21 15:31 ` CRT not detected via hotplug on resume Keith Packard
2011-09-21 16:15   ` Rainer Dorsch
2011-09-21 16:22     ` Simon Farnsworth
2011-09-21 17:09     ` Keith Packard
2011-09-22  8:36       ` Rainer Dorsch
2011-09-22 14:33         ` Keith Packard
2011-09-23 19:05           ` Rainer Dorsch
2011-09-24  5:29             ` Keith Packard
2011-10-22 18:41               ` Rainer Dorsch
2011-09-24  8:59 Rainer Dorsch

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=201109211423.01278.ml@bokomoko.de \
    --to=ml@bokomoko.de \
    --cc=intel-gfx@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 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.