Bug 23103

Summary: screen not lighting up on resume when using kms
Product: DRI Reporter: eruditehermit <eruditehermit>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: bryce, cornogle, freedesktop, preining
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
/var/log/debug
none
/var/log/messages
none
working.regs (register dump before suspend)
none
broken.regs (register dump after resume)
none
resume_corruption picture
none
dmesg upon resume
none
output from vbetool post 2>m10.regs
none
working regs after airlied 0001 patch
none
registers after resume from suspend.
none
dmesg before
none
broken.regs.txt
none
working.regs.txt
none
dmesg after resume
none
working.regs
none
broken.regs after resume
none
kern.log
none
broken.regs after resume from suspend running kernel drm-next with patch in comment 27.
none
working.regs before suspend/resume on drm-next kernel with patch from comment 27.
none
working.regs before suspend/resume on drm-next kernel with patch from comment 27. Real version.
none
broken.regs after resume from suspend running kernel drm-next with patch in comment 27. Real version.
none
registers before suspend with combios-v3 patch.
none
Registers after resume from suspend with combios-v3 patch.
none
Registers after resume from suspend with combios-v3 patch. 2nd try.
none
registers before suspend with combios-v3 patch. 2nd try.
none
kms Xorg.0.conf before suspending.
none
kms Xorg.0.conf after resuming.
none
Here are the registers before suspend.
none
Broken registers after resume.
none
dmesg after a resume
none
working.regs before suspend
none
broken.regs after resume
none
echo -n mem > sys/power/state
none
b) therefore some icons (the gnome-panel icons) are now screwed up now.
none
dmesg upon resume 2.6.33 drm linus branch of airlied tree
none
radeontool register dump before suspend (working state) 20100310 with VGA plugged in.
none
radeontool register dump after resume (broken state) 20100310 with VGA plugged in.
none
lspci output before suspend (working state) with VGA plugged in.
none
lspci output after resume (broken state) with VGA plugged in.
none
register dumps and mmapr command output
none
Register dumps and radeon_vram_mm radeon_pm_info
none
Register dumps and radeon_vram_mm radeon_pm_info using VT ONLY (NO X SERVER)
none
all registers with agpmode=-1 VGA and LVDS plugged in after resume.
none
all registers with agpmode=-1 VGA and LVDS plugged in before suspend.
none
all registers with agpmode=-1 VGA and LVDS plugged in after resume.
none
all registers with agpmode=-1 VGA and LVDS plugged in before suspend.
none
all registers with colortiling off agpmode=-1 VGA and LVDS plugged in after resume.
none
all registers with agpmode=-1 colortiling off, VGA and LVDS plugged in before suspend.
none
all registers with agpmode=-1 colortiling off VGA and LVDS plugged in before suspend new registers + switched to VT with X running.
none
all registers with agpmode=-1 colortiling off VGA and LVDS plugged in after resume new registers + switched to VT with X running.
none
log from vbtracetool obtained using airlied's instructions posted above
none
unloading radeon before suspend, resuming and if no text mode comes up, running vbtracetool, then loading radeon none

Description eruditehermit 2009-08-03 03:29:38 UTC
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
Comment 1 eruditehermit 2009-08-03 03:36:02 UTC
Created attachment 28288 [details]
/var/log/debug
Comment 2 eruditehermit 2009-08-03 03:37:07 UTC
Created attachment 28289 [details]
/var/log/messages
Comment 3 eruditehermit 2009-08-03 04:02:52 UTC
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
Comment 4 Alex Deucher 2009-08-03 08:53:24 UTC
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.
Comment 5 eruditehermit 2009-08-03 19:13:26 UTC
Created attachment 28325 [details] [review]
working.regs (register dump before suspend)

Here is the register dump before suspend from radeontool as requested in comment #4
Comment 6 eruditehermit 2009-08-03 19:14:50 UTC
Created attachment 28326 [details] [review]
broken.regs (register dump after resume)

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.
Comment 7 Alex Deucher 2009-08-05 11:12:26 UTC
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.
Comment 8 eruditehermit 2009-08-06 05:31:10 UTC
I tried setting all of the registers and none were able to restore the screen.(In reply to comment #7)
Comment 9 eruditehermit 2009-09-11 01:54:24 UTC
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.
Comment 10 eruditehermit 2009-09-11 02:07:23 UTC
Created attachment 29408 [details]
resume_corruption picture
Comment 11 Yang Zhao 2009-09-11 02:17:00 UTC
Similar symptoms to bug #23290 and bug #23273
Comment 12 eruditehermit 2009-11-08 16:41:47 UTC
Created attachment 31055 [details]
dmesg upon resume

This is the dmesg output when performing a resume from suspend. This was requested by airlied on IRC.
Comment 13 eruditehermit 2009-11-08 21:03:02 UTC
Created attachment 31056 [details]
output from vbetool post 2>m10.regs

Here is the m10.regs file from the command vbetool post 2>m10.regs as requested by airlied on IRC.
Comment 14 Dave Airlie 2009-11-10 20:44:58 UTC
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.
Comment 15 eruditehermit 2009-11-11 21:44:34 UTC
Created attachment 31125 [details]
working regs after airlied 0001 patch

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
Comment 16 eruditehermit 2009-11-11 21:48:30 UTC
Created attachment 31126 [details]
registers after resume from suspend.

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.
Comment 17 Dave Airlie 2009-11-11 22:28:43 UTC
http://people.freedesktop.org/~airlied/scratch/combios_readback.diff

please try this.
Comment 18 Christian Hartmann 2009-11-12 15:56:24 UTC
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
Comment 19 Christian Hartmann 2009-11-12 16:01:48 UTC
Created attachment 31147 [details]
dmesg before
Comment 20 Christian Hartmann 2009-11-12 16:02:53 UTC
Created attachment 31148 [details]
broken.regs.txt
Comment 21 Christian Hartmann 2009-11-12 16:03:08 UTC
Created attachment 31149 [details]
working.regs.txt
Comment 22 Christian Hartmann 2009-11-12 16:04:29 UTC
Created attachment 31150 [details]
dmesg after resume

I will produce another dmesg with more information, these dmesgs are truncated cause (near oos)
Comment 23 Christian Hartmann 2009-11-13 05:42:46 UTC
Created attachment 31166 [details]
working.regs

update from today.
Comment 24 Christian Hartmann 2009-11-13 05:46:15 UTC
Created attachment 31167 [details]
broken.regs after resume

* resume works, but using X not possible, I see a square mouse pointer flickering as everytime trying to resume. I can see my desktop as before resume. but no input is possible, so going into the console and shutting down gdm/xorg
restarting Xorg/gdm does not help

After reboot everytghing is fine.
Comment 25 Christian Hartmann 2009-11-13 05:50:21 UTC
Created attachment 31168 [details]
kern.log

this kern.log contains  the boot before suspend to disk and the resume.
 have to stop X, cause of many

[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Comment 26 eruditehermit 2009-11-14 16:44:29 UTC
(In reply to comment #17)
> http://people.freedesktop.org/~airlied/scratch/combios_readback.diff
> 
> please try this.
> 

I tried this patch with a kernel built from drm-next. It did not work. It exhibits the same behavior as that described earlier in the bug (i.e. the backlight for the display doesn't turn on after resume).

Please advise about what to try next.
Comment 27 Dave Airlie 2009-11-19 20:26:13 UTC
http://people.freedesktop.org/~airlied/scratch/combios-readback.patch

another revision of this patch to test.


Also get the latest radeontool and redump the before/after regs, I added some more regs (use regmatch '*')
Comment 28 eruditehermit 2009-11-20 19:10:59 UTC
Created attachment 31360 [details]
broken.regs after resume from suspend running kernel drm-next with patch in comment 27.
Comment 29 eruditehermit 2009-11-20 19:11:45 UTC
Created attachment 31361 [details]
working.regs before suspend/resume on drm-next kernel with patch from comment 27.
Comment 30 eruditehermit 2009-11-20 19:13:18 UTC
(In reply to comment #27)
> http://people.freedesktop.org/~airlied/scratch/combios-readback.patch
> 
> another revision of this patch to test.
> 
> 
> Also get the latest radeontool and redump the before/after regs, I added some
> more regs (use regmatch '*')
> 

I attached the broken.regs and working.regs while running the kernel in drm-next (kernel 2.6.32-rc6) with the patch in comment 27. The result was the same as before. I am able to suspend but upon resume, the backlight for the screen doesn't turn back on for the LVDS.
Comment 31 eruditehermit 2009-11-22 16:47:57 UTC
Created attachment 31398 [details]
working.regs before suspend/resume on drm-next kernel with patch from comment 27. Real version.
Comment 32 eruditehermit 2009-11-22 16:48:22 UTC
Created attachment 31399 [details]
broken.regs after resume from suspend running kernel drm-next with patch in comment 27. Real version.
Comment 33 Dave Airlie 2009-11-22 17:08:33 UTC
http://people.freedesktop.org/~airlied/scratch/combios-readback-v3.patch

yet another patch attempt.
Comment 34 eruditehermit 2009-11-22 20:59:00 UTC
Created attachment 31400 [details]
registers before suspend with combios-v3 patch.

Registers before suspend when using kernel with the combios-v3 patch.
Comment 35 eruditehermit 2009-11-22 20:59:48 UTC
Created attachment 31401 [details]
Registers after resume from suspend with combios-v3 patch.

Registers after resume from suspend with kernel build with combios-v3 patch.
Comment 36 eruditehermit 2009-11-22 21:28:40 UTC
Created attachment 31402 [details]
Registers after resume from suspend with combios-v3 patch. 2nd try.
Comment 37 eruditehermit 2009-11-22 21:29:04 UTC
Created attachment 31403 [details]
registers before suspend with combios-v3 patch. 2nd try.
Comment 38 eruditehermit 2009-11-23 04:03:03 UTC
Created attachment 31410 [details]
kms Xorg.0.conf before suspending.
Comment 39 eruditehermit 2009-11-23 04:06:49 UTC
Created attachment 31411 [details]
kms Xorg.0.conf after resuming.

What I did to get these 2 kms Xorg.0.conf logs:

1) Boot into kms
2) copy Xorg.0.conf to Xorg.0.conf.beforesuspend
3) switch to VT and as root service gdm stop
4) echo 0 > /sys/class/vtconsole/vtcon1/bind
5) modprobe -r radeon
6) echo -n mem > /sys/power/state
7) resume
8) vbetool post
9) modprobe radeon modeset=1 agpmode=-1
10) servide gdm start
11) copy Xorg.0.conf to Xorg.0.conf.afterresume
Comment 40 eruditehermit 2009-11-23 17:45:44 UTC
Created attachment 31430 [details]
Here are the registers before suspend.

