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

Nigel Cunningham wrote:
> Sorry for the delay in replying.
>
> On 31/12/11 08:12, Woody Suwalski wrote:
>> 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?
> Have you tried the old standard method of building as much as possible
> as modules, then doing a binary search in unloading modules and stopping
> services until you can say 'If I unload X, I can hibernate and resume
> okay'? (Where X may consist of more than one module).
>
> Regards,
>
> Nigel
No I have not. For the last 2 years I have been building kernels with 
AGP and video built-in.
OTOH your suspicion is probably correct, TOI  seems to work fine on 
EeePC with GMA500 video.
However starting in single mode with no kernel mode setting should be as 
safe as conceptually possible - and kernel itself loads fine - I can see 
that since I am starting TOI from the ramdisk.
So sooner or later it will need to be debugged - just I do not know how 
to do it?

There is no real serial on the boxes, but maybe ttyUSB will do? I will 
try to create a smarter ramdisk  and channel dmesg to ttyUSB... Just 
need to find another machine with a real serial port to receive the data ;-)

Any hints what to look for? Which parts of TOI/kernel sprinkle with more 
printk's? Any suggestions how to slow it down / flush messages / force 
some maximum-comatibilty mode? Maybe it is some weird timing problem?

Thanks, Woody