[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5D9C407E-C5BE-434D-86B7-9EA58331F35D@mac.com>
Date: Sat, 28 Apr 2007 23:43:27 -0400
From: Kyle Moffett <mrmacman_g4@....com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Pekka J Enberg <penberg@...helsinki.fi>,
LKML <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...sign.ru>
Subject: Re: Back to the future.
On Apr 28, 2007, at 19:45:01, Linus Torvalds wrote:
> On Sun, 29 Apr 2007, Rafael J. Wysocki wrote:
>> Well, I'm not sure whether or not that still would have been the
>> case if we had stopped to freeze kernel threads for the
>> hibernation/suspend.
>
> Did you miss the email where Paul pointed out that Mac/PowerPC
> didn't use to do any of this? And apparently never had any issues
> with it? And probably worked more reliably several years ago than
> suspend/hibernation
> does _today_?
Still works pretty reliably; the last time my PowerBook G4 was
rebooted was 6 weeks ago. Once every 60 suspends or so the kernel
USB driver gets really confused and doesn't wake up the USB
controller properly, leading to dead keyboard/mouse, but other than
that I never have problems. I wouldn't be surprised if I could
comment out 90% of the "suspend" code and still have it work, the
hardware in is is incredibly robust. I can even swap batteries while
it's in suspend-to-RAM, as long as I do it in less than 45 sec or so;
I get around 6-7 days of suspend-to-RAM time on a full charge.
Cheers,
Kyle Moffett
-
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/
Powered by blists - more mailing lists