These are the working registers. This was taken after the discussion on IRC with tormod and airlied about the radeon kms module problems with DDX.
Comment 41 eruditehermit 2009-11-23 17:47:29 UTC
Created attachment 31431 [details]
Broken registers after resume.

These are the registers after resume. The LVDS backlight is still not on. This was taken after the discussion with airlied and tormod about kms and DDX race condition. The workaround was to put radeon in /etc/modules to ensure it loaded before the DDX or X loaded.
Comment 42 Christian Hartmann 2009-11-24 06:12:10 UTC
Created attachment 31439 [details]
dmesg after a resume

last nightly build from git with combios_readback_v3 + applied patch from Jerome Glisse ( 
commit 28590df27d40ff101dc1533654a3ea972f7d3679
Author: christian hartmann <cornogle@googlemail.com>
Date:   Tue Nov 24 10:12:13 2009 +0100

    applying the Add_range_validation_function_v2.patch from Jerome Glisse

    Signed-off-by: christian hartmann <cornogle@googlemail.com>

commit 587d36f3209ed046f55e6ad5dfc9747012664ba2
Author: christian hartmann <cornogle@googlemail.com>
Date:   Tue Nov 24 10:11:01 2009 +0100

    applying the patch combios_readback.patch.V3 from airlied

    Signed-off-by: christian hartmann <cornogle@googlemail.com>

commit a8a8a669ea13d792296737505adc43ccacf3a648
Merge: 931ed94 a7d73d8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Nov 19 20:29:34 2009 -0800

    Merge branch 'i2c-pnx-fixes' of git://git.fluff.org/bjdooks/linux

The screen is not black, but I have problems to login in x with compiz, see last lines, but I do not know if there is already another bug entry for these error message
Comment 43 Christian Hartmann 2009-11-24 06:12:47 UTC
Created attachment 31440 [details]
working.regs before suspend
Comment 44 Christian Hartmann 2009-11-24 06:13:09 UTC
Created attachment 31441 [details]
broken.regs after resume
Comment 45 Christian Hartmann 2009-11-24 08:51:09 UTC
Update of 2.6.32-rc8:

a) s2disk and s2ram works perfectly for me now after pulling 
drm-2.6 drm-linus 

