All of lore.kernel.org
 help / color / mirror / Atom feed
* CRT not detected via hotplug on resume
@ 2011-09-21 12:23 Rainer Dorsch
  2011-09-21 15:31 ` Keith Packard
  0 siblings, 1 reply; 11+ messages in thread
From: Rainer Dorsch @ 2011-09-21 12:23 UTC (permalink / raw)
  To: intel-gfx

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/

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-21 12:23 CRT not detected via hotplug on resume Rainer Dorsch
@ 2011-09-21 15:31 ` Keith Packard
  2011-09-21 16:15   ` Rainer Dorsch
  0 siblings, 1 reply; 11+ messages in thread
From: Keith Packard @ 2011-09-21 15:31 UTC (permalink / raw)
  To: Rainer Dorsch, intel-gfx


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

On Wed, 21 Sep 2011 14:23:01 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> 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?

No, your monitor is not connected on a VGA cable, but an HDMI (or DVI)
cable through an SDVO card.

I don't see any visible differences between the two resume sequences.

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

I haven't heard of any trouble with resume on SVDO cards, but I also
don't know many machines using this.

Note that there's some review going on that supports hot-plug on SDVO
connected HDMI displays; it's possible that might help in your case, so
you might want to try that patch.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-21 15:31 ` Keith Packard
@ 2011-09-21 16:15   ` Rainer Dorsch
  2011-09-21 16:22     ` Simon Farnsworth
  2011-09-21 17:09     ` Keith Packard
  0 siblings, 2 replies; 11+ messages in thread
From: Rainer Dorsch @ 2011-09-21 16:15 UTC (permalink / raw)
  To: Keith Packard; +Cc: intel-gfx

Keith,

many thanks for the quick and useful reply.

Am Wednesday, 21. September 2011 schrieb Keith Packard:
> On Wed, 21 Sep 2011 14:23:01 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> > 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?
> 
> No, your monitor is not connected on a VGA cable, but an HDMI (or DVI)
> cable through an SDVO card.

Indeed, that is true.

> I don't see any visible differences between the two resume sequences.

Hmm...that is bad news. 

Since I can ssh into the machine, when the problem occurs, are there some 
diagnosis scripts/tools I could run?

> > Is that a know problem? Does it make sense to open a bug report?
> 
> I haven't heard of any trouble with resume on SVDO cards, but I also
> don't know many machines using this.
> 
> Note that there's some review going on that supports hot-plug on SDVO
> connected HDMI displays; it's possible that might help in your case, so
> you might want to try that patch.

Are you refereing to the mail from Simon from yesterday:

[Intel-gfx] [PATCHv5] drm/i915: Enable SDVO hotplug interrupts for HDMI and 
DVI

?

Do you expect that it can be applied to a Linux 3.0 kernel?

Thanks again,
Rainer

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

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-21 16:15   ` Rainer Dorsch
@ 2011-09-21 16:22     ` Simon Farnsworth
  2011-09-21 17:09     ` Keith Packard
  1 sibling, 0 replies; 11+ messages in thread
From: Simon Farnsworth @ 2011-09-21 16:22 UTC (permalink / raw)
  To: intel-gfx

On Wednesday 21 September 2011, Rainer Dorsch <ml@bokomoko.de> wrote:
> 
> Are you refereing to the mail from Simon from yesterday:
> 
> [Intel-gfx] [PATCHv5] drm/i915: Enable SDVO hotplug interrupts for HDMI and
> DVI
> 
> ?
> 
> Do you expect that it can be applied to a Linux 3.0 kernel?
> 
I've just sent a v6 of that patch - it should apply cleanly to a 3.0 kernel, 
as the only other change since 3.0 in that file is Akshay Joshi's whitespace 
cleanup.
-- 
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  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
  1 sibling, 1 reply; 11+ messages in thread
From: Keith Packard @ 2011-09-21 17:09 UTC (permalink / raw)
  To: Rainer Dorsch; +Cc: intel-gfx


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

