All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: alexander.deucher@amd.com
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	christian.koenig@amd.com, David Airlie <airlied@linux.ie>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Regression][v3.17][3.18][3.19-rc3] drm/radeon: re-enable dpm by default on BTC
Date: Wed, 07 Jan 2015 17:51:23 -0500	[thread overview]
Message-ID: <54ADB86B.10105@canonical.com> (raw)

Hi Alexander,

A kernel bug report was opened against Ubuntu [0].  After a kernel
bisect, it was found that reverting the following commit resolved this bug:

commit c08abf11900e19b14dd3a0cc3d105bd74519cd18
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Mon Jul 14 12:01:40 2014 -0400

    drm/radeon: re-enable dpm by default on BTC

The regression was introduced as of v3.17-rc1 and still exists in
current mainline.  It has also made it's way into the stable releases.

I was hoping to get your feedback, since you are the patch author.  Do
you think gathering any additional data will help diagnose this issue,
or would it be best to submit a revert request?
    
    
Thanks,

Joe

[0] http://pad.lv/1386534

             reply	other threads:[~2015-01-07 22:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 22:51 Joseph Salisbury [this message]
2015-01-08  2:51 ` [Regression][v3.17][3.18][3.19-rc3] drm/radeon: re-enable dpm by default on BTC Deucher, Alexander
2015-01-08  2:51   ` Deucher, Alexander
2015-01-08 16:12   ` Joseph Salisbury
2015-01-08 16:25   ` Joseph Salisbury
2015-01-08 17:48     ` Deucher, Alexander
2015-01-08 18:00       ` Joseph Salisbury
2015-01-08 21:58       ` Joseph Salisbury
2015-01-08 22:00         ` Deucher, Alexander
2015-01-08 22:00           ` Deucher, Alexander
2015-01-08 22:00           ` Deucher, Alexander
2015-01-08 22:11           ` Joseph Salisbury

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=54ADB86B.10105@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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.