From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: Regression: Backlight not coming on after resume. Date: Thu, 28 Feb 2013 17:33:56 +0200 Message-ID: <87lia8mp0b.fsf@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTP id 18E12E5C89 for ; Thu, 28 Feb 2013 07:33:30 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: James Courtier-Dutton , Intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Thu, 28 Feb 2013, James Courtier-Dutton wrote: > Bisect done on tree: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git > Worked on 3.7. > Broken on 3.8 > > Problem: "Backlight not coming on after resume." > git finally bisected for my Samsung Serial 7 Laptop. > Bisecting: 0 revisions left to test after this (roughly 0 steps) > [cf0a6584aa6d382f802f2c3cacac23ccbccde0cd] drm/i915: write backlight > harder <- This is the problem commit. Seems that fixing some > machines breaks others, based on the existing comments on that patch. The backlight haunts us again. Could you post the dmesg with drm.debug=0xe module parameter, first running vanilla 3.8, and then with the bad commit reverted, please? Might not be a bad idea to file a bug on Product=DRI, Component=DRM/Intel at https://bugs.freedesktop.org (see https://01.org/linuxgraphics/documentation/how-report-bugs-0 for details) and attach your bisect results and the dmesgs there. Thanks, Jani.