linux-kernel - Re: i915: display doesn't get on back after returning from standby in 2.6.27-rc*

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101126084538.GC12939@bicker>
Date:	Fri, 26 Nov 2010 11:45:38 +0300
From:	Dan Carpenter <error27@...il.com>
To:	Keith Packard <keithp@...thp.com>
Cc:	Nick Bowler <nbowler@...iptictech.com>,
	Michal Hocko <mhocko@...e.cz>,
	"Rafael J. Wysocki" <rjw@...k.pl>, intel-gfx@...ts.freedesktop.org,
	LKML <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org
Subject: Re: i915: display doesn't get on back after returning from standby
 in 2.6.27-rc*

On Thu, Nov 25, 2010 at 11:31:04AM -0800, Keith Packard wrote:
> On Thu, 25 Nov 2010 11:10:58 -0500, Nick Bowler <nbowler@...iptictech.com> wrote:
> > On 2010-11-25 16:58 +0100, Michal Hocko wrote:
> > > [Let's add Rafael for regression tracking]
> > > 
> > > On Tue 23-11-10 13:32:34, Michal Hocko wrote:
> > > > Hi,
> > > > since early 2.6.37 (I haven't bisected when exactly) my screen doesn't
> > > > get on after it got into standby mode. I have to either change to a
> > > > text console and back (if it gets to standby by the screen saver) or
> > > > close the lid on my laptop if I try:
> > > > xset dpms force standby
> > [...]
> > > > Is this a known issue?
> > 
> > I suspect that all of the following are the same issue:
> > 
> >   https://bugzilla.kernel.org/show_bug.cgi?id=23122
> >   https://bugzilla.kernel.org/show_bug.cgi?id=23472
> >   https://bugs.freedesktop.org/show_bug.cgi?id=31803
> 
> I've provided a couple of fixes that might be relevant here -- neither
> kernel nor user mode were setting the tracked DPMS state of the outputs
> to ON when doing mode setting, which caused all kinds of comedy. These
> should fix 23472 and 31803. I'm not entirely sure what's up with 23122,
> but it's possible that it's the same issue.
> 

Where are the patches?  I pulled drm-next but I don't see them.

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/