The display is completely garbage after returning from suspend to both ram and disk. The result is the same after suspend from both console and disk.

dmesg after suspend is full of on-and-on repeating lines of:

[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

These are spewed out continuously.

It must be noted that GNU/Linux is still running after suspend. It is possible to write shutdown -r now and press enter to get the box to reboot.

Possibly useful information:

- kernel 2.6.32-rc6-git6 with KMS (CONFIG_DRM_RADEON_KMS=y)
- libdrm, xf86-video-ati and mesa git as of Nov 14 2009

display device:
1:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 Graphics (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. Device 7576
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        I/O ports at 9000 [size=256]
        Memory at fe8f0000 (32-bit, non-prefetchable) [size=64K]
        Memory at fe700000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable-
        Kernel driver in use: radeon

two monitors (HDMI+VGA)

Possibly related bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=23479 (radeon Mobility X1400 with KMS)
https://bugs.freedesktop.org/show_bug.cgi?id=23273 (KMS suspend fails to resume with radeon mobility x2300)

These bugs mention different chips, but the bug may be exactly the same.

Please let me know if I can somehow provide more helpful incriminating evidence of this bug.