On Wed, 21 Sep 2011 18:15:27 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:

> Since I can ssh into the machine, when the problem occurs, are there some 
> diagnosis scripts/tools I could run?

Hrm. As far as I can tell, we're turning on the monitor successfully.

You might try playing with xrandr over ssh to make sure the system
thinks the monitor is running, then try turning it off and back on to
see if it lights up.

> Do you expect that it can be applied to a Linux 3.0 kernel?

yes, give v6 of the patch a try if you like; it will at least eliminate
the 10-second polling of your device, which won't suck.

Let me know if it actually helps your suspend/resume issues.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-21 17:09     ` Keith Packard
@ 2011-09-22  8:36       ` Rainer Dorsch
  2011-09-22 14:33         ` Keith Packard
  0 siblings, 1 reply; 11+ messages in thread
From: Rainer Dorsch @ 2011-09-22  8:36 UTC (permalink / raw)
  To: Keith Packard; +Cc: intel-gfx

Am Wednesday, 21. September 2011 schrieb Keith Packard:
> On Wed, 21 Sep 2011 18:15:27 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> > Since I can ssh into the machine, when the problem occurs, are there some
> > diagnosis scripts/tools I could run?
> 
> Hrm. As far as I can tell, we're turning on the monitor successfully.
> 
> You might try playing with xrandr over ssh to make sure the system
> thinks the monitor is running, then try turning it off and back on to
> see if it lights up.
> 
> > Do you expect that it can be applied to a Linux 3.0 kernel?
> 
> yes, give v6 of the patch a try if you like; it will at least eliminate
> the 10-second polling of your device, which won't suck.

I applied it and built. Although I am pretty sure, that the patch is included 
in the built kernel, Is there an easy way to validate that the patch is really 
included in the kernel?

This kind of output I do not see in the syslog anymore during regular 
operation now (is that the 10-second polling?):

Sep 22 09:25:58 blackbox kernel: [41988.264136] [drm:output_poll_execute], 
[CONNECTOR:5:VGA-1] status updated from 2 to 2
Sep 22 09:25:58 blackbox kernel: [41988.264139] [drm:intel_sdvo_debug_write], 
SDVOB: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
Sep 22 09:25:58 blackbox kernel: [41988.266996] 
[drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
Sep 22 09:25:58 blackbox kernel: [41988.272117] [drm:intel_sdvo_detect], SDVO 
response 1 0 [1]
Sep 22 09:25:58 blackbox kernel: [41988.272121] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:25:58 blackbox kernel: [41988.277823] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:25:58 blackbox kernel: [41988.331077] [drm:output_poll_execute], 
[CONNECTOR:8:HDMI-A-1] status updated from 1 to 1
Sep 22 09:26:08 blackbox kernel: [41998.344065] [drm:intel_crt_detect], CRT 
not detected via hotplug
Sep 22 09:26:08 blackbox kernel: [41998.344069] [drm:output_poll_execute], 
[CONNECTOR:5:VGA-1] status updated from 2 to 2
Sep 22 09:26:08 blackbox kernel: [41998.344073] [drm:intel_sdvo_debug_write], 
SDVOB: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
Sep 22 09:26:08 blackbox kernel: [41998.346928] 
[drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
Sep 22 09:26:08 blackbox kernel: [41998.352327] [drm:intel_sdvo_detect], SDVO 
response 1 0 [1]
Sep 22 09:26:08 blackbox kernel: [41998.352331] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:26:08 blackbox kernel: [41998.365324] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:26:08 blackbox kernel: [41998.418677] [drm:output_poll_execute], 
[CONNECTOR:8:HDMI-A-1] status updated from 1 to 1
Sep 22 09:26:18 blackbox kernel: [42008.456018] [drm:intel_crt_detect], CRT 
not detected via hotplug
Sep 22 09:26:18 blackbox kernel: [42008.456023] [drm:output_poll_execute], 
[CONNECTOR:5:VGA-1] status updated from 2 to 2
Sep 22 09:26:18 blackbox kernel: [42008.456027] [drm:intel_sdvo_debug_write], 
SDVOB: W: 0B                         (SDVO_CMD_GET_ATTACHED_DISPLAYS)
Sep 22 09:26:18 blackbox kernel: [42008.458900] 
[drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
Sep 22 09:26:18 blackbox kernel: [42008.463907] [drm:intel_sdvo_detect], SDVO 
response 1 0 [1]
Sep 22 09:26:18 blackbox kernel: [42008.465590] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:26:19 blackbox kernel: [42008.474405] [drm:intel_sdvo_debug_write], 
SDVOB: W: 7A 02                      (SDVO_CMD_SET_CONTROL_BUS_SWITCH)
Sep 22 09:26:19 blackbox kernel: [42008.527805] [drm:output_poll_execute], 
[CONNECTOR:8:HDMI-A-1] status updated from 1 to 1


just these messages are left

Sep 22 10:28:51 blackbox kernel: [  454.725402] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:28:51 blackbox kernel: [  454.765622] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:28:55 blackbox kernel: [  458.500948] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:28:55 blackbox kernel: [  458.526514] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:28:55 blackbox kernel: [  458.550393] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:28:55 blackbox kernel: [  458.575057] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:28:55 blackbox kernel: [  458.591470] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:28:58 blackbox kernel: [  461.028958] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:28:58 blackbox kernel: [  461.647929] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:28:59 blackbox kernel: [  462.239917] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:01 blackbox kernel: [  464.473398] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:01 blackbox kernel: [  464.473401] [drm:intel_crtc_cursor_set], 
cursor off
Sep 22 10:29:05 blackbox kernel: [  468.123755] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:24 blackbox kernel: [  487.733920] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:24 blackbox kernel: [  487.733923] [drm:intel_crtc_cursor_set], 
cursor off
Sep 22 10:29:25 blackbox kernel: [  488.916750] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:31 blackbox kernel: [  494.066445] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:31 blackbox kernel: [  494.066448] [drm:intel_crtc_cursor_set], 
cursor off
Sep 22 10:29:37 blackbox kernel: [  500.581494] [drm:intel_crtc_cursor_set], 
Sep 22 10:29:44 blackbox kernel: [  507.530714] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:29:46 blackbox kernel: [  509.739071] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:46 blackbox kernel: [  509.771637] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:29:46 blackbox kernel: [  509.791881] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:46 blackbox kernel: [  509.809341] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:29:46 blackbox kernel: [  509.825489] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:46 blackbox kernel: [  509.842508] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:29:46 blackbox kernel: [  509.859454] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:46 blackbox kernel: [  509.876596] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:29:46 blackbox kernel: [  509.893746] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:29:47 blackbox kernel: [  510.921999] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:30:04 blackbox kernel: [  527.865405] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:30:04 blackbox kernel: [  527.913576] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:30:05 blackbox kernel: [  527.951193] [drm:drm_mode_addfb], [FB:18]
Sep 22 10:30:05 blackbox kernel: [  527.992412] [drm:drm_mode_addfb], [FB:21]
Sep 22 10:30:09 blackbox kernel: [  532.298081] [drm:intel_crtc_cursor_set], 
Sep 22 10:30:09 blackbox kernel: [  532.298084] [drm:intel_crtc_cursor_set], 
cursor off
Sep 22 10:30:34 blackbox kernel: [  557.530754] [drm:intel_crtc_cursor_set], 
Sep 22 10:30:41 blackbox kernel: [  564.646592] [drm:intel_crtc_cursor_set], 
Sep 22 10:30:41 blackbox kernel: [  564.646595] [drm:intel_crtc_cursor_set], 
cursor off
Sep 22 10:31:40 blackbox kernel: [  623.605144] [drm:intel_crtc_cursor_set], 


> Let me know if it actually helps your suspend/resume issues.

So far the patch at least did not break anything visible to me :-) Since I 
cannot reproduce the suspend/resume issues reliably, this takes now some time. 
If I will have not seen it within the next two weeks, the problem is fixed or 
at least improved.

Many thanks,
Rainer

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

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-22  8:36       ` Rainer Dorsch
@ 2011-09-22 14:33         ` Keith Packard
  2011-09-23 19:05           ` Rainer Dorsch
  0 siblings, 1 reply; 11+ messages in thread
