linux-kernel - Re: [Regression in 3.10] Garbage displayed after resume on Acer Aspire S5

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]

Date:	Sat, 06 Jul 2013 22:26:28 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Daniel Vetter <daniel@...ll.ch>
Cc:	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Regression in 3.10] Garbage displayed after resume on Acer Aspire S5

On Saturday, July 06, 2013 04:16:36 PM Daniel Vetter wrote:
> On Sat, Jul 6, 2013 at 3:59 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > Hi,
> >
> > I've just started to play with a new Acer Aspire S5 test box and noticed that
> > garbage is displayed after resume from suspend to RAM with the 3.10 kernel
> > (under KDE 4.10.3 on openSUSE 12.3).  The display corruption goes away after
> > killing X and restarting it.
> >
> > The CPU is a Core i5-3317U (Ivy Bridge), i915 graphics.
> >
> > That doesn't happen with 3.9 (same config otherwise).  It also doesn't happen
> > with my older Sandy Bridge-based box (with 3.10), so I suspect Ivy Bridge
> > specifics.
> >
> > Is this known?  Do you want me to bisect?
> 
> Screenshot of the garbage would be a good start I'd say.

Well, it's just garbage.  Attached anyway.

When the "screen lock" password prompt screen starts it's completely garbled.
When I blind-type in the password, the desktop shows up and it looks kind of OK
until a new window is opened and then it looks like rectangular area full of
horizontal lines.

> Also, does a vt-switch not resolve the issue?

No, switching VTs back and forth doesn't help when this happens (it makes
things worse actually).

It's not 100% reproducible (but close to that on the IVB machine) and I've seen
it once on my other machine based on Sandy Bridge too.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
Download attachment "snapshot1.png" of type "image/png" (30416 bytes)