From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60791] Display corruption with Radeon driver during boot and on desktop
Date: Wed, 28 Aug 2013 13:04:25 +0000 [thread overview]
Message-ID: <bug-60791-2300-i4qqYxOprz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60791-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60791
--- Comment #13 from Alex Deucher <alexdeucher@gmail.com> ---
Can you revert parts of the patch to find out which element is causing the
problem. E.g., try:
/* reset data block */
// ctx->data_block = 0;
and see if that helps, then:
/* reset divmul */
// ctx->divmul[0] = 0;
ctx->divmul[1] = 0;
etc.
Additionally, can you dump the display registers in the working and non-working
states using radeonreg (http://cgit.freedesktop.org/~airlied/radeontool/)?
(as root)
boot with broken kernel:
./radeonreg regs dce3 > broken.regs
boot with working kernel:
./radeonreg regs dce3 > working.regs
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-08-28 13:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 21:20 [Bug 60791] New: Display corruption with Radeon driver during boot and on desktop bugzilla-daemon
2013-08-25 21:20 ` [Bug 60791] " bugzilla-daemon
2013-08-25 21:22 ` bugzilla-daemon
2013-08-25 21:24 ` bugzilla-daemon
2013-08-25 21:24 ` bugzilla-daemon
2013-08-25 21:24 ` bugzilla-daemon
2013-08-25 21:24 ` bugzilla-daemon
2013-08-25 21:26 ` bugzilla-daemon
2013-08-25 21:27 ` bugzilla-daemon
2013-08-25 21:27 ` bugzilla-daemon
2013-08-25 21:46 ` bugzilla-daemon
2013-08-26 13:01 ` bugzilla-daemon
2013-08-27 0:48 ` bugzilla-daemon
2013-08-27 23:54 ` bugzilla-daemon
2013-08-28 13:04 ` bugzilla-daemon [this message]
2013-08-29 2:11 ` bugzilla-daemon
2013-08-29 2:15 ` bugzilla-daemon
2013-08-29 2:16 ` bugzilla-daemon
2013-08-29 2:16 ` bugzilla-daemon
2013-09-03 3:00 ` bugzilla-daemon
2013-09-08 17:22 ` bugzilla-daemon
2013-09-08 17:23 ` bugzilla-daemon
2013-09-08 21:42 ` bugzilla-daemon
2013-09-09 0:01 ` bugzilla-daemon
2013-09-09 4:29 ` bugzilla-daemon
2013-09-09 15:08 ` bugzilla-daemon
2013-09-09 19:16 ` bugzilla-daemon
2013-09-09 19:18 ` bugzilla-daemon
2013-09-09 19:36 ` bugzilla-daemon
2013-09-09 19:36 ` bugzilla-daemon
2013-09-09 19:40 ` bugzilla-daemon
2013-09-09 19:44 ` bugzilla-daemon
2013-09-10 1:16 ` bugzilla-daemon
2013-09-10 14:05 ` bugzilla-daemon
2013-09-10 18:08 ` bugzilla-daemon
2013-09-27 21:40 ` bugzilla-daemon
2013-09-27 21:50 ` bugzilla-daemon
2013-10-10 19:36 ` 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-60791-2300-i4qqYxOprz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.