From: Keith Packard @ 2011-09-22 14:33 UTC (permalink / raw)
  To: Rainer Dorsch; +Cc: intel-gfx


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

On Thu, 22 Sep 2011 10:36:12 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:

> This kind of output I do not see in the syslog anymore during regular 
> operation now (is that the 10-second polling?):

Yes. So, the patch is definitely included.

> > Let me know if it actually helps your suspend/resume issues.
> 
> So far the patch at least did not break anything visible to me :-) Since I 
> cannot reproduce the suspend/resume issues reliably, this takes now some time. 
> If I will have not seen it within the next two weeks, the problem is fixed or 
> at least improved.

Thanks for testing this patch.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-22 14:33         ` Keith Packard
@ 2011-09-23 19:05           ` Rainer Dorsch
  2011-09-24  5:29             ` Keith Packard
  0 siblings, 1 reply; 11+ messages in thread
From: Rainer Dorsch @ 2011-09-23 19:05 UTC (permalink / raw)
  To: Keith Packard; +Cc: intel-gfx

Am Donnerstag 22 September 2011, 16:33:46 schrieb Keith Packard:
> On Thu, 22 Sep 2011 10:36:12 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> > This kind of output I do not see in the syslog anymore during regular
> 
> > operation now (is that the 10-second polling?):
> Yes. So, the patch is definitely included.

Thanks for confirming this.
 
> > > Let me know if it actually helps your suspend/resume issues.
> > 
> > So far the patch at least did not break anything visible to me :-) Since
> > I cannot reproduce the suspend/resume issues reliably, this takes now
> > some time. If I will have not seen it within the next two weeks, the
> > problem is fixed or at least improved.
> 
> Thanks for testing this patch.

The patch runs stable for me so far. But I hit the suspend/resume issue again. 
When I ssh into the machine, I get through xrandr

rd@blackbox:~$ xrandr -display :0
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
   1280x1024      60.0*+
   1024x768       60.0  
   800x600        60.3  
   640x480        60.0  
   720x400        70.1  
rd@blackbox:~$

which looks ok fo me. I tried to switch to another resolution, but the machine 
autosuspended, before I was able to do so (I took me a few minutes to figure 
out a copy and paste problem :-( ). After the second resume, HDMI was working 
again.

xrandr shows the same data after the second resume:

rd@blackbox:~$ xrandr -display :0
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm 
x 301mm
   1280x1024      60.0*+
   1024x768       60.0  
   800x600        60.3  
   640x480        60.0  
   720x400        70.1  
rd@blackbox:~$ 

Are there any other data I could gather to figure out what is going wrong?

Thanks,
Rainer

BTW, I start thinking on workarounds. One workaround would be to immediately 
suspend the system again, when I hit the problem. Since only graphics seems to 
be affected, I am thinking of "blindly" switching to a VT enter the root 
password and run pm-suspend. What I am worried about is that I have to enter 
the root password blindly. Are there better ways to manually suspend (without 
booting up another system and sshing in)? Could a cron script (e.g. running 
once a minute) detect the situation (but how, xrandr output seems to be ok)?

Many thanks,
Rainer

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-23 19:05           ` Rainer Dorsch
@ 2011-09-24  5:29             ` Keith Packard
  2011-10-22 18:41               ` Rainer Dorsch
  0 siblings, 1 reply; 11+ messages in thread
