linux-kernel - Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring

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: <CACraW2pN4+d4Cx7kA_HLc0AKippt1gV2e0kOD0Dng=+_pUai8w@mail.gmail.com>
Date:	Thu, 11 Apr 2013 08:16:51 +0300
From:	Tomas Melin <tomas.melin@....fi>
To:	Richard Cochran <richardcochran@...il.com>, daniel.vetter@...ll.ch
Cc:	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
	DRI Development <dri-devel@...ts.freedesktop.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Airlie <airlied@...il.com>,
	Chris Wilson <chris@...is-wilson.co.uk>, stable@...r.kernel.org
Subject: Re: [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring

On Wed, Apr 10, 2013 at 9:32 PM, Tomas Melin <tomas.melin@....fi> wrote:
> On Tue, Apr 9, 2013 at 10:51 PM, Daniel Vetter <daniel.vetter@...ll.ch> wrote:
>> v2: Try harder not to create a big patch (Chris).
>>
> Tested the patch applied to 3.9-rc6. Atleast on my machine that
> helped, although once I managed to get the error (but not warning and
> call trace as before):
> [drm:i9xx_crtc_mode_set] *ERROR* Couldn't find PLL settings for mode!
>

Update: the situation where I still get an error is if the machine is
in standby with the lid open. Then close and open will generate that
kind of error. The patch however fixes the original problem.

thanks,
Tomas
--
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/