[Regression, post-2.6.37-rc2] Unable to start KDE with 2.6.37-rc3 on Acer Ferrari One

[Rafael J. Wysocki]

On Wednesday, November 24, 2010, Rafael J. Wysocki wrote:
> Hi,
> 
> I cannot start KDE with the 2.6.37-rc3 kernel.  The X server and display
> manager start normally, but when I attempt to log into KDE, it attempts to
> start, but then the X apparently crashes and this appears in the dmesg output:
> 
> [   24.342287] radeon 0000:01:05.0: r600_cs_track_validate_cb offset[0] 0 46097920 4325376 too big
> [   24.342298] radeon 0000:01:05.0: r600_packet3_check:1331 invalid cmd stream 502
> [   24.342304] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
> [   24.694106] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> [   93.938946] radeon 0000:01:05.0: r600_cs_track_validate_cb offset[0] 0 46097920 4325376 too big
> [   93.938956] radeon 0000:01:05.0: r600_packet3_check:1331 invalid cmd stream 502
> [   93.938962] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
> [   94.278050] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> [  114.898043] radeon 0000:01:05.0: r600_cs_track_validate_cb offset[0] 0 46097920 4325376 too big
> [  114.898053] radeon 0000:01:05.0: r600_packet3_check:1331 invalid cmd stream 502
> [  114.898058] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
> [  115.266113] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> [  129.722472] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> [  142.984314] radeon 0000:01:05.0: r600_cs_track_validate_cb offset[0] 0 46097920 4325376 too big
> [  142.984324] radeon 0000:01:05.0: r600_packet3_check:1331 invalid cmd stream 502
> [  142.984330] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
> [  143.370083] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> 
> This doesn't happen with 2.6.37-rc2.

Reverting the following commit:

commit 16790569eddf4d406a16a65f4750f405fa669c52
Author: Alex Deucher <alexdeucher at gmail.com>
Date:   Sun Nov 14 20:24:35 2010 -0500

    drm/radeon/kms: fix and unify tiled buffer alignment checking for r6xx/7xx

fixes the issue for me (so everyone involved is already in the Cc list ;-)).

Thanks,
Rafael