* debugging Haswell eDP black screen after S3
@ 2013-05-14 21:01 Ben Guthro
2013-05-15 20:42 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-14 21:01 UTC (permalink / raw)
To: intel-gfx
I am attempting to debug an issue with some Haswell laptop systems
which do not restore their screen after resuming from S3 when running
on the stable 3.8 kernel (3.8.13)
The backlight is OK, but the screen is just black.
In trying to determine what was going wrong, I tried looking at the
output of intel_reg_dumper, in a good, and bad case:
diff -u good_reg.txt bad_reg.txt
--- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
+++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
@@ -1,5 +1,4 @@
- DCC: 0x00000000 (0x00000000f3400000
0x00000000f37fffff 0x00000000��
-�\x7f)
+ DCC: 0x00000000 (0x00000000f3400000
0x00000000f37fffff 0x00000000��=\x1c�\x7f)
CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
disabled, ch0 enh disabled, flex disabled, ep not present)
C0DRB0: 0x00000000 (0x0000)
C0DRB1: 0x00000000 (0x0000)
@@ -63,17 +62,17 @@
PIPEA_DP_LINK_N: 0x00000000
CURSOR_A_BASE: 0x01061000
CURSOR_A_CONTROL: 0x04000027
- CURSOR_A_POSITION: 0x03a3032f
+ CURSOR_A_POSITION: 0x01bb03fb
FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
clock, unknown mode, p1 = 0, p2 = 0)
DPLL_A_MD: 0x00000000
- HTOTAL_A: 0x0821077f (1920 active, 2082 total)
- HBLANK_A: 0x0821077f (1920 start, 2082 end)
- HSYNC_A: 0x081307af (1968 start, 2068 end)
- VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
- VBLANK_A: 0x045f0437 (1080 start, 1120 end)
- VSYNC_A: 0x044b0441 (1090 start, 1100 end)
+ HTOTAL_A: 0x00000000 (1 active, 1 total)
+ HBLANK_A: 0x00000000 (1 start, 1 end)
+ HSYNC_A: 0x00000000 (1 start, 1 end)
+ VTOTAL_A: 0x00000000 (1 active, 1 total)
+ VBLANK_A: 0x00000000 (1 start, 1 end)
+ VSYNC_A: 0x00000000 (1 start, 1 end)
BCLRPAT_A: 0x00000000
VSYNCSHIFT_A: 0x00000000
DSPBCNTR: 0x00004000 (disabled, pipe A)
It appears the registers that are saved, and restored in
i915_save_modeset_reg / i915_restore_modeset_reg is not working
properly.
When I put some debug in, I discovered that it was bailing out of
i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
However, it was set at the end of i915_init()
This, of course, confuses me.
Am I seeing memory corruption here?
Any insight is appreciated.
Ben
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-14 21:01 debugging Haswell eDP black screen after S3 Ben Guthro
@ 2013-05-15 20:42 ` Ben Guthro
2013-05-16 13:24 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-15 20:42 UTC (permalink / raw)
To: intel-gfx
On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
> I am attempting to debug an issue with some Haswell laptop systems
> which do not restore their screen after resuming from S3 when running
> on the stable 3.8 kernel (3.8.13)
> The backlight is OK, but the screen is just black.
>
> In trying to determine what was going wrong, I tried looking at the
> output of intel_reg_dumper, in a good, and bad case:
>
> diff -u good_reg.txt bad_reg.txt
> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
> @@ -1,5 +1,4 @@
> - DCC: 0x00000000 (0x00000000f3400000
> 0x00000000f37fffff 0x00000000��
> -� )
> + DCC: 0x00000000 (0x00000000f3400000
> 0x00000000f37fffff 0x00000000��= � )
> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
> disabled, ch0 enh disabled, flex disabled, ep not present)
> C0DRB0: 0x00000000 (0x0000)
> C0DRB1: 0x00000000 (0x0000)
> @@ -63,17 +62,17 @@
> PIPEA_DP_LINK_N: 0x00000000
> CURSOR_A_BASE: 0x01061000
> CURSOR_A_CONTROL: 0x04000027
> - CURSOR_A_POSITION: 0x03a3032f
> + CURSOR_A_POSITION: 0x01bb03fb
> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
> clock, unknown mode, p1 = 0, p2 = 0)
> DPLL_A_MD: 0x00000000
> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
> - HSYNC_A: 0x081307af (1968 start, 2068 end)
> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
> + HTOTAL_A: 0x00000000 (1 active, 1 total)
> + HBLANK_A: 0x00000000 (1 start, 1 end)
> + HSYNC_A: 0x00000000 (1 start, 1 end)
> + VTOTAL_A: 0x00000000 (1 active, 1 total)
> + VBLANK_A: 0x00000000 (1 start, 1 end)
> + VSYNC_A: 0x00000000 (1 start, 1 end)
> BCLRPAT_A: 0x00000000
> VSYNCSHIFT_A: 0x00000000
> DSPBCNTR: 0x00004000 (disabled, pipe A)
>
>
> It appears the registers that are saved, and restored in
> i915_save_modeset_reg / i915_restore_modeset_reg is not working
> properly.
>
> When I put some debug in, I discovered that it was bailing out of
> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
> However, it was set at the end of i915_init()
> This, of course, confuses me.
>
> Am I seeing memory corruption here?
It looks like I misread the code here, inversing an if statement state.
That said, I don't really have any clues as to why the display is
black after resuming from S3
Is this an eDP training issue? Are there any changesets I can try backporting?
I tried this, but it didn't seem to help:
https://patchwork.kernel.org/patch/2516601/
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-15 20:42 ` Ben Guthro
@ 2013-05-16 13:24 ` Ben Guthro
2013-05-17 11:52 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-16 13:24 UTC (permalink / raw)
To: intel-gfx
On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
>> I am attempting to debug an issue with some Haswell laptop systems
>> which do not restore their screen after resuming from S3 when running
>> on the stable 3.8 kernel (3.8.13)
>> The backlight is OK, but the screen is just black.
>>
>> In trying to determine what was going wrong, I tried looking at the
>> output of intel_reg_dumper, in a good, and bad case:
>>
>> diff -u good_reg.txt bad_reg.txt
>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
>> @@ -1,5 +1,4 @@
>> - DCC: 0x00000000 (0x00000000f3400000
>> 0x00000000f37fffff 0x00000000��
>> -� )
>> + DCC: 0x00000000 (0x00000000f3400000
>> 0x00000000f37fffff 0x00000000��= � )
>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
>> disabled, ch0 enh disabled, flex disabled, ep not present)
>> C0DRB0: 0x00000000 (0x0000)
>> C0DRB1: 0x00000000 (0x0000)
>> @@ -63,17 +62,17 @@
>> PIPEA_DP_LINK_N: 0x00000000
>> CURSOR_A_BASE: 0x01061000
>> CURSOR_A_CONTROL: 0x04000027
>> - CURSOR_A_POSITION: 0x03a3032f
>> + CURSOR_A_POSITION: 0x01bb03fb
>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
>> clock, unknown mode, p1 = 0, p2 = 0)
>> DPLL_A_MD: 0x00000000
>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
>> + HBLANK_A: 0x00000000 (1 start, 1 end)
>> + HSYNC_A: 0x00000000 (1 start, 1 end)
>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
>> + VBLANK_A: 0x00000000 (1 start, 1 end)
>> + VSYNC_A: 0x00000000 (1 start, 1 end)
>> BCLRPAT_A: 0x00000000
>> VSYNCSHIFT_A: 0x00000000
>> DSPBCNTR: 0x00004000 (disabled, pipe A)
>>
>>
>> It appears the registers that are saved, and restored in
>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
>> properly.
>>
>> When I put some debug in, I discovered that it was bailing out of
>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
>> However, it was set at the end of i915_init()
>> This, of course, confuses me.
>>
>> Am I seeing memory corruption here?
>
> It looks like I misread the code here, inversing an if statement state.
>
> That said, I don't really have any clues as to why the display is
> black after resuming from S3
>
> Is this an eDP training issue? Are there any changesets I can try backporting?
> I tried this, but it didn't seem to help:
> https://patchwork.kernel.org/patch/2516601/
Below is a serial dump with drm.debug=4, after resuming from S3
If anyone sees anything awry, being pointed in the right direction
would be appreciated:
[ 119.676134] ACPI: Low-level resume complete
[ 119.676200] PM: Restoring platform NVS memory
[ 119.676585] xen-acpi-processor: Uploading Xen processor PM info
[ 119.678302] Enabling non-boot CPUs ...
[ 119.678351] installing Xen timer for CPU 1
[ 119.678380] cpu 1 spinlock event irq 48
[ 119.679469] CPU1 is up
[ 119.679496] installing Xen timer for CPU 2
[ 119.679505] cpu 2 spinlock event irq 55
[ 119.680524] CPU2 is up
[ 119.680586] installing Xen timer for CPU 3
[ 119.680590] cpu 3 spinlock event irq 62
[ 119.681463] CPU3 is up
[ 119.681482] installing Xen timer for CPU 4
[ 119.681487] cpu 4 spinlock event irq 69
[ 119.682448] CPU4 is up
[ 119.682478] installing Xen timer for CPU 5
[ 119.682482] cpu 5 spinlock event irq 76
[ 119.683463] CPU5 is up
[ 119.683490] installing Xen timer for CPU 6
[ 119.683494] cpu 6 spinlock event irq 83
[ 119.684483] CPU6 is up
[ 119.684512] installing Xen timer for CPU 7
[ 119.684517] cpu 7 spinlock event irq 90
[ 119.685523] CPU7 is up
[ 119.685941] ACPI: Waking up from system sleep state S3
[ 120.546804] pci 0000:01:00.0: power state changed by ACPI to D0
[ 120.586931] PM: noirq resume of devices complete after 160.133 msecs
[ 120.587261] PM: early resume of devices complete after 0.247 msecs
[ 120.587438] xen: registering gsi 16 triggering 0 polarity 1
[ 120.587447] i915 0000:00:02.0: setting latency timer to 64
[ 120.587449] Already setup the GSI :16
[ 120.587569] xen: registering gsi 22 triggering 0 polarity 1
[ 120.587578] Already setup the GSI :22
[ 120.587749] pciehp 0000:00:1c.2:pcie04: pciehp_resume ENTRY
[ 120.587769] pciehp 0000:00:1c.0:pcie04: pciehp_resume ENTRY
[ 120.587837] pciehp 0000:00:1c.3:pcie04: pciehp_resume ENTRY
[ 120.587868] pciehp 0000:00:1c.4:pcie04: pciehp_resume ENTRY
[ 120.588125] pciehp 0000:00:1c.6:pcie04: pciehp_resume ENTRY
[ 120.588174] pciehp 0000:00:1c.7:pcie04: pciehp_resume ENTRY
[ 120.588203] pciehp 0000:00:1c.5:pcie04: pciehp_resume ENTRY
[ 120.588415] ahci 0000:00:1f.2: setting latency timer to 64
[ 120.633967] [drm:i915_write32] *ERROR* Unclaimed write to 70030
[ 120.634919] [drm:intel_modeset_setup_hw_state], [CRTC:3] hw state
readout: disabled
[ 120.634919] [drm:intel_modeset_setup_hw_state], [CRTC:5] hw state
readout: disabled
[ 120.634920] [drm:intel_modeset_setup_hw_state], [CRTC:7] hw state
readout: disabled
[ 120.634922] [drm:intel_modeset_setup_hw_state], [ENCODER:10:DAC-10]
hw state readout: disabled, pipe=0
[ 120.634923] [drm:intel_modeset_setup_hw_state],
[ENCODER:11:TMDS-11] hw state readout: disabled, pipe=0
[ 120.634924] [drm:intel_modeset_setup_hw_state],
[ENCODER:20:TMDS-20] hw state readout: disabled, pipe=0
[ 120.634925] [drm:intel_modeset_setup_hw_state],
[CONNECTOR:12:eDP-1] hw state readout: disabled
[ 120.634926] [drm:intel_modeset_setup_hw_state], [CONNECTOR:9:VGA-1]
hw state readout: disabled
[ 120.634927] [drm:intel_modeset_setup_hw_state],
[CONNECTOR:21:HDMI-A-1] hw state readout: disabled
[ 120.634928] [drm:intel_modeset_setup_hw_state], [CONNECTOR:22:DP-1]
hw state readout: disabled
[ 120.634931] [drm:intel_modeset_check_state], [ENCODER:10:DAC-10]
[ 120.634932] [drm:intel_modeset_check_state], [ENCODER:11:TMDS-11]
[ 120.634933] [drm:intel_modeset_check_state], [ENCODER:20:TMDS-20]
[ 120.634934] [drm:intel_modeset_check_state], [CRTC:3]
[ 120.634934] [drm:intel_modeset_check_state], [CRTC:5]
[ 120.634935] [drm:intel_modeset_check_state], [CRTC:7]
[ 120.634939] [drm:intel_crt_reset], pch crt adpa set to 0xf40000
[ 120.658327] [drm:intel_crtc_set_config], [CRTC:3] [FB:14]
#connectors=1 (x y) (0 0)
[ 120.658328] [drm:intel_set_config_compute_mode_changes], crtc has
no fb, full mode set
[ 120.658330] [drm:intel_modeset_stage_output_state], encoder
changed, full mode switch
[ 120.658331] [drm:intel_modeset_stage_output_state],
[CONNECTOR:12:eDP-1] to [CRTC:3]
[ 120.658332] [drm:intel_modeset_stage_output_state], crtc changed,
full mode switch
[ 120.658333] [drm:intel_crtc_set_config], attempting to set mode
from userspace
[ 120.658336] [drm:drm_mode_debug_printmodeline], Modeline
13:"1920x1080" 60 140000 1920 1968 2068 2082 1080 1090 1100 1120 0x48
0x9
[ 120.658337] [drm:intel_set_mode], set mode pipe masks: modeset: 1,
prepare: 1, disable: 0
[ 120.658340] [drm:intel_dp_mode_fixup], DP link computation with max
lane count 2 max bw 0a pixel clock 140000KHz
[ 120.658342] [drm:intel_dp_mode_fixup], DP link bw 0a lane count 2
clock 270000 bpp 24
[ 120.658343] [drm:intel_dp_mode_fixup], DP link bw required 336000
available 432000
[ 120.658344] [drm:intel_modeset_adjusted_mode], [CRTC:3]
[ 120.658348] [drm:intel_choose_pipe_bpp_dither], clamping display
bpc (was -1) to EDID reported max of 6
[ 120.658349] [drm:intel_choose_pipe_bpp_dither], setting pipe bpc to
8 (max display bpc 6)
[ 120.658350] [drm:haswell_crtc_mode_set], Mode for pipe 0:
[ 120.658352] [drm:drm_mode_debug_printmodeline], Modeline
13:"1920x1080" 60 140000 1920 1968 2068 2082 1080 1090 1100 1120 0x48
0x9
[ 120.658360] [drm:ironlake_update_plane], Writing base 00074000
00000000 0 0 7680
[ 120.658365] [drm:intel_crtc_mode_set], [ENCODER:11:TMDS-11] set
[MODE:13:1920x1080]
[ 120.658366] [drm:intel_ddi_mode_set], Preparing DDI mode for
Haswell on port A, pipe A
[ 120.658368] [drm:sandybridge_update_wm], FIFO watermarks For pipe A
- plane 16, cursor: 6
[ 120.658371] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[ 120.658374] [drm:ironlake_wait_panel_power_cycle], Wait for panel power cycle
[ 120.658378] [drm:ironlake_wait_panel_status], mask b800000f value
00000000 status 00000000 control abcd0000
[ 120.658386] [drm:ironlake_edp_panel_vdd_on], PCH_PP_STATUS:
0x00000000 PCH_PP_CONTROL: 0xabcd0008
[ 120.658387] [drm:ironlake_edp_panel_vdd_on], eDP was not running
[ 120.658866] e1000e 0000:00:19.0: System wakeup disabled by ACPI
[ 120.658883] e1000e 0000:00:19.0: setting latency timer to 64
[ 120.696373] pciehp 0000:00:1c.2:pcie04: Device 0000:03:00.0 already
exists at 0000:03:00, cannot hot-add
[ 120.696457] pciehp 0000:00:1c.2:pcie04: Cannot add device at 0000:03:00
[ 120.696474] pciehp 0000:00:1c.6:pcie04: Device 0000:0d:00.0 already
exists at 0000:0d:00, cannot hot-add
[ 120.696474] pciehp 0000:00:1c.6:pcie04: Cannot add device at 0000:0d:00
[ 120.696530] pci 0000:15:00.0: [1217:8520] type 00 class 0x080501
[ 120.696573] pci 0000:15:00.0: reg 10: [mem 0x00000000-0x00000fff]
[ 120.696594] pci 0000:15:00.0: reg 14: [mem 0x00000000-0x000007ff]
[ 120.696826] pci 0000:15:00.0: PME# supported from D3hot D3cold
[ 120.716533] pci 0000:15:00.0: BAR 0: assigned [mem 0xf3800000-0xf3800fff]
[ 120.716547] pci 0000:15:00.0: BAR 1: assigned [mem 0xf3801000-0xf38017ff]
[ 120.716561] pcieport 0000:00:1c.7: PCI bridge to [bus 15]
[ 120.716565] pcieport 0000:00:1c.7: bridge window [io 0x6000-0x7fff]
[ 120.716576] pcieport 0000:00:1c.7: bridge window [mem
0xf3800000-0xf41fffff]
[ 120.716585] pcieport 0000:00:1c.7: bridge window [mem
0xd2100000-0xd2afffff 64bit pref]
[ 120.716618] pci 0000:15:00.0: no hotplug settings from platform
[ 120.866415] [drm:ironlake_edp_panel_on], Turn eDP power on
[ 120.866419] [drm:ironlake_wait_panel_power_cycle], Wait for panel power cycle
[ 120.866427] [drm:ironlake_wait_panel_status], mask b800000f value
00000000 status 00000000 control abcd0008
[ 120.866434] [drm:ironlake_wait_panel_on], Wait for panel power on
[ 120.866440] [drm:ironlake_wait_panel_status], mask b000000f value
80000008 status 0000000a control abcd000b
[ 121.026430] ata4: SATA link down (SStatus 0 SControl 300)
[ 121.046458] ata3: SATA link down (SStatus 0 SControl 300)
[ 121.066461] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 121.078674] ata2.00: configured for UDMA/100
[ 121.086422] [drm:ironlake_edp_panel_vdd_off], Turn eDP VDD off 1
[ 121.086434] [drm:ironlake_panel_vdd_off_sync], PCH_PP_STATUS:
0x80000008 PCH_PP_CONTROL: 0xabcd0003
[ 121.147945] [drm:intel_dp_start_link_train], training pattern 1
signal levels 00000000
[ 121.149476] [drm:intel_dp_start_link_train], clock recovery OK
[ 121.151307] [drm:intel_dp_complete_link_train], Channel EQ done. DP
Training successfull
[ 121.206437] [drm:ironlake_wait_for_vblank], vblank wait timed out
[ 121.266417] [drm:ironlake_wait_for_vblank], vblank wait timed out
[ 121.266833] [drm:ironlake_edp_backlight_on],
[ 121.306450] [drm:intel_connector_check_state], [CONNECTOR:12:eDP-1]
[ 121.306456] [drm:intel_modeset_check_state], [ENCODER:10:DAC-10]
[ 121.306460] [drm:intel_modeset_check_state], [ENCODER:11:TMDS-11]
[ 121.306463] [drm:intel_modeset_check_state], [ENCODER:20:TMDS-20]
[ 121.306466] [drm:intel_modeset_check_state], [CRTC:3]
[ 121.306469] [drm:intel_modeset_check_state], [CRTC:5]
[ 121.306471] [drm:intel_modeset_check_state], [CRTC:7]
[ 121.826439] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 121.966446] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 122.214860] ata1.00: configured for UDMA/133
[ 122.226644] sd 0:0:0:0: [sda] Starting disk
[ 123.587377] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 123.587440] br-eth0: port 1(eth0) entered forwarding state
[ 123.587457] br-eth0: port 1(eth0) entered forwarding state
[ 124.196432] pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
[ 124.196436] pciehp 0000:00:1c.0:pcie04: Failed to check link status
[ 124.196643] dpm_run_callback(): pnp_bus_resume+0x0/0x70 returns -19
[ 124.196647] PM: Device 00:09 failed to resume: error -19
[ 124.198100] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 124.204676] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 124.427522] PM: resume of devices complete after 3840.259 msecs
[ 124.427617] PM: resume devices took 3.840 seconds
[ 124.427815] PM: Finishing wakeup.
[ 124.427816] Restarting tasks ... done.
[ 124.755977] video LNXVIDEO:00: Restoring backlight state
[ 124.755992] video LNXVIDEO:01: Restoring backlight state
[ 124.817272] [drm:drm_mode_setcrtc], [CRTC:3]
[ 124.817293] [drm:drm_mode_setcrtc], [CONNECTOR:12:eDP-1]
[ 124.817304] [drm:intel_crtc_set_config], [CRTC:3] [FB:25]
#connectors=1 (x y) (0 0)
[ 124.817318] [drm:intel_modeset_stage_output_state],
[CONNECTOR:12:eDP-1] to [CRTC:3]
[ 124.821673] [drm:ironlake_update_plane], Writing base 0085D000
00000000 0 0 7680
[ 124.836501] [drm:drm_mode_setcrtc], [CRTC:5]
[ 124.836521] [drm:intel_crtc_set_config], [CRTC:5] [NOFB]
[ 124.836536] [drm:intel_modeset_stage_output_state],
[CONNECTOR:12:eDP-1] to [CRTC:3]
[ 124.836775] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 124.836785] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1]
[ 124.836796] [drm:intel_dp_detect], DPCD: 11 0a 82 01 00 00 01 80 02
00 00 00 00 01 00
[ 124.836807] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[ 124.836823] [drm:ironlake_edp_panel_vdd_on], PCH_PP_STATUS:
0x80000008 PCH_PP_CONTROL: 0xabcd000f
[ 124.837345] [drm:intel_dp_probe_oui], Sink OUI: 00e04c
[ 124.837864] [drm:intel_dp_probe_oui], Branch OUI: 00e04c
[ 124.837873] [drm:ironlake_edp_panel_vdd_off], Turn eDP VDD off 1
[ 124.837900] [drm:drm_edid_to_eld], ELD: no CEA Extension found
[ 124.837913] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1] probed modes :
[ 124.837923] [drm:drm_mode_debug_printmodeline], Modeline
23:"1920x1080" 60 140000 1920 1968 2068 2082 1080 1090 1100 1120 0x48
0x9
[ 124.837939] [drm:drm_mode_debug_printmodeline], Modeline
24:"1920x1080" 40 140000 1920 1968 2068 2520 1080 1090 1100 1388 0x40
0x9
[ 124.837960] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 124.838445] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 124.838461] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 124.838472] [drm:intel_ironlake_crt_detect_hotplug], trigger
hotplug detect cycle: adpa=0xf40000
[ 124.856381] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 124.856402] [drm:intel_crt_detect], CRT not detected via hotplug
[ 124.876359] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 124.876363] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 124.876366] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 124.876368] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga. force bit now 1
[ 124.876763] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 124.876765] [drm:intel_gmbus_force_bit], disabling bit-banging on
i915 gmbus vga. force bit now 0
[ 124.876768] [drm:intel_crt_detect_ddc], CRT not detected via
DDC:0x50 [no valid EDID found]
[ 124.876770] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1] disconnected
[ 124.876775] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 124.876777] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 124.876781] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 124.876783] [drm:intel_crt_detect], CRT not detected via hotplug
[ 124.896366] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 124.896386] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 124.896401] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 124.896416] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga. force bit now 1
[ 124.896820] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 124.896830] [drm:intel_gmbus_force_bit], disabling bit-banging on
i915 gmbus vga. force bit now 0
[ 124.896840] [drm:intel_crt_detect_ddc], CRT not detected via
DDC:0x50 [no valid EDID found]
[ 124.896851] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1] disconnected
[ 124.896879] [drm:drm_mode_getconnector], [CONNECTOR:21:?]
[ 124.896889] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1]
[ 124.916382] [drm:gmbus_xfer], GMBUS [i915 gmbus dpd] NAK for addr: 0050 r(1)
[ 124.916400] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus dpd
[ 124.916413] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1] disconnected
[ 124.916433] [drm:drm_mode_getconnector], [CONNECTOR:21:?]
[ 124.916443] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1]
[ 124.936423] [drm:gmbus_xfer], GMBUS [i915 gmbus dpd] NAK for addr: 0050 r(1)
[ 124.936442] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus dpd
[ 124.936455] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1] disconnected
[ 124.936483] [drm:drm_mode_getconnector], [CONNECTOR:22:?]
[ 124.936493] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1]
[ 124.939070] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 124.958956] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 124.978973] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 124.996363] [drm:intel_dp_detect], DPCD: 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 124.996378] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1] disconnected
[ 124.996400] [drm:drm_mode_getconnector], [CONNECTOR:22:?]
[ 124.996410] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1]
[ 124.998998] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 125.018976] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 125.039002] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 125.056370] [drm:intel_dp_detect], DPCD: 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 125.056399] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1] disconnected
[ 125.157494] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 125.157606] ehci-pci: EHCI PCI platform driver
[ 125.157626] xen: registering gsi 16 triggering 0 polarity 1
[ 125.157630] Already setup the GSI :16
[ 125.157657] ehci-pci 0000:00:1a.0: setting latency timer to 64
[ 125.157661] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 125.157714] ehci-pci 0000:00:1a.0: new USB bus registered, assigned
bus number 1
[ 125.157739] ehci-pci 0000:00:1a.0: debug port 2
[ 125.161644] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 125.161683] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf743c000
[ 125.176355] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 125.176460] hub 1-0:1.0: USB hub found
[ 125.176464] hub 1-0:1.0: 3 ports detected
[ 125.186500] xen: registering gsi 21 triggering 0 polarity 1
[ 125.186515] Already setup the GSI :21
[ 125.186577] ehci-pci 0000:00:1d.0: setting latency timer to 64
[ 125.186581] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 125.186784] ehci-pci 0000:00:1d.0: new USB bus registered, assigned
bus number 2
[ 125.186843] ehci-pci 0000:00:1d.0: debug port 2
[ 125.190832] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 125.190912] ehci-pci 0000:00:1d.0: irq 21, io mem 0xf743b000
[ 125.206422] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 125.206767] hub 2-0:1.0: USB hub found
[ 125.206781] hub 2-0:1.0: 3 ports detected
[ 125.285197] xen: registering gsi 16 triggering 0 polarity 1
[ 125.285215] Already setup the GSI :16
[ 125.285341] xhci_hcd 0000:00:14.0: setting latency timer to 64
[ 125.285356] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 125.285599] xhci_hcd 0000:00:14.0: new USB bus registered, assigned
bus number 3
[ 125.285993] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 125.286705] xHCI xhci_add_endpoint called for root hub
[ 125.286715] xHCI xhci_check_bandwidth called for root hub
[ 125.286772] hub 3-0:1.0: USB hub found
[ 125.286799] hub 3-0:1.0: 15 ports detected
[ 125.296556] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 125.296754] xhci_hcd 0000:00:14.0: new USB bus registered, assigned
bus number 4
[ 125.297070] xHCI xhci_add_endpoint called for root hub
[ 125.297083] xHCI xhci_check_bandwidth called for root hub
[ 125.297182] hub 4-0:1.0: USB hub found
[ 125.297208] hub 4-0:1.0: 6 ports detected
[ 125.317531] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 125.317537] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1]
[ 125.317540] [drm:intel_dp_detect], DPCD: 11 0a 82 01 00 00 01 80 02
00 00 00 00 01 00
[ 125.317543] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[ 125.317546] [drm:ironlake_edp_panel_vdd_on], eDP VDD already on
[ 125.318054] [drm:intel_dp_probe_oui], Sink OUI: 00e04c
[ 125.318561] [drm:intel_dp_probe_oui], Branch OUI: 00e04c
[ 125.318563] [drm:ironlake_edp_panel_vdd_off], Turn eDP VDD off 1
[ 125.318571] [drm:drm_edid_to_eld], ELD: no CEA Extension found
[ 125.318575] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1] probed modes :
[ 125.318579] [drm:drm_mode_debug_printmodeline], Modeline
23:"1920x1080" 60 140000 1920 1968 2068 2082 1080 1090 1100 1120 0x48
0x9
[ 125.318583] [drm:drm_mode_debug_printmodeline], Modeline
24:"1920x1080" 40 140000 1920 1968 2068 2520 1080 1090 1100 1388 0x40
0x9
[ 125.318588] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 125.318717] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 125.318720] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 125.318724] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 125.318726] [drm:intel_crt_detect], CRT not detected via hotplug
[ 125.336369] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 125.336376] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 125.336380] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 125.336384] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga. force bit now 1
[ 125.336751] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 125.336753] [drm:intel_gmbus_force_bit], disabling bit-banging on
i915 gmbus vga. force bit now 0
[ 125.336755] [drm:intel_crt_detect_ddc], CRT not detected via
DDC:0x50 [no valid EDID found]
[ 125.336758] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1] disconnected
[ 125.336765] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 125.336768] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 125.336771] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 125.336774] [drm:intel_crt_detect], CRT not detected via hotplug
[ 125.356375] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 125.356386] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 125.356394] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 125.356401] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga.[ 126.506424] usb 3-14: new full-speed USB device
number 4 using xhci_hcd
[ 126.554084] usb 3-14: config 0 descriptor??
[ 126.626409] [drm:intel_modeset_check_state], [ENCODER:10:DAC-10]
[ 126.626426] [drm:intel_modeset_check_state], [ENCODER:11:TMDS-11]
[ 126.626436] [drm:intel_modeset_check_state], [ENCODER:20:TMDS-20]
[ 126.626445] [drm:intel_modeset_check_state], [CRTC:3]
[ 126.626453] [drm:intel_modeset_check_state], [CRTC:5]
[ 126.626461] [drm:intel_modeset_check_state], [CRTC:7]
[ 126.630921] [drm:drm_mode_setcrtc], [CRTC:3]
[ 126.630948] [drm:drm_mode_setcrtc], [CONNECTOR:12:eDP-1]
[ 126.630948] [drm:intel_crtc_set_config], [CRTC:3] [FB:25]
#connectors=1 (x y) (0 0)
[ 126.630960] [drm:intel_modeset_stage_output_state],
[CONNECTOR:12:eDP-1] to [CRTC:3]
[ 126.706999] [drm:sandybridge_update_wm], FIFO watermarks For pipe A
- plane 16, cursor: 6
[ 126.707006] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[ 126.707010] [drm:ironlake_wait_panel_power_cycle], Wait for panel power cycle
[ 126.707015] [drm:ironlake_wait_panel_status], mask b800000f value
00000000 status 00000000 control abcd0000
[ 126.707024] [drm:ironlake_edp_panel_vdd_on], PCH_PP_STATUS:
0x00000000 PCH_PP_CONTROL: 0xabcd0008
[ 126.707028] [drm:ironlake_edp_panel_vdd_on], eDP was not running
[ 126.916392] [drm:ironlake_edp_panel_on], Turn eDP power on
[ 126.916411] [drm:ironlake_wait_panel_power_cycle], Wait for panel power cycle
[ 126.916423] [drm:ironlake_wait_panel_status], mask b800000f value
00000000 status 00000000 control abcd0008
[ 126.916440] [drm:ironlake_wait_panel_on], Wait for panel power on
[ 126.916451] [drm:ironlake_wait_panel_status], mask b000000f value
80000008 status 9000000a control abcd000b
[ 127.136356] [drm:ironlake_edp_panel_vdd_off], Turn eDP VDD off 1
[ 127.136374] [drm:ironlake_panel_vdd_off_sync], PCH_PP_STATUS:
0x80000008 PCH_PP_CONTROL: 0xabcd0003
[ 127.197885] [drm:intel_dp_start_link_train], training pattern 1
signal levels 00000000
[ 127.199424] [drm:intel_dp_start_link_train], clock recovery OK
[ 127.201254] [drm:intel_dp_complete_link_train], Channel EQ done. DP
Training successfull
[ 127.256352] [drm:ironlake_wait_for_vblank], vblank wait timed out
[ 127.316443] [drm:ironlake_wait_for_vblank], vblank wait timed out
[ 127.316877] [drm:ironlake_edp_backlight_on],
[ 127.356458] [drm:intel_connector_check_state], [CONNECTOR:12:eDP-1]
[ 127.356478] [drm:intel_modeset_check_state], [ENCODER:10:DAC-10]
[ 127.356488] [drm:intel_modeset_check_state], [ENCODER:11:TMDS-11]
[ 127.356498] [drm:intel_modeset_check_state], [ENCODER:20:TMDS-20]
[ 127.356506] [drm:intel_modeset_check_state], [CRTC:3]
[ 127.356514] [drm:intel_modeset_check_state], [CRTC:5]
[ 127.356522] [drm:intel_modeset_check_state], [CRTC:7]
[ 127.360188] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 127.360193] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1]
[ 127.360196] [drm:intel_dp_detect], DPCD: 11 0a 82 01 00 00 01 80 02
00 00 00 00 01 00
[ 127.360199] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[ 127.360208] [drm:ironlake_edp_panel_vdd_on], PCH_PP_STATUS:
0x80000008 PCH_PP_CONTROL: 0xabcd000f
[ 127.360716] [drm:intel_dp_probe_oui], Sink OUI: 00e04c
[ 127.361222] [drm:intel_dp_probe_oui], Branch OUI: 00e04c
[ 127.361224] [drm:ironlake_edp_panel_vdd_off], Turn eDP VDD off 1
[ 127.361232] [drm:drm_edid_to_eld], ELD: no CEA Extension found
[ 127.361235] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:12:eDP-1] probed modes :
[ 127.361238] [drm:drm_mode_debug_printmodeline], Modeline
23:"1920x1080" 60 140000 1920 1968 2068 2082 1080 1090 1100 1120 0x48
0x9
[ 127.361241] [drm:drm_mode_debug_printmodeline], Modeline
24:"1920x1080" 40 140000 1920 1968 2068 2520 1080 1090 1100 1388 0x40
0x9
[ 127.361246] [drm:drm_mode_getconnector], [CONNECTOR:12:?]
[ 127.361362] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 127.361364] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 127.361368] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 127.361371] [drm:intel_crt_detect], CRT not detected via hotplug
[ 127.376384] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 127.376389] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 127.376391] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 127.376394] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga. force bit now 1
[ 127.376762] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 127.376764] [drm:intel_gmbus_force_bit], disabling bit-banging on
i915 gmbus vga. force bit now 0
[ 127.376766] [drm:intel_crt_detect_ddc], CRT not detected via
DDC:0x50 [no valid EDID found]
[ 127.376769] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1] disconnected
[ 127.376773] [drm:drm_mode_getconnector], [CONNECTOR:9:?]
[ 127.376776] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1]
[ 127.376779] [drm:intel_ironlake_crt_detect_hotplug], ironlake
hotplug adpa=0xf40000, result 0
[ 127.376781] [drm:intel_crt_detect], CRT not detected via hotplug
[ 127.396426] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1)
[ 127.396444] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 127.396456] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed,
retry using GPIO bit-banging
[ 127.396466] [drm:intel_gmbus_force_bit], enabling bit-banging on
i915 gmbus vga. force bit now 1
[ 127.396861] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus vga
[ 127.396871] [drm:intel_gmbus_force_bit], disabling bit-banging on
i915 gmbus vga. force bit now 0
[ 127.396881] [drm:intel_crt_detect_ddc], CRT not detected via
DDC:0x50 [no valid EDID found]
[ 127.396893] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:9:VGA-1] disconnected
[ 127.396933] [drm:drm_mode_getconnector], [CONNECTOR:21:?]
[ 127.396944] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1]
[ 127.416407] [drm:gmbus_xfer], GMBUS [i915 gmbus dpd] NAK for addr: 0050 r(1)
[ 127.416432] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus dpd
[ 127.416450] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1] disconnected
[ 127.416494] [drm:drm_mode_getconnector], [CONNECTOR:21:?]
[ 127.416509] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1]
[ 127.436382] [drm:gmbus_xfer], GMBUS [i915 gmbus dpd] NAK for addr: 0050 r(1)
[ 127.436386] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent
adapter i915 gmbus dpd
[ 127.436389] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:21:HDMI-A-1] disconnected
[ 127.436398] [drm:drm_mode_getconnector], [CONNECTOR:22:?]
[ 127.436401] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1]
[ 127.438956] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.458935] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.478930] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.496362] [drm:intel_dp_detect], DPCD: 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 127.496370] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1] disconnected
[ 127.496378] [drm:drm_mode_getconnector], [CONNECTOR:22:?]
[ 127.496389] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1]
[ 127.498943] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.518929] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.538929] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f
[ 127.556394] [drm:intel_dp_detect], DPCD: 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 127.556397] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:22:DP-1] disconnected
[ 127.846389] [drm:ironlake_panel_vdd_off_sync], PCH_PP_STATUS:
0x80000008 PCH_PP_CONTROL: 0xabcd0007
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-16 13:24 ` Ben Guthro
@ 2013-05-17 11:52 ` Ben Guthro
2013-05-17 13:26 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-17 11:52 UTC (permalink / raw)
To: intel-gfx
On Thu, May 16, 2013 at 9:24 AM, Ben Guthro <ben@guthro.net> wrote:
> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
>>> I am attempting to debug an issue with some Haswell laptop systems
>>> which do not restore their screen after resuming from S3 when running
>>> on the stable 3.8 kernel (3.8.13)
>>> The backlight is OK, but the screen is just black.
>>>
>>> In trying to determine what was going wrong, I tried looking at the
>>> output of intel_reg_dumper, in a good, and bad case:
>>>
>>> diff -u good_reg.txt bad_reg.txt
>>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
>>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
>>> @@ -1,5 +1,4 @@
>>> - DCC: 0x00000000 (0x00000000f3400000
>>> 0x00000000f37fffff 0x00000000��
>>> -� )
>>> + DCC: 0x00000000 (0x00000000f3400000
>>> 0x00000000f37fffff 0x00000000��= � )
>>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
>>> disabled, ch0 enh disabled, flex disabled, ep not present)
>>> C0DRB0: 0x00000000 (0x0000)
>>> C0DRB1: 0x00000000 (0x0000)
>>> @@ -63,17 +62,17 @@
>>> PIPEA_DP_LINK_N: 0x00000000
>>> CURSOR_A_BASE: 0x01061000
>>> CURSOR_A_CONTROL: 0x04000027
>>> - CURSOR_A_POSITION: 0x03a3032f
>>> + CURSOR_A_POSITION: 0x01bb03fb
>>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
>>> clock, unknown mode, p1 = 0, p2 = 0)
>>> DPLL_A_MD: 0x00000000
>>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
>>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
>>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
>>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
>>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
>>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
>>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
>>> + HBLANK_A: 0x00000000 (1 start, 1 end)
>>> + HSYNC_A: 0x00000000 (1 start, 1 end)
>>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
>>> + VBLANK_A: 0x00000000 (1 start, 1 end)
>>> + VSYNC_A: 0x00000000 (1 start, 1 end)
>>> BCLRPAT_A: 0x00000000
>>> VSYNCSHIFT_A: 0x00000000
>>> DSPBCNTR: 0x00004000 (disabled, pipe A)
>>>
>>>
>>> It appears the registers that are saved, and restored in
>>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
>>> properly.
>>>
>>> When I put some debug in, I discovered that it was bailing out of
>>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
>>> However, it was set at the end of i915_init()
>>> This, of course, confuses me.
>>>
>>> Am I seeing memory corruption here?
>>
>> It looks like I misread the code here, inversing an if statement state.
>>
>> That said, I don't really have any clues as to why the display is
>> black after resuming from S3
It appears that S3 is not necessary.
I can reproduce the black screen with just vbetool:
vbetool dpms off
vbetool dpms on
Does this suggest a bios issue?
>>
>> Is this an eDP training issue? Are there any changesets I can try backporting?
>> I tried this, but it didn't seem to help:
>> https://patchwork.kernel.org/patch/2516601/
>
>
> Below is a serial dump with drm.debug=4, after resuming from S3
>
> If anyone sees anything awry, being pointed in the right direction
> would be appreciated:
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-17 11:52 ` Ben Guthro
@ 2013-05-17 13:26 ` Ben Guthro
2013-05-21 8:00 ` Daniel Vetter
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-17 13:26 UTC (permalink / raw)
To: intel-gfx
On Fri, May 17, 2013 at 7:52 AM, Ben Guthro <ben@guthro.net> wrote:
> On Thu, May 16, 2013 at 9:24 AM, Ben Guthro <ben@guthro.net> wrote:
>> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
>>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
>>>> I am attempting to debug an issue with some Haswell laptop systems
>>>> which do not restore their screen after resuming from S3 when running
>>>> on the stable 3.8 kernel (3.8.13)
>>>> The backlight is OK, but the screen is just black.
>>>>
>>>> In trying to determine what was going wrong, I tried looking at the
>>>> output of intel_reg_dumper, in a good, and bad case:
>>>>
>>>> diff -u good_reg.txt bad_reg.txt
>>>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
>>>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
>>>> @@ -1,5 +1,4 @@
>>>> - DCC: 0x00000000 (0x00000000f3400000
>>>> 0x00000000f37fffff 0x00000000��
>>>> -� )
>>>> + DCC: 0x00000000 (0x00000000f3400000
>>>> 0x00000000f37fffff 0x00000000��= � )
>>>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
>>>> disabled, ch0 enh disabled, flex disabled, ep not present)
>>>> C0DRB0: 0x00000000 (0x0000)
>>>> C0DRB1: 0x00000000 (0x0000)
>>>> @@ -63,17 +62,17 @@
>>>> PIPEA_DP_LINK_N: 0x00000000
>>>> CURSOR_A_BASE: 0x01061000
>>>> CURSOR_A_CONTROL: 0x04000027
>>>> - CURSOR_A_POSITION: 0x03a3032f
>>>> + CURSOR_A_POSITION: 0x01bb03fb
>>>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
>>>> clock, unknown mode, p1 = 0, p2 = 0)
>>>> DPLL_A_MD: 0x00000000
>>>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
>>>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
>>>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
>>>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
>>>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
>>>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
>>>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
>>>> + HBLANK_A: 0x00000000 (1 start, 1 end)
>>>> + HSYNC_A: 0x00000000 (1 start, 1 end)
>>>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
>>>> + VBLANK_A: 0x00000000 (1 start, 1 end)
>>>> + VSYNC_A: 0x00000000 (1 start, 1 end)
>>>> BCLRPAT_A: 0x00000000
>>>> VSYNCSHIFT_A: 0x00000000
>>>> DSPBCNTR: 0x00004000 (disabled, pipe A)
>>>>
>>>>
>>>> It appears the registers that are saved, and restored in
>>>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
>>>> properly.
>>>>
>>>> When I put some debug in, I discovered that it was bailing out of
>>>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
>>>> However, it was set at the end of i915_init()
>>>> This, of course, confuses me.
>>>>
>>>> Am I seeing memory corruption here?
>>>
>>> It looks like I misread the code here, inversing an if statement state.
>>>
>>> That said, I don't really have any clues as to why the display is
>>> black after resuming from S3
>
> It appears that S3 is not necessary.
>
> I can reproduce the black screen with just vbetool:
> vbetool dpms off
> vbetool dpms on
>
> Does this suggest a bios issue?
This can be reliably reproduced on this machine, and worked around by
saving the vbestate, and restoring it after the fact:
(in a working state)
vbetool vbestate save > vbe.save
break the system:
vbetool dpms off
vbetool dpms on
The following brings the screen back, but in a low resolution corner of X:
vbetool vbestate restore < vbe.save
And then we can get the full resolution back with the following:
xrandr --output eDP1 --off
xrandr --output eDP1 --auto
This is clearly not an ideal solution to make a product out of.
Does this point to a BIOS issue?
Is anyone out there?
>
>
>
>>>
>>> Is this an eDP training issue? Are there any changesets I can try backporting?
>>> I tried this, but it didn't seem to help:
>>> https://patchwork.kernel.org/patch/2516601/
>>
>>
>> Below is a serial dump with drm.debug=4, after resuming from S3
>>
>> If anyone sees anything awry, being pointed in the right direction
>> would be appreciated:
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-17 13:26 ` Ben Guthro
@ 2013-05-21 8:00 ` Daniel Vetter
2013-05-21 13:44 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Vetter @ 2013-05-21 8:00 UTC (permalink / raw)
To: Ben Guthro; +Cc: intel-gfx
On Fri, May 17, 2013 at 09:26:18AM -0400, Ben Guthro wrote:
> On Fri, May 17, 2013 at 7:52 AM, Ben Guthro <ben@guthro.net> wrote:
> > On Thu, May 16, 2013 at 9:24 AM, Ben Guthro <ben@guthro.net> wrote:
> >> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
> >>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
> >>>> I am attempting to debug an issue with some Haswell laptop systems
> >>>> which do not restore their screen after resuming from S3 when running
> >>>> on the stable 3.8 kernel (3.8.13)
> >>>> The backlight is OK, but the screen is just black.
> >>>>
> >>>> In trying to determine what was going wrong, I tried looking at the
> >>>> output of intel_reg_dumper, in a good, and bad case:
> >>>>
> >>>> diff -u good_reg.txt bad_reg.txt
> >>>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
> >>>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
> >>>> @@ -1,5 +1,4 @@
> >>>> - DCC: 0x00000000 (0x00000000f3400000
> >>>> 0x00000000f37fffff 0x00000000��
> >>>> -� )
> >>>> + DCC: 0x00000000 (0x00000000f3400000
> >>>> 0x00000000f37fffff 0x00000000��= � )
> >>>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
> >>>> disabled, ch0 enh disabled, flex disabled, ep not present)
> >>>> C0DRB0: 0x00000000 (0x0000)
> >>>> C0DRB1: 0x00000000 (0x0000)
> >>>> @@ -63,17 +62,17 @@
> >>>> PIPEA_DP_LINK_N: 0x00000000
> >>>> CURSOR_A_BASE: 0x01061000
> >>>> CURSOR_A_CONTROL: 0x04000027
> >>>> - CURSOR_A_POSITION: 0x03a3032f
> >>>> + CURSOR_A_POSITION: 0x01bb03fb
> >>>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
> >>>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
> >>>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
> >>>> clock, unknown mode, p1 = 0, p2 = 0)
> >>>> DPLL_A_MD: 0x00000000
> >>>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
> >>>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
> >>>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
> >>>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
> >>>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
> >>>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
> >>>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
> >>>> + HBLANK_A: 0x00000000 (1 start, 1 end)
> >>>> + HSYNC_A: 0x00000000 (1 start, 1 end)
> >>>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
> >>>> + VBLANK_A: 0x00000000 (1 start, 1 end)
> >>>> + VSYNC_A: 0x00000000 (1 start, 1 end)
> >>>> BCLRPAT_A: 0x00000000
> >>>> VSYNCSHIFT_A: 0x00000000
> >>>> DSPBCNTR: 0x00004000 (disabled, pipe A)
> >>>>
> >>>>
> >>>> It appears the registers that are saved, and restored in
> >>>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
> >>>> properly.
> >>>>
> >>>> When I put some debug in, I discovered that it was bailing out of
> >>>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
> >>>> However, it was set at the end of i915_init()
> >>>> This, of course, confuses me.
> >>>>
> >>>> Am I seeing memory corruption here?
> >>>
> >>> It looks like I misread the code here, inversing an if statement state.
> >>>
> >>> That said, I don't really have any clues as to why the display is
> >>> black after resuming from S3
> >
> > It appears that S3 is not necessary.
> >
> > I can reproduce the black screen with just vbetool:
> > vbetool dpms off
> > vbetool dpms on
> >
> > Does this suggest a bios issue?
>
> This can be reliably reproduced on this machine, and worked around by
> saving the vbestate, and restoring it after the fact:
>
> (in a working state)
> vbetool vbestate save > vbe.save
>
> break the system:
> vbetool dpms off
> vbetool dpms on
This will break kms since now you have the vbios and the linux kms driver
fighting over the same piece of hw. Does
xset dpms force off
xset dpms force on
cause similar issues?
If not please make sure that vbetool isn't badly interfering with the
kernel modeset driver on suspend/resume. At least looking at your dmesg
and reg dumps vbe wreaking havoc with the kms driver seems like a rather
likely scenario. Also, can you please test latest 3.10-rc kernels?
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-21 8:00 ` Daniel Vetter
@ 2013-05-21 13:44 ` Ben Guthro
2013-05-21 13:53 ` Ben Guthro
2013-05-21 14:02 ` Daniel Vetter
0 siblings, 2 replies; 11+ messages in thread
From: Ben Guthro @ 2013-05-21 13:44 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
On Tue, May 21, 2013 at 4:00 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, May 17, 2013 at 09:26:18AM -0400, Ben Guthro wrote:
>> On Fri, May 17, 2013 at 7:52 AM, Ben Guthro <ben@guthro.net> wrote:
>> > On Thu, May 16, 2013 at 9:24 AM, Ben Guthro <ben@guthro.net> wrote:
>> >> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
>> >>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
>> >>>> I am attempting to debug an issue with some Haswell laptop systems
>> >>>> which do not restore their screen after resuming from S3 when running
>> >>>> on the stable 3.8 kernel (3.8.13)
>> >>>> The backlight is OK, but the screen is just black.
>> >>>>
>> >>>> In trying to determine what was going wrong, I tried looking at the
>> >>>> output of intel_reg_dumper, in a good, and bad case:
>> >>>>
>> >>>> diff -u good_reg.txt bad_reg.txt
>> >>>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
>> >>>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
>> >>>> @@ -1,5 +1,4 @@
>> >>>> - DCC: 0x00000000 (0x00000000f3400000
>> >>>> 0x00000000f37fffff 0x00000000��
>> >>>> -� )
>> >>>> + DCC: 0x00000000 (0x00000000f3400000
>> >>>> 0x00000000f37fffff 0x00000000��= � )
>> >>>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
>> >>>> disabled, ch0 enh disabled, flex disabled, ep not present)
>> >>>> C0DRB0: 0x00000000 (0x0000)
>> >>>> C0DRB1: 0x00000000 (0x0000)
>> >>>> @@ -63,17 +62,17 @@
>> >>>> PIPEA_DP_LINK_N: 0x00000000
>> >>>> CURSOR_A_BASE: 0x01061000
>> >>>> CURSOR_A_CONTROL: 0x04000027
>> >>>> - CURSOR_A_POSITION: 0x03a3032f
>> >>>> + CURSOR_A_POSITION: 0x01bb03fb
>> >>>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>> >>>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>> >>>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
>> >>>> clock, unknown mode, p1 = 0, p2 = 0)
>> >>>> DPLL_A_MD: 0x00000000
>> >>>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
>> >>>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
>> >>>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
>> >>>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
>> >>>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
>> >>>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
>> >>>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
>> >>>> + HBLANK_A: 0x00000000 (1 start, 1 end)
>> >>>> + HSYNC_A: 0x00000000 (1 start, 1 end)
>> >>>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
>> >>>> + VBLANK_A: 0x00000000 (1 start, 1 end)
>> >>>> + VSYNC_A: 0x00000000 (1 start, 1 end)
>> >>>> BCLRPAT_A: 0x00000000
>> >>>> VSYNCSHIFT_A: 0x00000000
>> >>>> DSPBCNTR: 0x00004000 (disabled, pipe A)
>> >>>>
>> >>>>
>> >>>> It appears the registers that are saved, and restored in
>> >>>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
>> >>>> properly.
>> >>>>
>> >>>> When I put some debug in, I discovered that it was bailing out of
>> >>>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
>> >>>> However, it was set at the end of i915_init()
>> >>>> This, of course, confuses me.
>> >>>>
>> >>>> Am I seeing memory corruption here?
>> >>>
>> >>> It looks like I misread the code here, inversing an if statement state.
>> >>>
>> >>> That said, I don't really have any clues as to why the display is
>> >>> black after resuming from S3
>> >
>> > It appears that S3 is not necessary.
>> >
>> > I can reproduce the black screen with just vbetool:
>> > vbetool dpms off
>> > vbetool dpms on
>> >
>> > Does this suggest a bios issue?
>>
>> This can be reliably reproduced on this machine, and worked around by
>> saving the vbestate, and restoring it after the fact:
>>
>> (in a working state)
>> vbetool vbestate save > vbe.save
>>
>> break the system:
>> vbetool dpms off
>> vbetool dpms on
>
> This will break kms since now you have the vbios and the linux kms driver
> fighting over the same piece of hw. Does
>
> xset dpms force off
> xset dpms force on
>
> cause similar issues?
No, these work as expected (on 3.8)
I didn't realize that these broke with KMS. I'll stick with the S3 reproduction.
>
> If not please make sure that vbetool isn't badly interfering with the
> kernel modeset driver on suspend/resume. At least looking at your dmesg
> and reg dumps vbe wreaking havoc with the kms driver seems like a rather
> likely scenario. Also, can you please test latest 3.10-rc kernels?
3.10-rc2 doesn't seem to work at all - it boots to a black screen every time.
Ben
>
> Cheers, Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-21 13:44 ` Ben Guthro
@ 2013-05-21 13:53 ` Ben Guthro
2013-05-21 14:02 ` Daniel Vetter
1 sibling, 0 replies; 11+ messages in thread
From: Ben Guthro @ 2013-05-21 13:53 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
On Tue, May 21, 2013 at 9:44 AM, Ben Guthro <ben@guthro.net> wrote:
> On Tue, May 21, 2013 at 4:00 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Fri, May 17, 2013 at 09:26:18AM -0400, Ben Guthro wrote:
>>> On Fri, May 17, 2013 at 7:52 AM, Ben Guthro <ben@guthro.net> wrote:
>>> > On Thu, May 16, 2013 at 9:24 AM, Ben Guthro <ben@guthro.net> wrote:
>>> >> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro <ben@guthro.net> wrote:
>>> >>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro <ben@guthro.net> wrote:
>>> >>>> I am attempting to debug an issue with some Haswell laptop systems
>>> >>>> which do not restore their screen after resuming from S3 when running
>>> >>>> on the stable 3.8 kernel (3.8.13)
>>> >>>> The backlight is OK, but the screen is just black.
>>> >>>>
>>> >>>> In trying to determine what was going wrong, I tried looking at the
>>> >>>> output of intel_reg_dumper, in a good, and bad case:
>>> >>>>
>>> >>>> diff -u good_reg.txt bad_reg.txt
>>> >>>> --- good_reg.txt 2013-05-14 15:08:44.361997000 +0000
>>> >>>> +++ bad_reg.txt 2013-05-14 15:09:20.480000000 +0000
>>> >>>> @@ -1,5 +1,4 @@
>>> >>>> - DCC: 0x00000000 (0x00000000f3400000
>>> >>>> 0x00000000f37fffff 0x00000000��
>>> >>>> -� )
>>> >>>> + DCC: 0x00000000 (0x00000000f3400000
>>> >>>> 0x00000000f37fffff 0x00000000��= � )
>>> >>>> CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh
>>> >>>> disabled, ch0 enh disabled, flex disabled, ep not present)
>>> >>>> C0DRB0: 0x00000000 (0x0000)
>>> >>>> C0DRB1: 0x00000000 (0x0000)
>>> >>>> @@ -63,17 +62,17 @@
>>> >>>> PIPEA_DP_LINK_N: 0x00000000
>>> >>>> CURSOR_A_BASE: 0x01061000
>>> >>>> CURSOR_A_CONTROL: 0x04000027
>>> >>>> - CURSOR_A_POSITION: 0x03a3032f
>>> >>>> + CURSOR_A_POSITION: 0x01bb03fb
>>> >>>> FPA0: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>> >>>> FPA1: 0x00000000 (n = 0, m1 = 0, m2 = 0)
>>> >>>> DPLL_A: 0x00000000 (disabled, non-dvo, VGA, default
>>> >>>> clock, unknown mode, p1 = 0, p2 = 0)
>>> >>>> DPLL_A_MD: 0x00000000
>>> >>>> - HTOTAL_A: 0x0821077f (1920 active, 2082 total)
>>> >>>> - HBLANK_A: 0x0821077f (1920 start, 2082 end)
>>> >>>> - HSYNC_A: 0x081307af (1968 start, 2068 end)
>>> >>>> - VTOTAL_A: 0x045f0437 (1080 active, 1120 total)
>>> >>>> - VBLANK_A: 0x045f0437 (1080 start, 1120 end)
>>> >>>> - VSYNC_A: 0x044b0441 (1090 start, 1100 end)
>>> >>>> + HTOTAL_A: 0x00000000 (1 active, 1 total)
>>> >>>> + HBLANK_A: 0x00000000 (1 start, 1 end)
>>> >>>> + HSYNC_A: 0x00000000 (1 start, 1 end)
>>> >>>> + VTOTAL_A: 0x00000000 (1 active, 1 total)
>>> >>>> + VBLANK_A: 0x00000000 (1 start, 1 end)
>>> >>>> + VSYNC_A: 0x00000000 (1 start, 1 end)
>>> >>>> BCLRPAT_A: 0x00000000
>>> >>>> VSYNCSHIFT_A: 0x00000000
>>> >>>> DSPBCNTR: 0x00004000 (disabled, pipe A)
>>> >>>>
>>> >>>>
>>> >>>> It appears the registers that are saved, and restored in
>>> >>>> i915_save_modeset_reg / i915_restore_modeset_reg is not working
>>> >>>> properly.
>>> >>>>
>>> >>>> When I put some debug in, I discovered that it was bailing out of
>>> >>>> i915_save_modeset_reg early since the DRIVER_MODESET bit was cleared.
>>> >>>> However, it was set at the end of i915_init()
>>> >>>> This, of course, confuses me.
>>> >>>>
>>> >>>> Am I seeing memory corruption here?
>>> >>>
>>> >>> It looks like I misread the code here, inversing an if statement state.
>>> >>>
>>> >>> That said, I don't really have any clues as to why the display is
>>> >>> black after resuming from S3
>>> >
>>> > It appears that S3 is not necessary.
>>> >
>>> > I can reproduce the black screen with just vbetool:
>>> > vbetool dpms off
>>> > vbetool dpms on
>>> >
>>> > Does this suggest a bios issue?
>>>
>>> This can be reliably reproduced on this machine, and worked around by
>>> saving the vbestate, and restoring it after the fact:
>>>
>>> (in a working state)
>>> vbetool vbestate save > vbe.save
>>>
>>> break the system:
>>> vbetool dpms off
>>> vbetool dpms on
>>
>> This will break kms since now you have the vbios and the linux kms driver
>> fighting over the same piece of hw. Does
>>
>> xset dpms force off
>> xset dpms force on
>>
>> cause similar issues?
>
> No, these work as expected (on 3.8)
> I didn't realize that these broke with KMS. I'll stick with the S3 reproduction.
>
>>
>> If not please make sure that vbetool isn't badly interfering with the
>> kernel modeset driver on suspend/resume. At least looking at your dmesg
>> and reg dumps vbe wreaking havoc with the kms driver seems like a rather
>> likely scenario.
vbetool was not installed on the system when I took those S3 dumps, so
it seems unlikely to be the root of the problem, IMO.
> Also, can you please test latest 3.10-rc kernels?
>
> 3.10-rc2 doesn't seem to work at all - it boots to a black screen every time.
>
> Ben
>
>>
>> Cheers, Daniel
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
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: debugging Haswell eDP black screen after S3
2013-05-21 13:44 ` Ben Guthro
2013-05-21 13:53 ` Ben Guthro
@ 2013-05-21 14:02 ` Daniel Vetter
2013-05-21 17:28 ` Ben Guthro
1 sibling, 1 reply; 11+ messages in thread
From: Daniel Vetter @ 2013-05-21 14:02 UTC (permalink / raw)
To: Ben Guthro; +Cc: intel-gfx
On Tue, May 21, 2013 at 3:44 PM, Ben Guthro <ben@guthro.net> wrote:
>> This will break kms since now you have the vbios and the linux kms driver
>> fighting over the same piece of hw. Does
>>
>> xset dpms force off
>> xset dpms force on
>>
>> cause similar issues?
>
> No, these work as expected (on 3.8)
> I didn't realize that these broke with KMS. I'll stick with the S3 reproduction.
Ok, so things are at least not terribly broken.
>> If not please make sure that vbetool isn't badly interfering with the
>> kernel modeset driver on suspend/resume. At least looking at your dmesg
>> and reg dumps vbe wreaking havoc with the kms driver seems like a rather
>> likely scenario. Also, can you please test latest 3.10-rc kernels?
>
> 3.10-rc2 doesn't seem to work at all - it boots to a black screen every time.
That otoh is ugly. Could be that though that this is the same (or a
similar bug) to your resume issue - in the last few kernel releases
we've tried very hard to unify the code between initial driver load at
boot-up and resume.
So can you please try to bisect where the boot-up regression has been
introduced between 3.8 and 3.10-rc2?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: debugging Haswell eDP black screen after S3
2013-05-21 14:02 ` Daniel Vetter
@ 2013-05-21 17:28 ` Ben Guthro
2013-05-28 20:43 ` Ben Guthro
0 siblings, 1 reply; 11+ messages in thread
From: Ben Guthro @ 2013-05-21 17:28 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
On Tue, May 21, 2013 at 10:02 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, May 21, 2013 at 3:44 PM, Ben Guthro <ben@guthro.net> wrote:
>>> This will break kms since now you have the vbios and the linux kms driver
>>> fighting over the same piece of hw. Does
>>>
>>> xset dpms force off
>>> xset dpms force on
>>>
>>> cause similar issues?
>>
>> No, these work as expected (on 3.8)
>> I didn't realize that these broke with KMS. I'll stick with the S3 reproduction.
>
> Ok, so things are at least not terribly broken.
>
>>> If not please make sure that vbetool isn't badly interfering with the
>>> kernel modeset driver on suspend/resume. At least looking at your dmesg
>>> and reg dumps vbe wreaking havoc with the kms driver seems like a rather
>>> likely scenario. Also, can you please test latest 3.10-rc kernels?
>>
>> 3.10-rc2 doesn't seem to work at all - it boots to a black screen every time.
>
> That otoh is ugly. Could be that though that this is the same (or a
> similar bug) to your resume issue - in the last few kernel releases
> we've tried very hard to unify the code between initial driver load at
> boot-up and resume.
Perhaps I should qualify "at all"
It seems that it fails somewhat late in the boot process. If I remove
the "boot splash" cli params, I can see it transition into the high
res mode, and seemingly get into init.
However, even if I boot to single user mode, the screen goes black.
Unfortunately, both times I tried to test this, and then reboot, I
ended up at a "grub rescue" prompt, with an unusable system.
>
> So can you please try to bisect where the boot-up regression has been
> introduced between 3.8 and 3.10-rc2?
I'm not sure I'll be able to do this.
With the failure condition I describe above, I am unable to even ssh
into this machine to debug, nevermind install a new kernel.
This means I need to generate a new kernel, and install kit with that
kernel for every bisection test.
This may be more time than I am able to dedicate to this problem - but I'll try.
Ben
>
> Thanks, Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: debugging Haswell eDP black screen after S3
2013-05-21 17:28 ` Ben Guthro
@ 2013-05-28 20:43 ` Ben Guthro
0 siblings, 0 replies; 11+ messages in thread
From: Ben Guthro @ 2013-05-28 20:43 UTC (permalink / raw)
To: Daniel Vetter; +Cc: intel-gfx
On Tue, May 21, 2013 at 1:28 PM, Ben Guthro <ben@guthro.net> wrote:
> On Tue, May 21, 2013 at 10:02 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Tue, May 21, 2013 at 3:44 PM, Ben Guthro <ben@guthro.net> wrote:
>>>> This will break kms since now you have the vbios and the linux kms driver
>>>> fighting over the same piece of hw. Does
>>>>
>>>> xset dpms force off
>>>> xset dpms force on
>>>>
>>>> cause similar issues?
>>>
>>> No, these work as expected (on 3.8)
>>> I didn't realize that these broke with KMS. I'll stick with the S3 reproduction.
>>
>> Ok, so things are at least not terribly broken.
>>
>>>> If not please make sure that vbetool isn't badly interfering with the
>>>> kernel modeset driver on suspend/resume. At least looking at your dmesg
>>>> and reg dumps vbe wreaking havoc with the kms driver seems like a rather
>>>> likely scenario. Also, can you please test latest 3.10-rc kernels?
>>>
>>> 3.10-rc2 doesn't seem to work at all - it boots to a black screen every time.
>>
>> That otoh is ugly. Could be that though that this is the same (or a
>> similar bug) to your resume issue - in the last few kernel releases
>> we've tried very hard to unify the code between initial driver load at
>> boot-up and resume.
>
> Perhaps I should qualify "at all"
>
> It seems that it fails somewhat late in the boot process. If I remove
> the "boot splash" cli params, I can see it transition into the high
> res mode, and seemingly get into init.
> However, even if I boot to single user mode, the screen goes black.
>
> Unfortunately, both times I tried to test this, and then reboot, I
> ended up at a "grub rescue" prompt, with an unusable system.
>
>>
>> So can you please try to bisect where the boot-up regression has been
>> introduced between 3.8 and 3.10-rc2?
>
> I'm not sure I'll be able to do this.
> With the failure condition I describe above, I am unable to even ssh
> into this machine to debug, nevermind install a new kernel.
> This means I need to generate a new kernel, and install kit with that
> kernel for every bisection test.
>
> This may be more time than I am able to dedicate to this problem - but I'll try.
>
> Ben
It appears I did not CC the list on my last 2 replies.
My apologies - I'll re-paste them below.
I tried to bisect this, but was unsuccessful, in that I didn't seem to
have a reproducible test case to get back into this failure condition.
It seemed that it always would succeed for me...which of course makes
bisecting near impossible.
I tried updating to 3.10-RC3...well, actually to this changeset at the
tip of Linus' tree:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=58f8bbd2e39c3732c55698494338ee19a92c53a0
I can get X to come up now on this machine - albeit very slowly.
Once it comes up, it seems to hang, and respawn
I get a lot of these in the log now, as well:
[ 392.195734] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
Things in the log that look suspicious to me are:
[ 34.293452] [drm:intel_pipe_set_base] *ERROR* pin & fence failed
[ 34.293486] [drm:intel_crtc_set_config] *ERROR* failed to set mode
on [CRTC:3], err = -28
I get the following errors in the X log, that prevent it from coming up:
[ 76.142] (EE) intel(0): failed to set mode: No space left on device
[ 76.142]
Fatal server error:
[ 76.142] AddScreen/ScreenInit failed for driver 0
[ 76.142]
[ 76.142] (EE)
Xorg also crashes in the following manner:
[ 218.876] (EE) Backtrace:
[ 218.880] (EE) 0: X (xorg_backtrace+0x34) [0x7fe44fff9754]
[ 218.880] (EE) 1: X (0x7fe44fe44000+0x1b96a9) [0x7fe44fffd6a9]
[ 218.880] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fe44f16a000+0xfcb0) [0x7fe44f179cb0]
[ 218.880] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(0x7fe44ddcf000+0x148c6b) [0x7fe44df17c6b]
[ 218.880] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so
(0x7fe44cb5a000+0x17c36) [0x7fe44cb71c36]
[ 218.880] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so
(0x7fe44cb5a000+0x19857) [0x7fe44cb73857]
[ 218.880] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so
(0x7fe44cb5a000+0xed429) [0x7fe44cc47429]
[ 218.880] (EE) 7: X (0x7fe44fe44000+0x13e8ac) [0x7fe44ff828ac]
[ 218.880] (EE) 8: X (0x7fe44fe44000+0x5239e) [0x7fe44fe9639e]
[ 218.880] (EE) 9: X (0x7fe44fe44000+0x557a1) [0x7fe44fe997a1]
[ 218.880] (EE) 10: X (0x7fe44fe44000+0x4415a) [0x7fe44fe8815a]
[ 218.880] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xed) [0x7fe44ddf076d]
[ 218.880] (EE) 12: X (0x7fe44fe44000+0x444b1) [0x7fe44fe884b1]
[ 218.880] (EE)
[ 218.880] (EE) Bus error at address 0x7fe44a6c9080
[ 218.880]
Fatal server error:
[ 218.881] Caught signal 7 (Bus error). Server aborting
[ 218.881]
[ 218.881] (EE)
I recognize that this isn't terribly helpful without the symbol
resolution. I tried installing debug symbols, but they didn't seem to
help.
Ben
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2013-05-28 20:43 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-14 21:01 debugging Haswell eDP black screen after S3 Ben Guthro
2013-05-15 20:42 ` Ben Guthro
2013-05-16 13:24 ` Ben Guthro
2013-05-17 11:52 ` Ben Guthro
2013-05-17 13:26 ` Ben Guthro
2013-05-21 8:00 ` Daniel Vetter
2013-05-21 13:44 ` Ben Guthro
2013-05-21 13:53 ` Ben Guthro
2013-05-21 14:02 ` Daniel Vetter
2013-05-21 17:28 ` Ben Guthro
2013-05-28 20:43 ` Ben Guthro
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.