Suspend Take 10s

[nax]

Hello, since I tryed upgrade (because wpa support) suspend is very slow. I have tryed format and unpack my root fylesystem (sd card) but it doesn't help.

Problem is that after pressing Cancel for 1s (normal suspend call - SL5500 don't have on/off button) my sl5500 freeze for about 10s ant after that turn off display and go to sleep.

In dmesg I have found this:

Code: [Select]

monitor_hotplug: agent: usbd interface: monitor action: suspend
usbdmonitor: warning - hotplug script timed out
monitor_pm_event: suspend finished (rc=0)
Interesting is also this:

Code: [Select]

# find / -name hotplug
...
find: /etc/hostplug: Input/output error
...
What does this mean?

[x86Daddy]

I get the same behavior with my setup.  I thought it was just a consequence of using altboot with my root on a loopback file on SD.  When I do a normal boot from the ROM, it suspends quickly and painlessly.

I get the same result with Hentges 3.5.4.1 using a loopback file on my SD card as well.

Edit: Is there any system file / log message / command output anyone could use from me to help fix this?  Or is it just a consequence of loopback files?  Thanks!

[x86Daddy]

Another observation: it does this whether I use the Cancel / On-Off button or Suspend from the menu.

[CoreDump]

Hello, since I tryed upgrade (because wpa support) suspend is very slow. I have tryed format and unpack my root fylesystem (sd card) but it doesn't help.

Problem is that after pressing Cancel for 1s (normal suspend call - SL5500 don't have on/off button) my sl5500 freeze for about 10s ant after that turn off display and go to sleep.

In dmesg I have found this:

Code: [Select]

monitor_hotplug: agent: usbd interface: monitor action: suspend
usbdmonitor: warning - hotplug script timed out
monitor_pm_event: suspend finished (rc=0)
Interesting is also this:

Code: [Select]

# find / -name hotplug
...
find: /etc/hostplug: Input/output error
...
What does this mean?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123775\"][{POST_SNAPBACK}][/a][/div]

I/O erros usually indicate a damaged FS or a card that "does not like ext2".

[guitara]

I have the same problem.. Often, it just won't resume at all. Any fixes?