commit 1d33047c9f0ad5a5e3cacf496557aa1672d95d41
Merge: 28590df 5349ef3
Author: christian hartmann <cornogle@googlemail.com>
Date:   Tue Nov 24 15:13:51 2009 +0100

    Merge branch 'drm-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 into rc8_drm_readback

b) therefore some icons (the gnome-panel icons) are now screwed up now.

c) echo mem > /sys/power/state will suspend and resume, but the screen looks very strange, I can see for a few miliseconds a message  "codec_read 0: read timeout for register 0x2", the screen looks like it will burn / flame, it look cool too :) Xorg is running opkay, after the resume from mem.

d) I tried also vbetool post in the console, but this is horrible, cause black screen as it is described above from  eruditehermit. Switching to X looks show me a very big mouse pointer, but I can not see anything else. I was able to blindly type "rcgdm stopt" or to login blindly via gdm and perform a rcgdm stop. 
When I switch back from Xorg here, the console is not resetted as it should be. It is lighted up, but I see the whole screen is flashing with random chars in darkgrey like a cursor does in the console. Restarting gdm/xorg gives me the same error as before the latest git pull:
[ 2320.550802] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11).
[ 2320.559919] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[ 2321.352296] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11).
[ 2321.361484] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

So vbetool does not work for me too, yet. (But s2disk does his job now, great.)

e) whenever I have the boot option "splash" enabled, i cannot enter anymore the uswsup-key to encrypt my suspended image. have  to reboot and set the nosplash option. sysrequest gives me only help message, but no task, no regs, no mem. only sysrq + O (poweroff) works at this state. this is all the time I have KMS enabled. using so far no splash until it it would be fixed.

Comment 46 Christian Hartmann 2009-11-24 09:04:11 UTC
(In reply to comment #45)
> Update of 2.6.32-rc8:

> d) I tried also vbetool post in the console, but this is horrible, cause black
> screen as it is described above from  eruditehermit. Switching to X looks show
> me a very big mouse pointer, but I can not see anything else. I was able to
> blindly type "rcgdm stopt" or to login blindly via gdm and perform a rcgdm
> stop. 
> When I switch back from Xorg here, the console is not resetted as it should be.
> It is lighted up, but I see the whole screen is flashing with random chars in
> darkgrey like a cursor does in the console. Restarting gdm/xorg gives me the
> same error as before the latest git pull:
> [ 2320.550802] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule
> IB(11).
> [ 2320.559919] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
> [ 2321.352296] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule
> IB(11).
> [ 2321.361484] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
> 
> So vbetool does not work for me too, yet. (But s2disk does his job now, great.)

