linux-kernel - Re: [linux-pm] Tyan S2923-E suspend to ram fails to 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: <20080812103143.GD2641@elf.ucw.cz>
Date:	Tue, 12 Aug 2008 12:31:43 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	linux-pm@...ts.linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Tyan S2923-E suspend to ram fails to resume

On Sat 2008-08-09 15:42:22, Simon Arlott wrote:
> On 08/08/08 12:20, Simon Arlott wrote:
>> On Fri, August 8, 2008 08:14, Pavel Machek wrote:
>>> On Mon 2008-08-04 22:56:07, Simon Arlott wrote:
>>>> My system (Tyan S2923-E, dmesg attached) suspends ok in
>>>> all pm_test modes, but it won't resume with pm_test
>>>> "none".
>>>>
>>>> [    6.423515] mem full: hash matches
>>>>
>>>> When I press the power button, the port 80 display shows:
>>>> FF D0 23 01 D0 ... DE
>>>> (and again each time I press it)
>>>>
>>>> If I force it to turn off, then on again:
>>>> FF D0 23 01 D0 ... FF D0 23 01 D0 ... (D2?) D3 00 01 D5
>>>> D6 <normal boot>
>>>>
>>>> Any ideas? (onboard SAS is disabled, watchdog is
>>>> disabled, everything else is enabled, PCI-E graphics
>>>> card)
>>>
>>> Try verifying if it reaches assembly code under realmode/ ...
>
> I've tried acpi_sleep=s3_beep, and this:
>
> diff --git a/arch/x86/kernel/acpi/realmode/wakeup.S b/arch/x86/kernel/acpi/realmode/wakeup.S
> index 3355973..50e50df 100644
> --- a/arch/x86/kernel/acpi/realmode/wakeup.S
> +++ b/arch/x86/kernel/acpi/realmode/wakeup.S
> @@ -37,6 +37,11 @@ signature:	.long	0x51ee1111
> 	.code16
> wakeup_code:
> _start:
> +	movb $0xC1, %al
> +	outb %al, $0x80
> +	cli
> +	hlt
> +
> 	cli
> 	cld
>
>
> Which doesn't work either.

Yep, that should work. When it does not, it means BIOS is not
returning to our real mode code :-(. You may want to try disabling
APIC and similar stuff, in hope of working around BIOS bug you are
hitting, but ...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/