On Tue, Jul 03, 2007 at 03:54:55PM -0400, Alan Stern wrote:
> On Tue, 3 Jul 2007, Matthew Garrett wrote:
> > There's nothing wrong with it as such, it's just that our implementation
> > appears to suck in a myriad of small ways that keep cropping up and
> > biting people. Even without the sys_sync(), freezing processes results
> > in the suspend failing because syslog is stuck in D state and won't go
> > into the refrigerator.
>
> Okay, I can believe that. The proper response then is to fix the
> freezer, not eliminate it. Has the syslog problem been reported on
> linux-pm? I don't recall hearing of it before.
See the start of this thread. It's just not clear what the freezer buys
us - removing it gets rid of a load of subtle issues and complexity, and
turns system suspend into something that looks more like runtime
suspend (which might then encourage people to get runtime suspend
right...)
--
Matthew Garrett | [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
