Bug 113141

Created attachment 47660 [details]
Powersave logs

Created attachment 47661 [details]
Hwinfo log

forwarding to pavel 

I really need to know kernel messages from suspend attempt. Does it poweroff
itself at the end of suspend?

Has suspend ever worked for you?

> I really need to know kernel messages from suspend attempt.

Which logs exactly do you need? I'd be happy to provide you with everything
needed to fix this bug.

> Does it poweroff itself at the end of suspend?

Yes it does. And I just saw when rebooting after suspend the filesystems are not
clean and ReiserFS seems to fix plenty of errors in the filesystem.

> Has suspend ever worked for you?

I tried it with another Linux distribution once but it never worked. It only
works on Windows XP.

I'd like to see messages that scroll on your screen just before poweroff.

Also please take a look at Doc*/power/swsusp.txt in kernel sources. Make sure
you have just one swap partition, etc.

Unclean filesystems are normal after failed suspend; remount them read-only
before attempt to be sure. Also ext2 is more robust against this kind of abuse.

> I'd like to see messages that scroll on your screen just before poweroff.

I'm sorry but I have no idea how I should log these to a file before poweroff.
But it seems that the error is fixed: While updating from Beta2 the kernel
parameters weren't updated.
I added resume=/dev/hda3 to /boot/grub/menu.lst and now it resumes to an X
login. The USB mouse needs some time to work but I guess that's another bug.

Thanks for helping. I think the resume=/dev/hdx should be added to the kernel
parameters automatically to avoid such errors.

Not sure why it works... it should resume from initrd. Anyway if it works with
resume=, it is probably not kernel problem.

Pavel: Shoud resume from disk work without a resume=/dev/hdaX work?

I've updated my workstation at home to Beta3 and no longer have resume=/dev/hda5
in /boot/grub/menu.lst.  But that have been there as I can check from the
menu.lst.old file.

Created attachment 47886 [details]
grub config modified by Beta 4 update

Created attachment 47887 [details]
Log while calling powersave -U

Sven: To capture the output of powersave -U I've configured a serial console in
menu.lst

Pavel: The output gave the hint to use resume= and if I set it again resume
works well. :)

Lars: Thanks! 

My powersave -U log looked almost identical. Seems the resume= is definitely  
needed.

It can probably not work without resume= parameter because the initrd must setup
the resume device and can only know this from the resume parameter.

This is not a kernel/initrd bug but a bug for whoever hosed the update or forgot
to add the resume= parameter during install

Please provide YaST2 logs from installation so we can check why the
resume= parameter was missing in the first place, see:
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST

Created attachment 48046 [details]
YaST2 logs

Attaching the output of save_y2logs

Had the same problems with missing the resume=/dev/*** entry in the command line.
It looks like the two machines I updated from Beta2 to Beta3 are missing the
resume line. A fresh installation done afterwards with Beta3 was OK...

Jiri, is this yours? Adding resume=... parameter? See comment #13 and comment #16

The problem occurred in Beta3 only durign updates, fresh installatino should 
have been fine. It has already been fixed in Beta4. 

*** This bug has been marked as a duplicate of 112794 ***