screen not lighting up on resume when using kms

Submitted by eruditehermit

Assigned to Default DRI bug account

Link to original bug (#23103)

Description

When I try to suspend and resume with kernel mode setting, I am able to suspend but on resume, the screen is completely black and the laptop screen does not turn back on. The screen doesn't emit any light as it does when the screen shows a black colour. I am able to perform a VT switch with Ctrl+Alt+F1 and reboot the machine with ctrl+alt+del.

My Setup:
Laptop Dell Inspiron 8600
Radeon Mobility 9600 M10/M11 RV350 4E50
Kernel 2.6.31-5
radeon driver git 2009/07/29
the debug and messages files are with drm.debug=15

added Radeon bugzilla labels

eruditehermit uploaded an attachment:

Attachment 28288, "/var/log/debug":
suspendresume_debug.txt.tar.bz2

eruditehermit uploaded an attachment:

Attachment 28289, "/var/log/messages":
suspendresmume_messages.txt

eruditehermit said:

This is the output of radeontool regs:

RADEON_DAC_CNTL ff008002
RADEON_DAC_EXT_CNTL 00000000
RADEON_DAC_MACRO_CNTL 00070705
RADEON_DAC_CNTL2 00000000
RADEON_TV_DAC_CNTL 07770142
RADEON_DISP_OUTPUT_CNTL 1000000a
RADEON_CONFIG_MEMSIZE 08000000
RADEON_AUX_SC_CNTL 00000000
RADEON_CRTC_EXT_CNTL 00000041
RADEON_CRTC_GEN_CNTL 03200600
RADEON_CRTC2_GEN_CNTL 36800000
RADEON_DEVICE_ID 00004e50
RADEON_DISP_MISC_CNTL 5b300600
RADEON_GPIO_MONID 00000300
RADEON_GPIO_MONIDB 00000000
RADEON_GPIO_CRT2_DDC 00000000
RADEON_GPIO_DVI_DDC 00000300
RADEON_GPIO_VGA_DDC 00000300
RADEON_LVDS_GEN_CNTL 003cffa5
RADEON_LVDS_PLL_CNTL 00091282
RADEON_FP_GEN_CNTL 01430000
RADEON_FP2_GEN_CNTL 1000000a
RADEON_PIXCLKS_CNTL 3310f8c0
RADEON_MEM_TIMING_CNTL 1a251a12

Alex Deucher @agd5f said:

Can you use the git version of radeontool:
http://cgit.freedesktop.org/~airlied/radeontool

before suspending, run:
radeontool regmatch '' > working.regs

then after resume, run:
radeontool regmatch '' > broken.regs

and attach the reg dumps to this bug.

eruditehermit submitted a patch:

Here is the register dump before suspend from radeontool as requested in comment 4

Patch 28325, "working.regs (register dump before suspend)":
working.regs

eruditehermit submitted a patch:

This is the radeontool dump after resume from suspend. I had to ssh into the machine to get this dump as the screen is black. This is in response to comment 4.

Patch 28326, "broken.regs (register dump after resume)":
broken.regs

Alex Deucher @agd5f said:

Of the registers dumped, these look like possible candidates:

--- working.regs 2009-08-03 22:18:01.000000000 -0400
+++ broken.regs 2009-08-03 22:18:15.000000000 -0400

-CONFIG_CNTL (00e0) 0x000c0100 (786688)
+CONFIG_CNTL (00e0) 0x000c0000 (786432)

-FP_GEN_CNTL (0284) 0x01430000 (21168128)
+FP_GEN_CNTL (0284) 0x00004008 (16392)

-CLK_PIN_CNTL (CL: 0001) 0x0a098015 (168394773)
+CLK_PIN_CNTL (CL: 0001) 0x00018015 (98325)

-SS_INT_CNTL (CL: 0033) 0x00200271 (2097777)
+SS_INT_CNTL (CL: 0033) 0x00200000 (2097152)

-LVDS_PLL_CNTL (02d4) 0x00091282 (594562)
+LVDS_PLL_CNTL (02d4) 0x0009128c (594572)

You can try setting the working value of the reg with radeontool, e.g.:
radeontool regset LVDS_PLL_CNTL 0x00091282
And see if changing any of them help.

eruditehermit said:

I tried setting all of the registers and none were able to restore the screen.(In reply to comment 7)

eruditehermit said:

Airlied and glisse suggested connecting an external monitor and then performing suspend and resume. Upon resume, the external LCD does turn on, but the output is corrupted as shown in the attachment labeled resume_corruption.

eruditehermit uploaded an attachment:

Attachment 29408, "resume_corruption picture":

Yang Zhao @yzhao said:

Similar symptoms to bug #23290 and bug #23273

eruditehermit uploaded an attachment:

This is the dmesg output when performing a resume from suspend. This was requested by airlied on IRC.

Attachment 31055, "dmesg upon resume":
dmesg_resume.txt

eruditehermit uploaded an attachment:

Here is the m10.regs file from the command vbetool post 2>m10.regs as requested by airlied on IRC.

Attachment 31056, "output from vbetool post 2>m10.regs":
m10.regs.tar.bz2

Dave Airlie said:

http://people.freedesktop.org/~airlied/scratch/0001-drm-radeon-kms-add-legacy-LVDS-spread-spectrum-suppo.patch

cane you try that patch on top of a newish drm-next kernel

Let me know if you stop booting, if resume still fails can you
dump the broken.regs file again and attach.

eruditehermit uploaded an attachment:

This is the dump from radeontool of the working regs before I suspend using a kernel with kms enabled patched with airlied 0001-drm-radeon-kms-add-legacy-LVDS-spread-spectrum-suppo.patch

Attachment 31125, "working regs after airlied 0001 patch":
working0001patch.regs

eruditehermit uploaded an attachment:

This is the radeontool dump after resuming from suspend on a kernel with kms enabled and airlied's 0001-drm-radeon-kms-add-legacy-LVDS-spread-spectrum-suppo.patch. With this kernel and kms the screen has corruption even before suspend, on the left side. It is fuzzy and there is some doubling of pixels that shifts the right edge of the display off the right edge of the physical screen.

Attachment 31126, "registers after resume from suspend.":
broken0001patch.regs

Dave Airlie said:

http://people.freedesktop.org/~airlied/scratch/combios_readback.diff

please try this.

Christian Hartmann said:

I followed this bug issue since some days, cause on my system

thinkpad T30
Ati Radeon Mobility M7 7500
20091112\2.6.31-rc9_drm-next

--- regs.before 2009-11-12 16:51:53.000000000 +0100
+++ regs.after 2009-11-12 18:24:12.000000000 +0100
@@ -4,8 +4,8 @@
RADEON_DISP_OUTPUT_CNTL=10000002
RADEON_CONFIG_MEMSIZE=01000000
RADEON_AUX_SC_CNTL=00000000
-RADEON_CRTC_EXT_CNTL=0d000040
-RADEON_CRTC_GEN_CNTL=03200600
+RADEON_CRTC_EXT_CNTL=0b000040
+RADEON_CRTC_GEN_CNTL=03000600
RADEON_CRTC2_GEN_CNTL=36800000
RADEON_DEVICE_ID=00004c57
RADEON_DISP_MISC_CNTL=5b300600

attaching dmesg before and the working + the broken regs

Christian Hartmann uploaded an attachment:

Attachment 31147, "dmesg before":
dmesg_before.txt