Bug#597664: linux-image-2.6.32-5-686: Xorg crashes with radeon kernel messages
(resending to new address)
Hi,
Sorry for the long silence.
The Anarcat wrote:
> Today I had a very special issue with my workstation. The display would
> start but freeze. Even though in the back things are still happening,
> the display isn't updated and the only way out is to go to TTY1
> (control-alt-F1) where the console gets flooded with messages like this:
>
> Sep 21 17:59:04 lenny kernel: [ 102.324219] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0).
> Sep 21 17:59:04 lenny kernel: [ 102.354242] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
> Sep 21 17:59:04 lenny kernel: [ 103.124761] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
> Sep 21 17:59:04 lenny kernel: [ 103.155110] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
> [...]
>
> (The message loops through IB(0) to IB(15).)
[...]
> [3] http://bugs.debian.org/588688 suggests upgrading to 2.6.35~rc2. I
> tried 2.6.35-1~experimental.3 and it crashes.
Could you elaborate on that? Do you mean that 2.6.35 produces the
same symptoms or did something else?
> [7] https://bugzilla.kernel.org/show_bug.cgi?id=15969 is the upstream,
> closed kernel bug
That bug points to v2.6.34-rc7~6^2~11 (drm/radeon/kms: r300 fix CS
checker to allow zbuffer-only fastfill, 2010-04-13) as cause and
v2.6.35-rc1~18^2~6 (drm/radeon/kms: release AGP bridge at suspend,
2010-05-21) as a fix, so I suspect it's a different bug.
Because it's been so long, I also should ask:
- can you still reproduce this with recent sid and squeeze kernels?
- any ideas, weird symptoms, or workarounds discovered since then?
How have you been coping in the meantime?
Thanks and hope that helps,
Jonathan
Reply to: