All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	dri-devel@lists.freedesktop.org, indan@nul.nu
Subject: Re: Linux 2.6.37
Date: Tue, 11 Jan 2011 19:37:56 +0100	[thread overview]
Message-ID: <20110111183756.GA3782@tiehlicka.suse.cz> (raw)
In-Reply-To: <20110111173741.GA3988@tiehlicka.suse.cz>

On Tue 11-01-11 18:37:41, Michal Hocko wrote:
> On Tue 11-01-11 18:17:44, Michal Hocko wrote:
> > [Let's CC Indan - author of the bugzilla patches]
> > 
> > On Thu 06-01-11 11:48:16, Michal Hocko wrote:
> > > Hi,
> > > 
> > > On Tue 04-01-11 17:15:45, Linus Torvalds wrote:
> > > [...]
> > > > We did have another revert to fix hopefullythe last "blank screen"
> > > > regression on intel graphics.
> > > 
> > > It seems that there is still a regression for intel graphic cards
> > > backlight. One report is https://bugzilla.kernel.org/show_bug.cgi?id=22672.
> > > I can reproduce the problem easily by:
> > > xset dpms force standby; sleep 3s; xset dpms force on
> > > 
> > > backlight doesn't get up (there is really dark picture though which
> > > doesn't get brighter by function keys which work normally) after dpms on
> > > until I close and open lid. 
> > > 
> > > The problem wasn't present in 2.6.36
> > 
> > I can confirm that this problem is not present if both patches from
> > bko#22672 are applied on top of 2.6.37 kernel.
> > I haven't tried both patches separately, but I can surely try it if it
> > makes any sense.
> 
> I have just tried that and they are really both necessary.

I must have mixed something. After retesting with the first patch
(https://bugzilla.kernel.org/show_bug.cgi?id=22672#c33) the usecase
works just fine (backlight is on without need to close&open the lid)

Sorry for confusion

-- 
Michal Hocko
L3 team 
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

  reply	other threads:[~2011-01-11 18:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  1:15 Linux 2.6.37 Linus Torvalds
2011-01-06 10:48 ` Michal Hocko
2011-01-06 16:29   ` Linus Torvalds
2011-01-06 17:03     ` Michal Hocko
2011-01-06 17:03       ` Michal Hocko
2011-01-06 17:49     ` Chris Wilson
2011-01-06 20:55       ` Alex Riesen
2011-01-06 21:03         ` Chris Wilson
2011-01-06 21:03           ` Chris Wilson
2011-01-06 21:08         ` Alex Riesen
2011-01-07 15:52           ` Michal Hocko
2011-01-11 13:33   ` Pavel Machek
2011-01-11 14:28     ` Michal Hocko
2011-01-11 14:47     ` Alex Riesen
2011-01-11 17:19   ` Michal Hocko
2011-01-11 17:37     ` Michal Hocko
2011-01-11 18:37       ` Michal Hocko [this message]
2011-01-11 17:39     ` Chris Wilson
2011-01-11 17:44       ` Michal Hocko
2011-01-12  0:35       ` Indan Zupancic
2011-01-12 12:07         ` Chris Wilson
2011-01-12 12:14           ` Chris Wilson
2011-01-13  0:35           ` Indan Zupancic
2011-01-07 19:20 Zephaniah E. Loss-Cutler-Hull

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=20110111183756.GA3782@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=indan@nul.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.