[lkml]   [2011]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: What about / Bug 37142 / Tuxonice developer going to quit development

On Tue, 1 Nov 2011 13:01:58 +0100
richard -rw- weinberger <> wrote:

> On Tue, Nov 1, 2011 at 11:14 AM, Michael Leun <>
> wrote:
> > Rafael, Richard: What do you think is the current state of this bug?
> > Was it ever fixed for you?
> No.
> But I'm quite sure that my netbook is causing the issue.
> Now I can reproduce the error after 1-2 s2disk runs.
> A few months ago 10-20 runs were needed.
> My netbook seesm to die. :-(
> But I'll retest the issue with kernel Currently I'm using
> 3.1.

I doubt that is related to HW, because I can reproduce on at least two,
if not 3 different machines and on the two where it matters to me using
tuxonice fixed it.

So, you might want to try if you can cure your dying HW with some
tuxonice ;-)

With 3.1 it also takes me one or two tries to see an corruption (create
md5 over some *bin* and *lib* stuff, suspend, resume, check md5sum and
if there are faults throw away caches, what "fixes" the errors seen if
the file affected is not currently opened).

But regarding the question who needs tuxonice, to be honest:

OK, at the moment there is this bug, but if that would not be there I
clearly would prefer the in kernel solution and in fact before there
was this bug I used uswsusp.

I happily would take the additional features of tuxonice if available
in the vanilla kernel, but for me there are no additional features in
tuxonice which justify for dealing with an out of tree patch all the


Michael Leun

 \ /
  Last update: 2011-11-01 13:21    [W:0.044 / U:35.980 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site