linux-kernel - Suspend to RAM regression (bisected)

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-next>] [day] [month] [year] [list]

Date:	Sun, 20 Jul 2008 21:03:49 -0500
From:	"Carlos R. Mafra" <crmafra2@...il.com>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, airlied@...hat.com
Subject: Suspend to RAM regression (bisected)

Hi,

There is a suspend to RAM regression in the latest Linus tree of
17th of july (5b664cb235e). It was working perfectly with 
2.6.26.

If I suspend to RAM from X with 'echo mem > /sys/power/state' the
screen comes back very dark and I can't read anything.
If I switch to the text console and then go back to X this problem
is fixed and everything is ok.

I bisected this regression down to c0e09200dc0813972442e550a5905a132768e56c
("drm: reorganise drm tree to be more future proof"), and I checked that
reverting this commit (it reverts cleanly) really makes the regression go
away.

The laptop is a Vaio 64bit with Intel GM965/GL960 graphics card.
More information about my laptop can be found here:
http://www.ift.unesp.br/users/crmafra/dmesg-good.txt

--
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/