The only solution for me of this mess up is to 
%echo -n mem > /sys/power/state 
again, and resume again -> console is back as it should be. 
Xorg is usless until reboot cause of the IB schedule errors ( since the vbetool post)
Comment 47 Christian Hartmann 2009-11-24 09:05:56 UTC
Comment on attachment 31441 [details]
broken.regs after resume

was before pulling drm-linus
Comment 48 Christian Hartmann 2009-11-24 09:08:02 UTC
Comment on attachment 31440 [details]
working.regs before suspend

was before pulling drm-linus
Comment 49 Christian Hartmann 2009-11-24 09:08:24 UTC
Comment on attachment 31439 [details]
dmesg after a resume

was before pulling drm-linus
Comment 50 Christian Hartmann 2009-11-24 09:20:34 UTC
Created attachment 31447 [details]
echo -n mem > sys/power/state

c) message  "codec_read 0: read
timeout for register 0x2", the screen looks like it will burn / flame, it look
cool too :) Xorg is running opkay, after the resume from mem.
Comment 51 Christian Hartmann 2009-11-24 09:43:30 UTC
Created attachment 31449 [details]
b) therefore some icons (the gnome-panel icons) are now screwed up now.
Comment 52 eruditehermit 2010-03-10 01:18:28 UTC
Created attachment 33917 [details]
dmesg upon resume 2.6.33 drm linus branch of airlied tree

Here is the dmesg when s/r on 2.6.33 drm-linus branch of tree at  git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus on 20100310.
Comment 53 eruditehermit 2010-03-10 22:45:58 UTC
Created attachment 33935 [details]
radeontool register dump before suspend (working state) 20100310 with VGA plugged in.

radeontool register dump before suspend (working state) 20100310 with VGA plugged in.
Comment 54 eruditehermit 2010-03-10 22:47:04 UTC
Created attachment 33936 [details]
radeontool register dump after resume (broken state) 20100310 with VGA plugged in.

radeontool register dump after resume (broken state) 20100310 with VGA plugged in.
Comment 55 eruditehermit 2010-03-10 22:47:45 UTC
Created attachment 33937 [details]
lspci output before suspend (working state) with VGA plugged in.

lspci output before suspend (working state) with VGA plugged in.
Comment 56 eruditehermit 2010-03-10 22:48:13 UTC
Created attachment 33938 [details]
lspci output after resume (broken state) with VGA plugged in.

lspci output after resume (broken state) with VGA plugged in.
Comment 57 eruditehermit 2010-03-10 23:40:40 UTC
Created attachment 33940 [details]
register dumps and mmapr command output

The radeontool register dumps were performed using the following script I created.

#!/bin/bash
for x in 0x220 0x224 0x228 0x320 0x324 0x328 0x32c 0x23c 0x33c
do
 ./radeontool regmatch $x > 20100310_regmatch_$x\_LVDS_VGA_broken.reg
done
cd /sys/bus/pci/devices/0000:01:00.0
mmapr resource0 0 256 | xxd > /home/user/20100310_mmapr_LVDS_VGA_broken
cd /home/user

repeated for working state as well

Also included are the lspci and reg dumps from the previous posts on 20100310 for convenience.
Comment 58 eruditehermit 2010-03-11 01:26:44 UTC
Created attachment 33945 [details]
Register dumps and radeon_vram_mm radeon_pm_info

output from registers 0xe0, 0x130, 0xb00, 0xb0c, 0x148, 0x108

cat /sys/kernel/debug/dri/0/radeon_pm_info
cat /sys/kernel/debug/dri/0/radeon_vram_mm

when mount -t debugfs none /sys/kernel/debug

