linux-kernel - Re: Regression: suspend to ram completely broken since at least 3.13-rc5, works with 3.12.

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: <20141202144615.GA3178@xo-6d-61-c0.localdomain>
Date:	Tue, 2 Dec 2014 15:46:15 +0100
From:	Pavel Machek <pavel@....cz>
To:	Volker Armin Hemmann <volkerarmin@...glemail.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Regression: suspend to ram completely broken since at least
 3.13-rc5, works with 3.12.

Hi!

> with kernel 3.12.X with X tested up to .23 suspend to ram works
> flawlessly. My machine suspends quickly and wakes up reliably, giving me
> uptimes measured in weeks.
> 
> Every kernel I tried between 3.13.0-rc5 and 3.16.7 on the other hand
> shows this behaviour:
> 
> IF suspend works it takes ages. Video blanks quickly, harddisks are
> turned off, then it is stuck for a long time (more minute than tens of
> seconds), and at some point suspends.
> 
> Afterwards there is a 50% chance it will wake up. In that case: nothing
> in dmesg.
> If it does not wake up on pressing any button, I have to press power
> button for a nice cold boot.
> 
> Even if it does suspend and resume successfully, it will NOT suspend the
> next time. Never.
> 
> The much more likely failure mode looks like this:
> It will blank video and turn of harddisks and then nothing happens. usb
> dead, ps2 keyboard dead, no harddisk activity, fans are spinning,
> mainboard is powered - and nothing happens. I can turn off or hit reset
> button.
> 
> Of course, after a reboot nothing will show up in the logs.
> 
> So this is a severe regression. Box worked, it stopped working.

Any chance to do a bisect? Any chance to try with minimum drivers?

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