Bug 11888
| Summary: | [RADEON:UMS] the screen remains black after resume | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Matthias-Christian Ott (ott) |
| Component: | Video(Other) | Assignee: | drivers_video-dri |
| Status: | CLOSED UNREPRODUCIBLE | ||
| Severity: | normal | CC: | glisse, rjw, yakui.zhao |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.26, 2.6.28-rc2-git3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216 | ||
| Attachments: | dmesg output | ||
|
Description
Matthias-Christian Ott
2008-10-29 07:49:00 UTC
Created attachment 18495 [details]
dmesg output
See also: * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503870 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/67710 * https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/134476 * http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=447338&prodTypeId=321957&prodSeriesId=447338&objectID=c01209446 (seems related) I will try the latest git version as soon as possible I tested suspending with linux 2.6.28-rc2-git3 and got the same results except that I was not able to use the keyboard, so I couldn't capture dmesg's output. Can you please try s2ram (http://en.opensuse.org/s2ram)? The problem still occurs.
# s2ram -i
This machine can be identified by:
sys_vendor = "Hewlett-Packard"
sys_product = "HP Compaq nc8230 (PV406AW#ABD)"
sys_version = "F.16"
bios_version = "68DTV Ver. F.16"
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
See also: http://bugzilla.kernel.org/show_bug.cgi?id=7857
What combinations of s2ram options did you try? All in the wiki I think (first I hadn't vbetool installed, but did the relevant tests with vbetool installed again). I should add that I used 2.6.28-rc2-git3 to ensure that the issue was not already fixed. I tried to compile suspend-cvs, but it failed because Debian doesn't ship libgcc_s.a. Anyhow it tried to run the test-s2ram script with suspend-0.8, but it stopped after the first test. Can you give my a hint what to do/which options to try/which information you need? I got it working with s2ram -f -s, it just took a long time to resume, maybe I was not patient enough during my first test. The following combinations worked: s2ram -v -f -p -s s2ram -v -f -s s2ram -f -s s2ram -f -p -s But sometimes the system doesn't resume for some random reason and the light gets turned on maximally. Anyhow is it normal that the s2ram can take a minute or so? *** This bug has been marked as a duplicate of bug 7857 *** Today I found the time to test it again: # s2ram -f -p -s Switching from vt7 to vt1 Calling save_state Allocated buffer at 0x2010 (base is 0x0) ES: 0x0201 EBX: 0x0000 fbcon fb0 state 1 Calling do_post Error: something went wrong performing real mode call Calling restore_state_from Function not supported? fbcon fb0 state 0 switching back to vt7 Maybe this is the reason for the performance issues. I will reopen the bug until this is resolved. (In reply to comment #11) > Today I found the time to test it again: > > # s2ram -f -p -s > Switching from vt7 to vt1 > Calling save_state > Allocated buffer at 0x2010 (base is 0x0) > ES: 0x0201 EBX: 0x0000 > fbcon fb0 state 1 > Calling do_post > Error: something went wrong performing real mode call > Calling restore_state_from > Function not supported? This means the '-s' option of s2ram doesn't work on your system. You can drop it. If I drop it, the screen is still blank (I think the light works). Can you check if resume works with the ATI binary driver, please? I tried the proprietary ATI driver, but on X.org startup the screen remained blank (I did apt-get install fglrx-driver and changed my xorg.conf). Seems that (as usual) proprietary software doesn't work. Shall I try it with radeonfb or plain vga? Maybe you can explain to me what conjecture you have. I'm a confident C programmer maybe I can help. I will provide you every debugging information you need. If you need remote serial access to the device just give me a shout. Meanwhile I tried plain s2ram which worked (because of a correct entry for my laptop in whitelist.c [-p -s]). Nearly a month has passed and still no status update. Is there still a change to get this working? Not really at the moment. What did you mean by "I tried plain s2ram which worked" ? I meant that the specified options (see entry in whitelist.c) work (-p -s). Anyhow it's terribly slow (in comparison to s2disk) and I get the error message that I posted above (dropping -s doesn't work as mentioned). From the dmesg in comment #1 it seems that the system can be resumed from the S3 sleeping state. But the issue is that the screen remains black. This issue is related with the ATI graphics driver. Hi, ATI guys Do you have the opportunity to look at this issue? Hi, Rui
How about move this bug to other category?
Thanks.
Matthias-Christian, can you test 2.6.37, preferably with the KMS driver, and see if the issue is still there? We only support KMS now, so please test with lastest kernel with KMS enabled and report back, if you are using fglrx than it's not our bug and there is nothing we can do I don't have the laptop anymore. It broke over a year ago. Ok closing this bug |