linux-kernel - Re: Corrupted files after suspend to disk

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: <alpine.LNX.2.00.1203290011230.25526@pobox.suse.cz>
Date:	Thu, 29 Mar 2012 00:12:53 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Dave Jones <davej@...hat.com>
Cc:	Andreas Hartmann <andihartmann@...19freenet.de>,
	richard -rw- weinberger <richard.weinberger@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
	keithp@...thp.com
Subject: Re: Corrupted files after suspend to disk

On Mon, 12 Mar 2012, Dave Jones wrote:

>  > https://bugzilla.novell.com/show_bug.cgi?id=732908
>  > 
>  > Following the link, you are able to compare the used chips - maybe there
>  > are some equal components?
> 
> This looks like the i915 corruption problem mentioned in a few other threads.
> 
> if you compare the hexdump of the good/bad files, you find that the corruption
> happens in 8x 4 byte writes of either 0x00000000 or 0x00aaaaaa.
> 
> KeithP clued me in last week that that looks like an ARGB pixel quad, so these
> writes are likely 8 pixel strips.

So this keeps happening to me on almost every resume still ... Keith, is 
there any way I could help you debug this?

-- 
Jiri Kosina
SUSE Labs
--
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/