[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111229040110.GA10398@bender.csupomona.edu>
Date: Wed, 28 Dec 2011 20:01:12 -0800
From: "Paul B. Henson" <henson@....org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: "linux-kernel@...r.kernel.org" <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?)
On Wed, Dec 28, 2011 at 03:55:04PM -0800, Rafael J. Wysocki wrote:
> You may try to pass acpi_sleep=nonvs or acpi_sleep=sci_force_enable to
> the kernel command line and retest.
Neither of these options made any apparent difference.
> Well, please attach the output of acpidump from your system.
Attached.
> 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.
Understood. I only bring this up as it works under Windows 7, so I was
hoping whatever workaround Microsoft is using might work for Linux too.
I will continue to poke Asus to fix their BIOS, but I'm stuck in level 1
support without too much hope of getting to someone in a position to
understand the issue let alone fix it <sigh>. It doesn't help there's an
unrelated issue with suspend/resume on this board involving overclocking
and PLL overvoltage, which doesn't apply here but level 1 wants to jump
through those hoops anyway.
Thanks much for your reply.
(Note to potential responders; I'm not subscribed to any of these lists
so would appreciate the courtesy of a CC).
View attachment "acpidump.out" of type "text/plain" (165495 bytes)
Powered by blists - more mailing lists