linux-kernel - [REGRESSION] Re: [Bug 11568] spontaneous reboot on resume with 2.6.27

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

Message-Id: <200810122144.02897.rjw@sisk.pl>
Date:	Sun, 12 Oct 2008 21:44:02 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andy Wettstein <ajw1980@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Pavel Machek <pavel@...e.cz>, "H. Peter Anvin" <hpa@...or.com>
Cc:	bugme-daemon@...zilla.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: [REGRESSION] Re: [Bug 11568] spontaneous reboot on resume with 2.6.27

On Sunday, 12 of October 2008, bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11568
> 
> 
> 
> 
> 
> ------- Comment #27 from ajw1980@...il.com  2008-10-12 12:25 -------
> SMP enabled with patch from #24 does not abort the suspend, and of course
> reboots on resume.

Andy, thanks for testing.

Ingo, Peter, Pavel,

The regression here is that x86_64 non-SMP systems using SMP kernel fail to
resume from suspend to RAM, most probably due to the trampoline code being
busted.  I haven't found anything obviously wrong in the code yet, but I
suspect that something simply writes over the (original) trampoline code.

This is in 2.6.27 as well as in the current mainline and it's quite urgent,
because we'll get hit by it in distro kernels based on 2.6.27 if we don't fix
it timely. 

Please have a look at bug #11568.

Thanks,
Rafael
--
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/