This was performed with X running. Kernel is 2.6.33 drm-linus branch of airlied tree.
Comment 59 eruditehermit 2010-03-11 01:40:20 UTC
Created attachment 33946 [details]
Register dumps and radeon_vram_mm radeon_pm_info using VT ONLY (NO X SERVER)

output from registers 0xe0, 0x130, 0xb00, 0xb0c, 0x148, 0x108

cat /sys/kernel/debug/dri/0/radeon_pm_info
cat /sys/kernel/debug/dri/0/radeon_vram_mm

when mount -t debugfs none /sys/kernel/debug

This was performed WITHOUT X running. Kernel is 2.6.33 drm-linus branch of airlied
tree.
Comment 60 eruditehermit 2010-03-22 20:56:44 UTC
Created attachment 34340 [details]
all registers with agpmode=-1 VGA and LVDS plugged in after resume.
Comment 61 eruditehermit 2010-03-22 20:57:05 UTC
Created attachment 34341 [details]
all registers with agpmode=-1 VGA and LVDS plugged in before suspend.
Comment 62 eruditehermit 2010-03-22 21:03:37 UTC
Created attachment 34342 [details]
all registers with agpmode=-1 VGA and LVDS plugged in after resume.
Comment 63 eruditehermit 2010-03-22 21:04:11 UTC
Created attachment 34343 [details]
all registers with agpmode=-1 VGA and LVDS plugged in before suspend.
Comment 64 eruditehermit 2010-03-22 21:37:45 UTC
Created attachment 34344 [details]
all registers with colortiling off agpmode=-1 VGA and LVDS plugged in after resume.
Comment 65 eruditehermit 2010-03-22 21:38:14 UTC
Created attachment 34345 [details]
all registers with agpmode=-1 colortiling off, VGA and LVDS plugged in before suspend.
Comment 66 eruditehermit 2010-03-22 22:20:31 UTC
Created attachment 34346 [details]
all registers with agpmode=-1 colortiling off VGA and LVDS plugged in before suspend new registers + switched to VT with X running.
Comment 67 eruditehermit 2010-03-22 22:21:00 UTC
Created attachment 34347 [details]
all registers with agpmode=-1 colortiling off VGA and LVDS plugged in after resume new registers + switched to VT with X running.
Comment 68 Dave Airlie 2010-03-22 22:44:16 UTC
git clone git://people.freedesktop.org/~stuart/vbtracetool
cd vbtracetool; make

kill X, suspend, resume, 
echo 0 > /sys/class/vtconsole/vtcon1/bind
rmmod radeon

vbtracetool -p -l 2> mytracelog

gzip mytracelog

stick it here.
Comment 69 eruditehermit 2010-03-22 23:06:15 UTC
Created attachment 34349 [details]
log from vbtracetool obtained using airlied's instructions posted above
Comment 70 eruditehermit 2010-03-23 00:08:44 UTC
Created attachment 34350 [details]
unloading radeon before suspend, resuming and if no text mode comes up, running vbtracetool, then loading radeon
Comment 71 Dave Airlie 2010-03-23 17:16:24 UTC
http://people.freedesktop.org/~airlied/scratch/bios_post_test.patch

can you try with the attached patch.

if that doesn't help, can you suspend/resume, unload radeon

radeontool regset CONFIG_CNTL 0x0xc0100 

then vbetool post

and see if text mode comes back.
Comment 72 Keith Moyer 2012-04-27 18:38:35 UTC
What is the status on this issue?  It looks like there was some pretty furious activity for a while then a sudden stop.

Is there anything I can do to help track it down?  I've had this issue for a couple of years, but have just lived with it (same hardware).
Comment 73 Alex Deucher 2012-05-04 05:48:46 UTC
*** Bug 24097 has been marked as a duplicate of this bug. ***
Comment 74 Martin Peres 2019-11-19 08:07:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/54.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.