01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 3100 Graphics (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 82ee
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at d000 [size=256]
Memory at fbef0000 (32-bit, non-prefetchable) [size=64K]
Memory at fbd00000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled]
Capabilities:  Power Management version 3
Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable-
Kernel driver in use: radeon
Kernel modules: radeon
01:05.0 0300: 1002:9611 (prog-if 00 [VGA controller])
When using everything (libdrm, mesa, xserver, xf86-video-ati) from git trees (master branch everywhere) - i got very visible screen corruption.
Reverting 955b9f23a34cc79a5cd9676b45b3df4ffcc7302b for xserver git tree ("EXA: ModifyPixmapHeader_mixed fixes") fixes problems for me.
Created attachment 31876 [details]
gkrellm with corruption
Created attachment 31877 [details]
Messy, as usual.
Created attachment 31878 [details]
old X log
Created attachment 31879 [details]
current X log
I can confirm the corruption on r300/M26/X700/1002:5653.
For kernel side i have 2.6.32-rc8-i486 , actually kernel for drm-radeon-next Because this tree rebased often, i can only tell what i have currently kernel with r7xx irq support, and of course i have firmware in /lib , as posted on dri-devel ML. kernel tree from around 1 dec 2009 -
4c7886791264f03428d5424befb1b96f08fc90f4 (drm/radeon/kms: Rework radeon object handling) and pervious commit was 1614f8b17b8cc3ad143541d41569623d30dbc9ec (drm/radeon/kms: add irq mitigation code for sw interrupt.) and even before that d8f60cfc93452d0554f6a701aa8e3236cbee4636 (drm/radeon/kms: Add support for interrupts on r6xx/r7xx chips (v3))
Created attachment 31880 [details] [review]
This xserver patch should fix it.
(In reply to comment #7)
> Created an attachment (id=31880) [details]
> Probable fix
> This xserver patch should fix it.
Yes, image back to normal with patch. Thanks a lot!
I can confirm the patch fixed the issue. Thanks!
Fix landed on master, thanks for testing.
*** Bug 25575 has been marked as a duplicate of this bug. ***