Bug 42708 - drm:radeon_cs_ioctl "Failed to schedule IB" error after s2ram and wakeup
Summary: drm:radeon_cs_ioctl "Failed to schedule IB" error after s2ram and wakeup
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 20:58 UTC by Konstantin Nikiforov
Modified: 2012-08-30 14:43 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.2.1-1-ARCH
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Konstantin Nikiforov 2012-01-31 20:58:52 UTC 
Distrib: Archlinux current.
Issue is 100% reproduceable on 3.2.1, but NOT reproduceable on <3.2 (any older kernels).

Steps to reproduce:
0. Notebook Toshiba Sattelite A210 (see lspci[1])
1. Power up, boot to X
2. s2ram
3. wake it up using power button

Expected result: xorg can work
Result: xorg freezed, picture looks corrupted, but mouse pointer works.
In console (ctrl+alt+f1) infinite messages:

Feb  1 00:33:04 host kernel: [11060.390851] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0).
Feb  1 00:33:04 host kernel: [11060.394089] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
Feb  1 00:33:05 host kernel: [11061.391806] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
Feb  1 00:33:05 host kernel: [11061.395257] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
Feb  1 00:33:06 host kernel: [11062.394362] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2).
Feb  1 00:33:06 host kernel: [11062.397986] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
t up using power button
...

`/etc/rc.d/lxdm restart` does not help. Only reboot.

[1] - lspci -v: http://pastebin.ca/2108254
[2] - radeon.ko loaded with dynclks=1 modeset=1
Comment 1 Konstantin Nikiforov 2012-08-30 14:43:05 UTC 
Not reproduceable anymore on kernels 3.4 - 3.5. Closed.
Note You need to log in before you can comment on or make changes to this bug.