Re: [Intel-gfx] CRT not detected via hotplug on resume
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 fe80 (32-bit, non-prefetchable) [size=1M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at cc00 [size=8]
Expansion ROM at [disabled]
Capabilities:
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: 0x0018 ( �y�dcz�T�v�H���d�{�)
+ DCC: 0x0018 ( �|�t}�d���z�X��d�~�)
CHDECMISC: 0x00ac (XOR bank/rank, ch2 enh disabled, ch1 enh
enabled, ch0 enh enabled, flex disabled, ep not present)
C0DRB0: 0x0018 (0x0008)
C0DRB1: 0x00180010 (0x0010)
@@ -51,18 +51,18 @@
DSPAPOS: 0x (0, 0)
DSPASIZE: 0x (1, 1)
DSPABASE: 0x
-DSPASURF: 0x0144c000
+DSPASURF: 0x0e4eb000
DSPATILEOFF: 0x
PIPEACONF: 0xc000 (enabled, active)
PIPEASRC: 0x04ff03ff (1280, 1024)
- PIPEASTAT: 0x0307 (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: 0x
PIPEA_GMCH_DATA_N: 0x
PIPEA_DP_LINK_M: 0x
PIPEA_DP_LINK_N: 0x
CURSOR_A_BASE: 0x0195
CURSOR_A_CONTROL: 0x0427
- 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: 0x
FBC_FENCE_OFF: 0x
FBC_MOD_NUM: 0x
- MI_MODE: 0x0240
+ MI_MODE: 0x0040
MI_ARB_STATE: 0x0044
MI_RDRET_STATE: 0x
ECOSKPD: 0x0307
@@ -195,36 +195,36 @@
FENCE 5: 0x (disabled)
FENCE 6: 0x (disabled)
FENCE 7: 0x (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 p
Re: [Intel-gfx] CRT not detected via hotplug on resume
Am Saturday, 24. September 2011 schrieben Sie: > On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch 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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch 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.pack...@intel.com pgpvFPX6MGbiA.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
Am Donnerstag 22 September 2011, 16:33:46 schrieb Keith Packard: > On Thu, 22 Sep 2011 10:36:12 +0200, Rainer Dorsch 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 800x60060.3 640x48060.0 720x40070.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 800x60060.3 640x48060.0 720x40070.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 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
On Thu, 22 Sep 2011 10:36:12 +0200, Rainer Dorsch 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.pack...@intel.com pgpPX6lnE15Lh.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
Am Wednesday, 21. September 2011 schrieb Keith Packard: > On Wed, 21 Sep 2011 18:15:27 +0200, Rainer Dorsch 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] [dr
Re: [Intel-gfx] CRT not detected via hotplug on resume
On Wed, 21 Sep 2011 18:15:27 +0200, Rainer Dorsch 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.pack...@intel.com pgpmZq7qswJQi.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
On Wednesday 21 September 2011, Rainer Dorsch 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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
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 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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] CRT not detected via hotplug on resume
On Wed, 21 Sep 2011 14:23:01 +0200, Rainer Dorsch 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.pack...@intel.com pgpCkBy2YzEW5.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] CRT not detected via hotplug on resume
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-1303syslog- 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/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
