I saw the article in Suspend to disk - openSUSE and I decided to test s2disk on my VAIO VGN-AR41L (laptop) using ext4 system (which supports journaling). I used the button of the KDE4 to initiate the process of suspend to disk. The process of storing the image and shutdown the computer worked. But the reverse process didn’t work. I want to produce a log in order to show it to some expert here in the forums in order to find a solution. I also saw in the article that there is a workaround for the journaled systems. Instead of doing this can I switch off journaling on ext4 without loss of data? And if yes, how can this be done?
On 12/09/2009 01:46 PM, Leonardo12 wrote:
>
> Hello,
>
> I saw the article in ‘Suspend to disk - openSUSE’
> (http://en.opensuse.org/S2disk) and I decided to test s2disk on my VAIO
> VGN-AR41L (laptop) using ext4 system (which supports journaling). I used
> the button of the KDE4 to initiate the process of suspend to disk. The
> process of storing the image and shutdown the computer worked. But the
> reverse process didn’t work. I want to produce a log in order to show it
> to some expert here in the forums in order to find a solution. I also
> saw in the article that there is a workaround for the journaled systems.
> Instead of doing this can I switch off journaling on ext4 without loss
> of data? And if yes, how can this be done?
Suspending to disk from the “Leave” menu of KDE4 works for me on 11.2
on an ext4 file system.
The problems with journaling in that article is with reiserfs file
systems. GRUB has problems with them. AFAIK, there is not a problem
with ext4. Certainly, I see no journal replay delay.
Is your swap partition big enough? You need enough to store a
compressed image of RAM. A file half the size of RAM should be OK. I’m
using 2.1 GB swap for 3 GB RAM.
When you try to restart, you should see it trying to reload RAM. Do
you see that display? When it fails, what do you see? I do not think
anything can be logged until the OS gets restarted.
I am using 2.01 GB swap for 2GB RAM. In the very start I see a message that 100% image loaded but after that the screen goes very fast and eventually the all process freezes and the screen has many messages that I cannot describe all of them here. None of these indicates a failure except one that says “usb root hub lost power or was reset” All the other messages conclude with a “done” so I think they don’t indicate failure. Also my keyboard doesn’t respond. The buttons that control the LED(CAPS LOCK,SCRL LOCK NUM LOCK) do not light the LEDs. Neither can change virtual console. So I have to power off my laptop by disconnecting the battery and the AC.
On 12/09/2009 03:26 PM, Leonardo12 wrote:
>
> lwfinger;2084991 Wrote:
>> On 12/09/2009 01:46 PM, Leonardo12 wrote:
>>>
>>> Hello,
>>>
>>> I saw the article in ‘Suspend to disk - openSUSE’
>>> (‘Suspend to disk - openSUSE’ (http://en.opensuse.org/S2disk)) and I
>> decided to test s2disk on my VAIO
>>> VGN-AR41L (laptop) using ext4 system (which supports journaling). I
>> used
>>> the button of the KDE4 to initiate the process of suspend to disk.
>> The
>>> process of storing the image and shutdown the computer worked. But
>> the
>>> reverse process didn’t work. I want to produce a log in order to show
>> it
>>> to some expert here in the forums in order to find a solution. I
>> also
>>> saw in the article that there is a workaround for the journaled
>> systems.
>>> Instead of doing this can I switch off journaling on ext4 without
>> loss
>>> of data? And if yes, how can this be done?
>>
>> Suspending to disk from the “Leave” menu of KDE4 works for me on 11.2
>> on an ext4 file system.
>>
>> The problems with journaling in that article is with reiserfs file
>> systems. GRUB has problems with them. AFAIK, there is not a problem
>> with ext4. Certainly, I see no journal replay delay.
>>
>> Is your swap partition big enough? You need enough to store a
>> compressed image of RAM. A file half the size of RAM should be OK. I’m
>> using 2.1 GB swap for 3 GB RAM.
>>
>> When you try to restart, you should see it trying to reload RAM. Do
>> you see that display? When it fails, what do you see? I do not think
>> anything can be logged until the OS gets restarted.
>
> I am using 2.01 GB swap for 2GB RAM. In the very start I see a message
> that 100% image loaded but after that the screen goes very fast and
> eventually the all process freezes and the screen has many messages that
> I cannot describe all of them here. None of these indicates a failure
> except one that says “usb root hub lost power or was reset” All the
> other messages conclude with a “done” so I think they don’t indicate
> failure. Also my keyboard doesn’t respond. The buttons that control the
> LED(CAPS LOCK,SCRL LOCK NUM LOCK) do not light the LEDs. Neither can
> change virtual console. So I have to power off my laptop by
> disconnecting the battery and the AC.
The log messages should be in /var/log/messages. The USB hub messages
are normal. I get them too. When shutting down, do you see the penguin
going to sleep? When I use the standard kernel, I also see him waking
up, then the KDE GUI comes back on.
No, I don’t see any penguin. I see only the chameleon and a progress bar underneath.
Now the logs:
Another message is that I take an ACPI Exception AE_TIME
and ACPI Error Method parse/execute failed.
the log from /var/log/pm-suspend: /var/log/pm-suspend (mylogssite)
the log from /var/log/messages: /var/log/messages (mylogssite)