On Mon, 16 Jul 2007, Rafael J. Wysocki wrote:
On Sunday, 15 July 2007 22:13, [EMAIL PROTECTED] wrote:
On Sun, 15 Jul 2007, Rafael J. Wysocki wrote:
Hi,
Since many alternative approaches to hibernation are now being considered and
discussed, I thought it might be a good idea to list some
On Monday, 16 July 2007 00:42, [EMAIL PROTECTED] wrote:
On Mon, 16 Jul 2007, Rafael J. Wysocki wrote:
On Sunday, 15 July 2007 22:13, [EMAIL PROTECTED] wrote:
On Sun, 15 Jul 2007, Rafael J. Wysocki wrote:
Hi,
Since many alternative approaches to hibernation are now being considered
On Sun, 15 Jul 2007 [EMAIL PROTECTED] wrote:
for a pure hibernate mode, you will be powering off the box after saving
the suspend image. why are there any special ACPI modes involved?
Because, for example, on my machine the status of power supply (present
vs not present) is not updated
On Sun, 15 Jul 2007 [EMAIL PROTECTED] wrote:
(1) Filesystems mounted before the hibernation are untouchable
When there's a memory snapshot, either in the form of a hibernation
image,
or in the form of the old kernel and processes available to the new
kexeced kernel
On Sun, 15 Jul 2007, Al Boldi wrote:
Alan Stern wrote:
On Sun, 15 Jul 2007, Al Boldi wrote:
If possible, during a restore devices should be brought back to
the same state in which they were before the corresponding
hibernation. Of course in some situations it might be
Hi.
On Monday 16 July 2007 09:15:47 Alan Stern wrote:
On Sun, 15 Jul 2007 [EMAIL PROTECTED] wrote:
for a pure hibernate mode, you will be powering off the box after
saving
the suspend image. why are there any special ACPI modes involved?
Because, for example, on my machine the
On Sun, 15 Jul 2007, Alan Stern wrote:
On Sun, 15 Jul 2007 [EMAIL PROTECTED] wrote:
for a pure hibernate mode, you will be powering off the box after saving
the suspend image. why are there any special ACPI modes involved?
Because, for example, on my machine the status of power supply
On Mon, 16 Jul 2007, Rafael J. Wysocki wrote:
On Monday, 16 July 2007 00:42, [EMAIL PROTECTED] wrote:
On Mon, 16 Jul 2007, Rafael J. Wysocki wrote:
On Sunday, 15 July 2007 22:13, [EMAIL PROTECTED] wrote:
On Sun, 15 Jul 2007, Rafael J. Wysocki wrote:
The ACPI specification requires us
On Sun, 15 Jul 2007, Alan Stern wrote:
On Sun, 15 Jul 2007 [EMAIL PROTECTED] wrote:
(1) Filesystems mounted before the hibernation are untouchable
When there's a memory snapshot, either in the form of a hibernation image,
or in the form of the old kernel and processes available to the
On Sun, 15 Jul 2007, Alan Stern wrote:
On Sun, 15 Jul 2007, Al Boldi wrote:
Alan Stern wrote:
On Sun, 15 Jul 2007, Al Boldi wrote:
This should be the responsibility of the kexec'd hibernating kernel.
Note though in (6), the normal kernel takes care of preparing devices,
then the
On Sun, Jul 15, 2007 at 02:33:32PM +0200, Rafael J. Wysocki wrote:
(snip)
Many of these assumptions are based on the assumption that we want to
save a full image of RAM. I'm not convinced that this is true. The two
things that we need are application state and hardware state.
Application
On Mon, 16 Jul 2007, Matthew Garrett wrote:
On Sun, Jul 15, 2007 at 02:33:32PM +0200, Rafael J. Wysocki wrote:
(snip)
Many of these assumptions are based on the assumption that we want to
save a full image of RAM. I'm not convinced that this is true. The two
things that we need are
Alan Stern wrote:
As for the VGA font, the effect is easy to see: Run setfont before
hibernating; when you resume the original font will be back. The
kernel simply does not bother to save the VGA font information across a
hibernate.
This could probably be handled by a device suspend/resume
[EMAIL PROTECTED] writes:
[snip]
Isn't is possible to avoid this problem by mounting an ext3 filesystem
as readonly ext2? Provided the filesystem isn't dirty it should be
doable. (And provided the filesystem doesn't use any ext3 extensions
that are incompatible with ext2.)
from the last
401 - 414 of 414 matches
Mail list logo