From: Keith Packard @ 2011-09-24  5:29 UTC (permalink / raw)
  To: Rainer Dorsch; +Cc: intel-gfx


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

On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:

> Are there any other data I could gather to figure out what is going
> wrong?

Oh, have we gotten register dumps from a working vs non-working resume?

        git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools

Let's hope there's some difference...

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
  2011-09-24  5:29             ` Keith Packard
@ 2011-10-22 18:41               ` Rainer Dorsch
  0 siblings, 0 replies; 11+ messages in thread
From: Rainer Dorsch @ 2011-10-22 18:41 UTC (permalink / raw)
  To: Keith Packard; +Cc: intel-gfx

Keith,

sorry for the late reply, but it took until now until the problem came back.

My problem was that with my G35 (GMA X3500)

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated 
Graphics Controller (rev 03) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 8276
        Flags: bus master, fast devsel, latency 0, IRQ 44
        Memory at fe800000 (32-bit, non-prefetchable) [size=1M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at cc00 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>
        Kernel driver in use: i915


SDVO did not come up after resume in rare cases, i.e. the screen stays black 
(machine is fine, login via ssh is no problem at all):

http://lists.freedesktop.org/archives/intel-gfx/2011-September/012132.html

Now I got a register dump from a clean resume:

http://bokomoko.de/~rd/GMA3500-black-screen/intel_reg_dump-20111022-working-
screen.dump

and a not working resume

http://bokomoko.de/~rd/GMA3500-black-screen/intel_reg_dump-20111022-black-
screen.dump

Here is the diff of the register dumps, a few registers are different:

blackbox:~# diff -u intel_reg_dump-20111022-working-screen.dump 
intel_reg_dump-20111022-black-screen.dump
--- intel_reg_dump-20111022-working-screen.dump 2011-10-22 18:17:31.740634880 
+0200
+++ intel_reg_dump-20111022-black-screen.dump   2011-10-22 18:14:10.651270448 
+0200
@@ -1,4 +1,4 @@
-                 DCC: 0x00100008 ( �y�d����cz�T�����v�H���d�{�)
+                 DCC: 0x00100008 ( �|�t����}�d���z�X��d�~�)
            CHDECMISC: 0x000000ac (XOR bank/rank, ch2 enh disabled, ch1 enh 
enabled, ch0 enh enabled, flex disabled, ep not present)
               C0DRB0: 0x00100008 (0x0008)
               C0DRB1: 0x00180010 (0x0010)
@@ -51,18 +51,18 @@
              DSPAPOS: 0x00000000 (0, 0)
             DSPASIZE: 0x00000000 (1, 1)
             DSPABASE: 0x00000000
-            DSPASURF: 0x0144c000
+            DSPASURF: 0x0e4eb000
          DSPATILEOFF: 0x00000000
            PIPEACONF: 0xc0000000 (enabled, active)
             PIPEASRC: 0x04ff03ff (1280, 1024)
-           PIPEASTAT: 0x00000307 (status: VSYNC_INT_STATUS 
DLINE_COMPARE_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS)
+           PIPEASTAT: 0x00040203 (status: SVBLANK_INT_ENABLE VSYNC_INT_STATUS 
VBLANK_INT_STATUS OREG_UPDATE_STATUS)
    PIPEA_GMCH_DATA_M: 0x00000000
    PIPEA_GMCH_DATA_N: 0x00000000
      PIPEA_DP_LINK_M: 0x00000000
      PIPEA_DP_LINK_N: 0x00000000
        CURSOR_A_BASE: 0x01950000
     CURSOR_A_CONTROL: 0x04000027
-   CURSOR_A_POSITION: 0x0267800b
+   CURSOR_A_POSITION: 0x024b0182
                 FPA0: 0x00020e08 (n = 2, m1 = 14, m2 = 8)
                 FPA1: 0x00020e08 (n = 2, m1 = 14, m2 = 8)
               DPLL_A: 0xd4020c00 (enabled, dvo, default clock, DAC/serial 
mode, p1 = 2, p2 = 10)
@@ -150,7 +150,7 @@
         FBC_CONTROL2: 0xffffffff
        FBC_FENCE_OFF: 0xffffffff
          FBC_MOD_NUM: 0xffffffff
-             MI_MODE: 0x00000240
+             MI_MODE: 0x00000040
         MI_ARB_STATE: 0x00000044
       MI_RDRET_STATE: 0x00000000
              ECOSKPD: 0x00000307
@@ -195,36 +195,36 @@
             FENCE  5: 0x00000000 (disabled)
             FENCE  6: 0x00000000 (disabled)
             FENCE  7: 0x00000000 (disabled)
-            FENCE  8: 0x085f809d (disabled)
-            FENCE  9: 0x08af7000 (disabled)
-           FENCE  10: 0x0ae6409d (disabled)
-           FENCE  11: 0x0b363000 (disabled)
-           FENCE  12: 0x0e4eb09d (disabled)
-           FENCE  13: 0x0e9ea000 (disabled)
-           FENCE  14: 0x04f5d09d (disabled)
-           FENCE  15: 0x04f84000 (disabled)
-       FENCE START 0: 0x085f809d ( enabled, X tile walk, 5120 pitch, 
0x085f8000 start)
-         FENCE END 0: 0x08af7000 (                                   
0x08af7000 end)
-       FENCE START 1: 0x0ae6409d ( enabled, X tile walk, 5120 pitch, 
0x0ae64000 start)
-         FENCE END 1: 0x0b363000 (                                   
0x0b363000 end)
-       FENCE START 2: 0x0e4eb09d ( enabled, X tile walk, 5120 pitch, 
0x0e4eb000 start)
-         FENCE END 2: 0x0e9ea000 (                                   
0x0e9ea000 end)
-       FENCE START 3: 0x04f5d09d ( enabled, X tile walk, 5120 pitch, 
0x04f5d000 start)
-         FENCE END 3: 0x04f84000 (                                   
0x04f84000 end)
-       FENCE START 4: 0x07ddb06d ( enabled, X tile walk, 3584 pitch, 
0x07ddb000 start)
-         FENCE END 4: 0x080da000 (                                   
0x080da000 end)
-       FENCE START 5: 0x048f109d ( enabled, X tile walk, 5120 pitch, 
0x048f1000 start)
-         FENCE END 5: 0x04918000 (                                   
0x04918000 end)
-       FENCE START 6: 0x0d39e09d ( enabled, X tile walk, 5120 pitch, 
0x0d39e000 start)
-         FENCE END 6: 0x0d89d000 (                                   
0x0d89d000 end)
-       FENCE START 7: 0x0144c09d ( enabled, X tile walk, 5120 pitch, 
0x0144c000 start)
-         FENCE END 7: 0x0194b000 (                                   
0x0194b000 end)
-       FENCE START 8: 0x0491d09d ( enabled, X tile walk, 5120 pitch, 
0x0491d000 start)
-         FENCE END 8: 0x04944000 (                                   
0x04944000 end)
-       FENCE START 9: 0x00000000 (disabled, X tile walk,  128 pitch, 
0x00000000 start)
-         FENCE END 9: 0x00000000 (                                   
0x00000000 end)
-      FENCE START 10: 0x00000000 (disabled, X tile walk,  128 pitch, 
0x00000000 start)
-        FENCE END 10: 0x00000000 (                                   
0x00000000 end)
+            FENCE  8: 0x0144c09d (disabled)
+            FENCE  9: 0x0194b000 (disabled)
+           FENCE  10: 0x0e4eb09d (disabled)
+           FENCE  11: 0x0e9ea000 (disabled)
+           FENCE  12: 0x086e909d (disabled)
+           FENCE  13: 0x08be8000 (disabled)
+           FENCE  14: 0x064ab09d (disabled)
+           FENCE  15: 0x069aa000 (disabled)
+       FENCE START 0: 0x0144c09d ( enabled, X tile walk, 5120 pitch, 
0x0144c000 start)
+         FENCE END 0: 0x0194b000 (                                   
0x0194b000 end)
+       FENCE START 1: 0x0e4eb09d ( enabled, X tile walk, 5120 pitch, 
0x0e4eb000 start)
+         FENCE END 1: 0x0e9ea000 (                                   
0x0e9ea000 end)
+       FENCE START 2: 0x086e909d ( enabled, X tile walk, 5120 pitch, 
0x086e9000 start)
+         FENCE END 2: 0x08be8000 (                                   
0x08be8000 end)
+       FENCE START 3: 0x064ab09d ( enabled, X tile walk, 5120 pitch, 
0x064ab000 start)
+         FENCE END 3: 0x069aa000 (                                   
0x069aa000 end)
+       FENCE START 4: 0x0d39e09d ( enabled, X tile walk, 5120 pitch, 
0x0d39e000 start)
+         FENCE END 4: 0x0d89d000 (                                   
0x0d89d000 end)
+       FENCE START 5: 0x04f5d09d ( enabled, X tile walk, 5120 pitch, 
0x04f5d000 start)
+         FENCE END 5: 0x04f84000 (                                   
0x04f84000 end)
+       FENCE START 6: 0x048f109d ( enabled, X tile walk, 5120 pitch, 
0x048f1000 start)
+         FENCE END 6: 0x04918000 (                                   
0x04918000 end)
+       FENCE START 7: 0x0491d09d ( enabled, X tile walk, 5120 pitch, 
0x0491d000 start)
+         FENCE END 7: 0x04944000 (                                   
0x04944000 end)
+       FENCE START 8: 0x0dc8300d ( enabled, X tile walk,  512 pitch, 
0x0dc83000 start)
+         FENCE END 8: 0x0dc85000 (                                   
0x0dc85000 end)
+       FENCE START 9: 0x0dc1e00d ( enabled, X tile walk,  512 pitch, 
0x0dc1e000 start)
+         FENCE END 9: 0x0dc20000 (                                   
0x0dc20000 end)
+      FENCE START 10: 0x0dc2101d ( enabled, X tile walk, 1024 pitch, 
0x0dc21000 start)
+        FENCE END 10: 0x0dc26000 (                                   
0x0dc26000 end)
       FENCE START 11: 0x00000000 (disabled, X tile walk,  128 pitch, 
0x00000000 start)
         FENCE END 11: 0x00000000 (                                   
0x00000000 end)
       FENCE START 12: 0x00000000 (disabled, X tile walk,  128 pitch, 
0x00000000 start)
blackbox:~# 


(when I suspend the machine after the not working resume again, it usually 
comes up nicely after that resume).

Is there anything unexpected in the register dumps?

Many thanks,
Rainer

Am Saturday, 24. September 2011 schrieb Keith Packard:
> On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> > Are there any other data I could gather to figure out what is going
> > wrong?
> 
> Oh, have we gotten register dumps from a working vs non-working resume?
> 
>         git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools
> 
> Let's hope there's some difference...



-- 
Rainer Dorsch
http://bokomoko.de/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: CRT not detected via hotplug on resume
@ 2011-09-24  8:59 Rainer Dorsch
  0 siblings, 0 replies; 11+ messages in thread
From: Rainer Dorsch @ 2011-09-24  8:59 UTC (permalink / raw)
  To: intel-gfx

Am Saturday, 24. September 2011 schrieben Sie:
> On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch <ml@bokomoko.de> wrote:
> > Are there any other data I could gather to figure out what is going
> > wrong?
> 
> Oh, have we gotten register dumps from a working vs non-working resume?
> 
>         git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools
> 
> Let's hope there's some difference...

I will generate register dumps, when I hit next time the problem.

Thanks for the pointer,
Rainer


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

^ permalink raw reply	[flat|nested] 11+ messages in thread
end of thread, other threads:[~2011-10-22 18:42 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-21 12:23 CRT not detected via hotplug on resume Rainer Dorsch
2011-09-21 15:31 ` 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

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.