function thaw_kernel_threads introduced by new kernel stable patch

Hi all,

the kernel stable patch 

pm-hibernate-fix-s2disk-regression-related-to-freezing-workqueues

has introduced another version of the function "thaw_kernel_threads"
that conflicts with this one from TuxOnIce,

Regards,

Jordi Pujol

Live never ending Tale
GNU/Linux Live forever!
http://livenet.selfip.com

Proposed git tree changes.

Hi all.

I'm considering making some changes to the way I arrange the git trees,
partly in fulfillment of suggestions posted on this list already and
would like your input. Proposed changes are:
- Make one big git tree instead of separate ones for each branch
- For each vanilla kernel version, have a upstream and a tuxonice
branch, hence upstream-3.0, tuxonice-3.0, upstream-3.1, tuxonice-3.1,
upstream-head, tuxonice-head and so on
- Tags for tuxonice branches will be in the format
tuxonice-<tuxonice-version>-for-≤upstream-version> so that there will be
no namespace difficulties
- At any time, only the 2 most recent upstream releases will get
TuxOnIce updates. This will reduce the amount of testing I need to do
before releases. Until now, I've only tended to drop old releases when
more recent changes make backporting too much effort.

If these changes sound good to people, I'll start implementing them.
Hopefully I'll then be able to fix up my long neglected scripts and get
regular updates and patches going again.

Regards,

Nigel
--

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

Web Git down?

Hello list,

I was wondering if the gitweb interface is down or not, or is it just my 
browser of choice (luakit) screwing around?

Cheers,
Ignas A.

First cut of catch up patch... Still frozen on restore...

Nigel, Merry Christmas,

Thanks for updating the git tree - I could use TOI once again, now on 
3.2 kernels...

I keep reading that it works for most of people, however on EeePC with 
i915 it is crashing 100% on restore, the last messages are:

Reading kernel & process data...
Atomic restore.
Doing atomic copy/restore.

I have tried on 2 different devices, it is 100% repeatable.
I tried from normal X-session, then from a single mode, then even from 
single mode with nomodeset, without text-gui - can not be simpler than 
that - yet it still crashes... Tried to disable all 
no-[flusher_thread/pageset2/readahead/multithreded_io] - not much help...

Is there a trick to debug it?

Thanks, Woody

First cut of catch up patch.

Hi all.

Here's a first cut of the catch-up patch. I've not had the opportunity
to test it yet, but thought I'd throw it out there anyway for those of
you who are so keen to try the latest and greatest. Shouldn't eat your
children or anything like that, but you've been warned that I haven't
given it the chance to eat mine yet...

Regards,

Nigel
--

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

_______________________________________________
TuxOnIce-devel mailing list
TuxOnIce-devel <at> lists.tuxonice.net
http://lists.tuxonice.net/listinfo/tuxonice-devel

Official patch for 3.1 kernel?

Bit late in the game here, but I'm glad that Tuxonice is going to stay with us for a while longer!

I saw that you have the 3.1 branch up and I'm going to get that via git in a little while to test it out (however
from the other messages so far, it looks like it will be fine), I was just wondering if there is going to be an
official patch released soon for it (or am I managing to miss it completely)?

Anyways, just wanted to see if an actual zipped patch would be put up soon.  Thanks again for the awesome work
Nigel!  I've been using TOI for about two years now and have had a great experience with it ever since!
------------------------------------------------------------------------------------

Re: ACPI events dead after suspend / resume in 3.x

On 18.12.2011 19:42, Harald Judt wrote:
> Am 18.12.2011 19:09, schrieb U Kuehn:
>> Hi Harald,
>>
>> On 18.12.2011 15:12, Harald Judt wrote:
>>>> All acpi events are gone after a suspend / resume cycle under TuxOnIce.
>>>> This happens with the newest 3.1.5 branch (cloned Dec 18, 2011) from
>>>> the
>>>> tuxonice git, but happened before for all versions I tried (3.0.9,
>>>> 3.0.11, 3.0.12).
>>>>
>>>> The problem seems to have occured somewhere between 2.6.39.4 and the
>>>> 3.x
>>>> series. I am attaching my current config for 3.1.5 from the tuxonice
>>>> git.
>>>>
>>>> Some info on my system:
>>>> Thinkpad x61s, 4GB of RAM, running debian 64bit (amd64).
>>>
>>> Maybe related, maybe not: You're using a Thinkpad with tuxonice, so are
>>> your special keys (Fn+..., ThinkVantage Button) functional after
>>> resuming?
>>>
>>
>> Nope, they are all gone for kernels 3.x. No rf switch, no fn-f12 (or any
>> other special key). acpi_listen is completely silent.
>>
>> Regards,
>> Ulrich
> 

Re: ACPI events dead after suspend / resume in 3.x

Hi Harald,

On 18.12.2011 15:12, Harald Judt wrote:
>> All acpi events are gone after a suspend / resume cycle under TuxOnIce.
>> This happens with the newest 3.1.5 branch (cloned Dec 18, 2011) from the
>> tuxonice git, but happened before for all versions I tried (3.0.9,
>> 3.0.11, 3.0.12).
>>
>> The problem seems to have occured somewhere between 2.6.39.4 and the 3.x
>> series. I am attaching my current config for 3.1.5 from the tuxonice git.
>>
>> Some info on my system:
>> Thinkpad x61s, 4GB of RAM, running debian 64bit (amd64).
> 
> Maybe related, maybe not: You're using a Thinkpad with tuxonice, so are
> your special keys (Fn+..., ThinkVantage Button) functional after resuming?
> 

Nope, they are all gone for kernels 3.x. No rf switch, no fn-f12 (or any
other special key). acpi_listen is completely silent.

Regards,
Ulrich

ACPI events dead after suspend / resume in 3.x

Hi,

I am having some trouble with the 3.x kernel series:

All acpi events are gone after a suspend / resume cycle under TuxOnIce.
This happens with the newest 3.1.5 branch (cloned Dec 18, 2011) from the
tuxonice git, but happened before for all versions I tried (3.0.9,
3.0.11, 3.0.12).

The problem seems to have occured somewhere between 2.6.39.4 and the 3.x
series. I am attaching my current config for 3.1.5 from the tuxonice git.

Some info on my system:
Thinkpad x61s, 4GB of RAM, running debian 64bit (amd64).

Maybe there is a weired interaction between suspend / resume and
thinkpad_acpi? I have found some indication of other regressions in the
3.1 series but I am not sure this is related. Here the versions of my
acpi userspace tools:
acpi                                     1.5-3
acpi-fakekey                             0.138-9
acpi-support                             0.138-9
acpi-support-base                        0.138-9
acpid                                    1:2.0.13-1
acpidump                                 20100513-3
acpitail                                 0.1-3
acpitool                                 0.5.1-2
libacpi0                                 0.2-4

May someone on the list can give me a hint what the problem might be or

3.1 branch

Hi all.

I have a 3.1 branch up now. I've only compile tested it at this stage,
but since there's little difference from the other branches I'm working
on, it should be fine to use.

Regards,

Nigel
--

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

Activity!

Hi all.

Some of you may have already noticed that I've pushed an update to
git.tuxonice.net. Please be weary of using it at the moment - I'm still
testing and debugging, and there are a couple of changes I want to look
at more closely. I hope to have more time to work on this tomorrow
night. Failing that, it should happen the day after because I'm back to
4 days a week at work now (glad of that - I can get other things done
again!).

Regards,

Nigel
--

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