linux-kernel - Re: Broken suspend to RAM on Asus P8P67-M motherboard (bad BIOS?)

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]

Date:	Thu, 29 Dec 2011 00:55:04 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Paul B. Henson" <henson@....org>
Cc:	linux-kernel@...r.kernel.org,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: Broken suspend to RAM on Asus P8P67-M motherboard (bad BIOS?)

Hi,

On Thursday, December 29, 2011, Paul B. Henson wrote:
> I have an Asus P8P67-M Pro motherboard which fails to suspend to ram
> under Linux yet suspends successfully under Windows 7.
> 
> Under Windows 7, suspending results in the typical slowly blinking
> power light, and the system wakes up correctly.
> 
> Under Linux (tested with 3.0.7 and 3.1.6), on entering suspend mode the
> power light turns off and stays off, it does *not* blink. On attempting
> to wake up, the power light turns on momentarily and the fans spin up,
> the power light goes off again and the fans spin down, then the power
> light/fans come on but nothing happens, the box is completely wedged,
> not even the reset button works, requiring a hard power cycle to bring
> back.

You may try to pass acpi_sleep=nonvs or acpi_sleep=sci_force_enable to
the kernel command line and retest.

> While working on the issue, I noticed the following suspicious ACPI
> errors logged when doing a core test of STR:
> 
> Dec 28 14:28:41 htpc-lr kernel: ACPI: Preparing to enter system sleep
> state S3
> Dec 28 14:28:41 htpc-lr kernel: ACPI Error: [RAMB] Namespace lookup
> failure, AE_NOT_FOUND (20110623/psargs-359)
> Dec 28 14:28:41 htpc-lr kernel: ACPI Error: Method parse/execution
> failed [\_PTS] (Node ffff88011e8a3a38), AE_NOT_FOUND
> (20110623/psparse-536)

Well, please attach the output of acpidump from your system.

> There is also an ACPI complaint during boot:
> 
> ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND
> (20110623/psargs-359)
> ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW]
> (Region) (20110623/nsinit-349)
> 
> The core test worked fine with no issues. I'm pretty sure the root cause
> of the problem is that the system is not correctly entering S3 due to
> these ACPI issues (given the lack of the usual blinking power light).
> I'm guessing there's something broken in the BIOS and have opened a
> support request with Asus.
> 
> However, given it "works under Windows (tm)" 8-/, I don't anticipate a timely
> response from Asus <sigh>.
> 
> Clearly Windows is working around whatever BIOS problem exists. If it's
> not too ugly or distasteful, it would be nice if Linux could do so as
> well, I hate it when Windows seems more robust ;).

Well, the problem is we need to know what to do, which may be difficult
(if not impossible) to figure out without the (already missing) vendor
information.

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/