dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 27 Aug 2013 23:54:58 +0000	[thread overview]
Message-ID: <bug-60791-2300-0VxaxmZJhx@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 #12 from Brian Hall <hallbw@gmail.com> ---
Bisect results below. According to my Xorg.0.log, my board is a 
"ATI Radeon HD 4200" (ChipID = 0x9710) and lspci calls it a RS880.

6f8bbaf568c7f2c497558bfd04654c0b9841ad57 is the first bad commit
commit 6f8bbaf568c7f2c497558bfd04654c0b9841ad57
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Tue Jul 30 00:22:53 2013 -0400

    drm/radeon/atom: initialize more atom interpretor elements to 0

    commit 42a21826dc54583cdb79cc8477732e911ac9c376 upstream.

    The ProcessAuxChannel table on some rv635 boards assumes
    the divmul members are initialized to 0 otherwise we get
    an invalid fb offset since it has a bad mask set when
    setting the fb base.  While here initialize all the
    atom interpretor elements to 0.

    Fixes:
    https://bugzilla.kernel.org/show_bug.cgi?id=60639

    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

:040000 040000 d2bb057047f71419a89def40e6e21dc948c5784c
7e49987ae73078e644723f0cb6c791e15e102ab0 M    drivers

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-08-27 23:55 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 [this message]
2013-08-28 13:04 ` bugzilla-daemon
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-0VxaxmZJhx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox