linux-kernel - Re: [Bisected] 3.7-rc1 can't resume

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: <3513716.1dZa4Epkei@vostro.rjw.lan>
Date:	Sun, 17 Feb 2013 21:40:42 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Jonas Heinrich <onny@...ject-insanity.org>
Cc:	hpa@...or.com, len.brown@...el.com, pavel@....cz,
	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [Bisected] 3.7-rc1 can't resume

On Sunday, February 17, 2013 05:48:25 PM Jonas Heinrich wrote:
> Hello,
> since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43)
> from suspend2ram anymore.
> 
> I started a kernel bisection (see bisection_log in attachement). Also
> see kernel conifg @ attachement.
> 
> The culprit commit seems to be: 
> - x86, smap: Do not abuse the [f][x]rstor_checking() functions for user space
> commit e139e95590dfebab81841bf7a3ac46500f51a47c

Does the commit immediately preceding this one behave correctly?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/