Hi!
> >> Maybe that even would give me a chance to fix some hardware problem
> >> causing the timeout, and then retry the resume.
> >
> > ..while doing resume few times, trying to change hw config to make it
> > resume is _way_ more dangerous.
>
> I guess it would be. But then, what are the chances it would make the
> situation any worse? Probably never would work, but at least I would
Yes, you could make the situation worse -- if you actually
succeeded. We are talking silent corruption on filesystem here...
("swsusp gives you enough rope to blow up small town")...
> Thanks for all the good work! I've been running Linux on a number of
> laptops since 1998 and am most impressed by the swsusp evolution the
> last few years. Things weren't too bad when APM used to work and
> "lots of RAM" meant 80GB, but today I don't think I could use a laptop
> without swsusp.
Thanks. (I'd still like to see that 80GB laptop :-).
Pavel
--
Thanks, Sharp!
-
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]
