Hi.
Rafael J. Wysocki wrote:
Is there another mechanism preventing this?
Not at the kernel level, but you can prevent this from happening by running
mkswap on all swap spaces that refuse to come up after a fresh boot.
We really should do something about this. It should be possible to
handle
Hi.
Rafael J. Wysocki wrote:
I suppose we can always disable this when we start to support hardware
changing over hibernate (I have ideas in this direction - memory cold
plugging, for a start).
Well, if we support such features, we won't be following ACPI any more.
Mmm. Apparently I'm not
Hi!
That way any suspend breakage would be detectable (and bisectable)
in automated testing - if the resume does not come back after 10-20
seconds then the test failed.
Yes, but please note that some systems require user space
manipulations of the graphics adapter for
On Thu 2007-12-27 19:15:16, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
The execution of ACPI global control methods _GTS and _BFS is
currently tied to the preparation to enter a sleep state and to the
leaving of the sleep state, respectively. However, these functions
Hi,
I hope that this is the right list for my problem:
I have a LG e500 Notebook (Core2Duo - Santa rosa).
All works fine but the Suspend:
Suspend to ram works fine. The Notebook is off but the LED is flashing.
But if I press any key to resume the system, the system goes on for zwo
minutes
On Thursday, 3 of January 2008, Nigel Cunningham wrote:
Hi.
Rafael J. Wysocki wrote:
I suppose we can always disable this when we start to support hardware
changing over hibernate (I have ideas in this direction - memory cold
plugging, for a start).
Well, if we support such
Hi Matthew,
On Dec 26, 2007 5:48 PM, Matthew Garrett [EMAIL PROTECTED] wrote:
+ } else
+ printk (KERN_INFO HP WMI: Unknown response received\n);
+
+ return;
No need for empty returns.
+}
+
+static int __init hp_wmi_init(void)
+{
+ int err;
+ const
On Thursday, 3 of January 2008, Pavel Machek wrote:
On Thu 2007-12-27 19:15:16, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
The execution of ACPI global control methods _GTS and _BFS is
currently tied to the preparation to enter a sleep state and to the
leaving
On Thursday, 3 of January 2008, Pavel Machek wrote:
Hi!
From: Rafael J. Wysocki [EMAIL PROTECTED]
The preparation to enter an ACPI system sleep state is now tied to
the disabling of GPEs, but the GPEs should not be disabled before
suspending devices. Since on ACPI 1.0x systems the
On Thursday, 3 of January 2008, Shaohua Li wrote:
On Wed, 2008-01-02 at 22:05 +0800, Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Shaohua Li wrote:
ACPI defines a hardware signature. BIOS calculates the signature
according to hardware configure, if hardware changes, the
Hi.
Rafael J. Wysocki wrote:
On Thursday, 3 of January 2008, Nigel Cunningham wrote:
Hi.
Rafael J. Wysocki wrote:
I suppose we can always disable this when we start to support hardware
changing over hibernate (I have ideas in this direction - memory cold
plugging, for a start).
Well, if
Reintroduce run time configurable max_cstate for !CPU_IDLE case.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
===
--- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
Venki Pallipadi wrote:
Reintroduce run time configurable max_cstate for !CPU_IDLE case.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
===
---
On Fri, 2008-01-04 at 01:04 +0800, Rafael J. Wysocki wrote:
On Thursday, 3 of January 2008, Shaohua Li wrote:
On Wed, 2008-01-02 at 22:05 +0800, Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Shaohua Li wrote:
ACPI defines a hardware signature. BIOS calculates the signature
14 matches
Mail list logo
