Bug 44916 - Suspend to RAM causes a blank screen with a mouse cursor on Mobility Radeon HD 2400 XT with radeon driver.
Summary: Suspend to RAM causes a blank screen with a mouse cursor on Mobility Radeon H...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL: http://forums.opensuse.org/english/ge...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 16:58 UTC by alfla
Modified: 2018-06-12 19:06 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
The dmesg output (77.25 KB, text/plain)
2012-01-19 04:42 UTC, alfla 		no flags Details
/var/log/Xorg.0.log (50.05 KB, text/plain)
2012-01-19 04:43 UTC, alfla 		no flags Details
View All

Description alfla 2012-01-18 16:58:13 UTC 
Steps to reproduce:

1. Suspend to RAM.
2. Resume.

Result:

A blank screen with a mouse cursor. The laptop responds to keyboard and mouse.

Expected result:

Fully resumed state of the laptop before suspend.

Detailed description:

My laptop is Acer 5520G (2008) with Mobility Radeon HD 2400 XT.

The problem is related to radeon driver. In all GNU/Linux distributions I used (openSUSE 11.4 as well as openSUSE 12.1, Fedora 16) I experience the problem with suspend/resume (s2ram). Laptop suspends, but when I try to resume it, I see only a blank screen with a mouse cursor. This is true for KDE, Gnome, and "init 1" stage. I checked in openSUSE 11.4, 12.1, and Fedora 16. In openSUSE 11.2 clicking the suspend option locked the screen and the laptop did not suspend. My experiments show that it is related to problems with KMS and radeon driver. In tty1 I see scrolling messages

[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0)
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1)
...
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15).

In openSUSE 11.4 there were error messages too. This led to artefacts in KDE after reboot: horizontal lines on plasma panels, menus, etc. Ctrl+Alt+Backspace and reboot helped me to remove those artefacts almost every time. Even in init 1 when I use s2ram and try resuming the result is the same:
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0)... (openSUSE 12.1).
I tried to install kernel 3.1.8. The bug is not fixed there. In /var/log/Xorg.0.log there are errors:
[ 54.726] (EE) Failed to load module "fglrx" (module does not exist, 0)
[ 54.778] (EE) FATAL: RadeonHD presently does not work with kernel modesetting (KMS).
Comment 1 Michel Dänzer 2012-01-19 01:26:09 UTC 
Please attach /var/log/Xorg.0.log and the dmesg output.
Comment 2 alfla 2012-01-19 04:42:14 UTC 
Created attachment 55774 [details]
The dmesg output
Comment 3 alfla 2012-01-19 04:43:36 UTC 
Created attachment 55775 [details]
/var/log/Xorg.0.log
Comment 4 Adam Jackson 2018-06-12 19:06:52 UTC 
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.