[Bug 28426] New: hardware cursor corruption with radeon+kms
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jun 7 09:16:41 PDT 2010
https://bugs.freedesktop.org/show_bug.cgi?id=28426
Summary: hardware cursor corruption with radeon+kms
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel at lists.freedesktop.org
ReportedBy: maillist at pnpitalia.it
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-gimp.jpeg"
cursor as it should be (after a reboot)
- "VGA-0-cursor-broken.jpeg"
cursor as it's shown in the left monitor VGA-0
- "DVI-0-cursor-broken.jpeg"
cursor as it's shown in the right monitor DVI-0
- "Xorg.0.log"
log for the server on vt7 whit kde running
- "Xorg.1.log"
tentative to start another X server on vt8, it also had a broken cursor
- "xorg.conf"
"SWcursor" is commented out
- "radeontool--debug-regs.log"
`radeontool debug regs` output
- "installed-software.log"
radeon and x11 related software installed on this pc
- "modinfo-radeon.log"
`modinfo radeon` output
- "lsmod.log"
`lsmod` output
- "xrandr--verbose.log"
`xrandr -q --verbose` output
- "lspci-vvv.log"
`lspci -vvv` output
- "lshw.log"
`lshw` output, it's an hardware lister
- "dmesg.log"
`dmesg` output
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the dri-devel
mailing list