please see also bug #19215, may be related
After some days the xorg server is up and running the cursor get corrupted.
This is a kde4 desktop on a dual 1920x1080 screen powered by an ATI Radeon HD 4670.
The bug happens often, having played a game like Aquaria (in windowed mode) help a lot, but it does not guarantees an immediate trigger.
This time xorg was up and running for about four days (not totally sure), yesterday I've played with the already mentioned Aquaria.
please feel free to request further information
since I don't know where to start I've tried to be broad on covering the system information, here is what the attached zip file contain:
cursor as it should be (after a reboot)
cursor as it's shown in the left monitor VGA-0
cursor as it's shown in the right monitor DVI-0
log for the server on vt7 whit kde running
tentative to start another X server on vt8, it also had a broken cursor
"SWcursor" is commented out
`radeontool debug regs` output
radeon and x11 related software installed on this pc
`modinfo radeon` output
`xrandr -q --verbose` output
`lspci -vvv` output
`lshw` output, it's an hardware lister
Created attachment 36105 [details]
various log and information on the system
Created attachment 36106 [details]
Created attachment 36107 [details]
Created attachment 36108 [details]
got absolutely the same problems with HD 4870.
Attachment 36107 [details] (DVI-0-cursor-broken.jpeg) looks like what I am seeing.
Radeon HD 4650
Radeon driver 6.14.2
I have not found a way to trigger it, it just happens after a few hours working on a desktop.
1) the cursor corruption seems to occur when the cursor crosses the boundary between the two displays of a dual-head setup
2) restarting X does not get back the regular cursor; it stays corrupted until the machine is rebooted
3) I did _not_ see this problem with a Radeon X300SE on an almost identical software setup
I have the same issue with a Radeon HD 4770 and two 1920x1200 monitors connected via DVI. I'm currently running Linux 3.0.6 and xf86-video-ati 6.14.2, but I've been seeing this for a long time.
Kernel 3.0.7 has one HW cursor fix, 3.1 has more and other HW cursor changes. Do any of those help?
sorry, I've switched to nvidia, cannot test
I've now updated to Linux 3.1. It's looking fine so far but it usually takes a couple days or so until the cursor corruption starts. I will report back.
My Linux 3.1 system has been running for over 6 days now without issues. Seems like it may finally be fixed for good :) Thanks!
Like Jürg Billeter, I haven't seen the problem since switching to Linux 3.1.
I don't currently use the affected system as much as I usually do, so it may be too early to celebrate, but I guess the bug could be closed as resolved and reopened later if need be.
(In reply to comment #12)
> Like Jürg Billeter, I haven't seen the problem since switching to Linux 3.1.
So far, so good. Thanks for the updates, guys.
> I don't currently use the affected system as much as I usually do, so it may be
> too early to celebrate, but I guess the bug could be closed as resolved and
> reopened later if need be.
Sounds like a plan. :)
I'm having the exact same problem and I'm using kernel 3.2 with a Radeon HD 4350 on Debian sid. I had it with 3.0 an 3.1 too. Right now I have a vertical line on my left screen and the rainbow square on my right screen. It happens randomly and usualy goes away after a while. If it doesn't I have to reboot.
(In reply to comment #14)
> I'm having the exact same problem and I'm using kernel 3.2 with a Radeon HD
> 4350 on Debian sid. I had it with 3.0 an 3.1 too. Right now I have a vertical
> line on my left screen and the rainbow square on my right screen. It happens
> randomly and usualy goes away after a while. If it doesn't I have to reboot.
Is this a dual-head system, too, or do you have just one display?
For what it is worth, I have not experienced the problem since my earlier report that Linux 3.1 seems to fix it.
So the bug appears to be better hidden now, which tends to make fixing harder.
Maybe some driver developer can suggest a way out?
(In reply to comment #14)
> It happens randomly and usualy goes away after a while.
Given that this bug really seems fixed for others, and comment #7 says only a reboot helped, your problem sounds more similar to bug 33183 than this one.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/131.