Bugzilla – Bug 113629
Suspend2disk and suspend2ram unsuccessful on Fujitsu-Siemens E4010
Last modified: 2005-11-22 23:41:27 UTC
I tried s2d and s2r on Fujitsu-Siemens E4010. With both procedures the system does not wake up. s2r: screen stays black, no reaction on NumLock, only poweroff helps (tried with acpi_sleep=s3bios and s3_mode, no difference). s2d: upon rebooting after s2d the system boots, but graphical system does not come up and a few seconds later the system locks up.
Created attachment 47888 [details] hwinfo of Fujitsu-Siemens E4010
Created attachment 47892 [details] Logs from suspend2ram
Created attachment 47893 [details] logs from suspend2disk
this may be a duplicate of bug #113607 - try getting rid of intelfb before suspend to disk. Suspend to RAM is a different issue, please open a separate bug for this.
I am not sure if this a really a duplicate. I removed the intelfb, intel_agp and agpgart module files. After rebooting the system runs for about 1 second and then locks up hard. I will attach the logs.
Created attachment 48068 [details] new logs from suspend2disk without intelfb
the logs are useless in this case - the machine does not wake up, so it does not write anything. And if it did, it would be in /var/log/messages. Do i understand correctly that you don't get an oops, but the machine just hangs without any output? You could try the hardcore-debugging described on http://www.susewiki.org/index.php?title=ACPI_suspend to narrow it down.
hm, maybe the logs actually help: The sequence of events: - unloaded uhci_hcd - unloaded ipw2200 - suspend - resume - load ipw2200 <==== this is the last line in suspend2disk.log - load uhci_hcd so it looks like it crashed either after loading ipw2200 or uhci_hcd removing those modules before suspend manually might give a hint. Also, pulling out the airo_cs wlan pcmcia card before suspend might be a good idea.
Ok, tried that. See the log files. No ipw2200 and pcmcia, but uhci_hcd -> locks hard. Once again without uhci_hcd -> locks hard.
Created attachment 48252 [details] logs with uhci_hcd
Created attachment 48253 [details] without uhci_hcd
this is strange since at least powersave finished its restore_after_suspend_to_disk :-( What type of machine is this? SATA disk? Unusual filesystems? LVM? cryptofs? Does it work with init=/bin/bash as described in http://www.susewiki.org/index.php?title=ACPI_suspend (and can you access your disk afterwards)?
No need to test these. The system comes up indeed, but not longer than 3 seconds later it is locked hard. BTW: where to submit successful tests?
successful tests: - for suspend to disk, not necessary, i expect that to work - suspend to RAM: bug #103930 The system locking up after resume might well be a problem of being unable to read / write from disk, which might be caused by stuff like SATA disks, unusual filesystems, LVM etc. If it does not lock in init=/bin/bash it might also be a broken device driver.
Nothing of them inside. When I try to resume and have removed device drivers for network cards (ipw2200 airo_cs) and the in turn loaded drivers, the system also hangs. But the system runs for about 2 or 3 seconds and locks then!
ok. I am lost here. Pavel, any ideas?
Well, init=/bin/bash experiment would be nice...
Stefan, we need those init=/bin/bash experiments...
I understand, but ATM the notebook is not here... I expect it to be back in approx. two weeks...
It has been in NEEDINFO for way too long.