On Tuesday, 29 of January 2008, Max Whitney wrote: > I've been trying to use Uswsusp to suspend to disk on my Asus EEE PC using an > SD card as the resume device. The suspend program appears to run successfully > with no errors, but the resume program doesn't do anything besides print the > message that says it's running. On further examination, the Uswsusp signature > is not on the disk after suspending and rebooting. > > The problem seems to be that the two calls to fsync in the write_image() function > in suspend.c fail, leaving errno set to 5 and perror reporting "Input/output error". > > I'm not sure if this is a Uswsusp problem or just my configuration, but I'm > not sure what to try now. Is suspending to a removable device (I think it's > a USB device internally) just a bad idea? Any advice, or ideas on how to > continue debugging? Actually, this is a kernel problem. In short, the kernel disconnects removable storage devices before putting them into low power states and this cannot be fixed totally cleanly, AFAICS. If this is a USB device, you may try to set CONFIG_USB_PERSIST in the kernel config (this is not a safe option, though). Thanks, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
