What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[Michael Leun]

Is there any timeline for bringing bugzilla.kernel.org up again?


I'm mainly asking because I was tracking 

Bug 37142 – [GM965/KMS/UXA] memory corruption on resume from hibernate

a memory corruption issue which is around for quite some time, see

http://thread.gmane.org/gmane.linux.kernel/1116939/focus=1117113

that was March 2011. I suspect this bug might be there since
introduction of KMS.

My workaround since I noticed that bug was to use tuxonice for suspend
to disk, what works perfectly (that in particular means without memory
corruption), but unfortunately the current developer of tuxonice, Nigel
Cunningham is going to stop development, see

http://lists.tuxonice.net/pipermail/tuxonice-users/2011-November/000945.html


Rafael, Richard: What do you think is the current state of this bug?
Was it ever fixed for you?

As far as I remember in bugzilla 37142 there were patches floating
around, but they did'nt make any change for me. I didn't notice any
change on that bug until kernel.org went down due to that security
issue.

At the moment I'm compiling a vanilla 3.1 to see if I still see this
bug.

-- 
MfG,

Michael Leun

Re: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[Nigel Cunningham]

Hi.

On 01/11/11 21:14, Michael Leun wrote:
> Is there any timeline for bringing bugzilla.kernel.org up again?
> 
> 
> I'm mainly asking because I was tracking 
> 
> Bug 37142 – [GM965/KMS/UXA] memory corruption on resume from hibernate
> 
> a memory corruption issue which is around for quite some time, see
> 
> http://thread.gmane.org/gmane.linux.kernel/1116939/focus=1117113
> 
> that was March 2011. I suspect this bug might be there since
> introduction of KMS.
> 
> My workaround since I noticed that bug was to use tuxonice for suspend
> to disk, what works perfectly (that in particular means without memory
> corruption), but unfortunately the current developer of tuxonice, Nigel
> Cunningham is going to stop development, see
> 
> http://lists.tuxonice.net/pipermail/tuxonice-users/2011-November/000945.html

I'm asking for input, not committing myself to stopping development
(yet). If there are good reasons to continue to maintain ToI, I'll
happily do that - I just have no idea at the moment how many people are
still saying "[u]swsusp doesn't work for me, TuxOnIce does."

Regards,

Nigel
-- 
Evolution (n): A hypothetical process whereby improbable
events occur with alarming frequency, order arises from chaos, and
no one is given credit.

Re: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[richard -rw- weinberger]

On Tue, Nov 1, 2011 at 11:14 AM, Michael Leun <ml@newton.leun.net> 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 2.6.37.4. Currently I'm using 3.1.

-- 
Thanks,
//richard

Re: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[Michael Leun]

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

> On Tue, Nov 1, 2011 at 11:14 AM, Michael Leun <ml@newton.leun.net>
> 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 2.6.37.4. 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
time.

-- 
MfG,

Michael Leun

Re: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[richard -rw- weinberger]

On Tue, Nov 1, 2011 at 1:18 PM, Michael Leun <ml@newton.leun.net> wrote:
>
> On Tue, 1 Nov 2011 13:01:58 +0100
> richard -rw- weinberger <richard.weinberger@gmail.com> wrote:
>
>> On Tue, Nov 1, 2011 at 11:14 AM, Michael Leun <ml@newton.leun.net>
>> 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 2.6.37.4. 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.

Okay. I'll retest!

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

I've never used tuxonice. What makes it so special?

-- 
Thanks,
//richard

Re: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development

[Michael Leun]

On Tue, 1 Nov 2011 13:20:59 +0100
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:

> > So, you might want to try if you can cure your dying HW with some
> > tuxonice ;-)
> 
> I've never used tuxonice. What makes it so special?

A few years ago, at least for me, it was the first really usable suspend
to disk solution working almost out of the box.


>From linux/Documentation/power/tuxonice.txt (some of that seems to be
outdated with the current in kernel implementation):


4. Why not just use the version already in the kernel?

   The version in the vanilla kernel has a number of drawbacks. The most
   serious of these are:
        - it has a maximum image size of 1/2 total memory;
        - it doesn't allocate storage until after it has snapshotted
   memory. This means that you can't be sure hibernating will work
   until you see it start to write the image;
        - it does not allow you to press escape to cancel a cycle;
        - it does not allow you to press escape to cancel resuming;
        - it does not allow you to automatically swapon a file when
          starting a cycle;
        - it does not allow you to use multiple swap partitions or
   files;
        - it does not allow you to use ordinary files;
        - it just invalidates an image and continues to boot if you
          accidentally boot the wrong kernel after hibernating;
        - it doesn't support any sort of nice display while hibernating;
        - it is moving toward requiring that you have an
   initrd/initramfs to ever have a hope of resuming (uswsusp). While
   uswsusp will address some of the concerns above, it won't address
   all of them, and will be more complicated to get set up;
        - it doesn't have support for suspend-to-both (write a
   hibernation image, then suspend to ram; I think this is known as
   ReadySafe under M$).



-- 
MfG,

Michael Leun