[Bug 44916] New: Suspend to RAM causes a blank screen with a mouse cursor on Mobility Radeon HD 2400 XT with radeon driver.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 18 16:58:13 PST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=44916

             Bug #: 44916
           Summary: Suspend to RAM causes a blank screen with a mouse
                    cursor on Mobility Radeon HD 2400 XT with radeon
                    driver.
    Classification: Unclassified
           Product: xorg
           Version: 7.7 (2011)
          Platform: x86-64 (AMD64)
               URL: http://forums.opensuse.org/english/get-technical-help-
                    here/laptop/471255-cannot-resume-after-suspend-acer-55
                    20g-mobility-radeon-hd-2400-xt.html
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: alfla at rambler.ru
         QAContact: xorg-team at lists.x.org


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).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list