On Tue, 3 Jul 2007, Matthew Garrett wrote:
> > I agree that in general the suspend process should not have to wait for
> > a userspace callback to complete. Indeed, there's no particular
> > reason that anything running during STR should have to wait for
> > something in userspace to complete. Given that fact, I don't see
> > anything wrong with freezing userspace when doing STR.
>
> 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.
Alan Stern
-
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]