From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28426] New: hardware cursor corruption with radeon+kms
Date: Mon, 7 Jun 2010 09:16:41 -0700 (PDT) [thread overview]
Message-ID: <bug-28426-502@http.bugs.freedesktop.org/> (raw)
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@lists.freedesktop.org
ReportedBy: maillist@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.
next reply other threads:[~2010-06-07 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 16:16 bugzilla-daemon [this message]
2010-06-07 16:20 ` [Bug 28426] hardware cursor corruption with radeon+kms bugzilla-daemon
2010-06-07 16:20 ` bugzilla-daemon
2010-06-07 16:21 ` bugzilla-daemon
2010-06-07 16:21 ` bugzilla-daemon
2010-08-09 17:52 ` bugzilla-daemon
2011-08-17 10:06 ` bugzilla-daemon
2011-11-02 7:50 ` bugzilla-daemon
2011-11-02 10:53 ` bugzilla-daemon
2011-11-02 19:39 ` bugzilla-daemon
2011-11-03 7:25 ` bugzilla-daemon
2011-11-09 16:51 ` bugzilla-daemon
2011-11-10 8:24 ` bugzilla-daemon
2011-11-10 17:46 ` bugzilla-daemon
2012-01-26 13:39 ` bugzilla-daemon
2012-01-26 14:21 ` bugzilla-daemon
2012-01-30 15:41 ` bugzilla-daemon
2019-11-19 8:13 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28426-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.