I have also tried the LFDk CD and my machine also suspended right away.

I have been trying to hunt this bug down, adding many printk to my
kernel to see where the time is being spend.

Up to now I can see that the system I get the following:

enter_state in kernel/power/main.c is called that calls
suspend_enter in kernel/power/main.c is called that calls
device_power_up in drivers/base/power/resume that calls
sysdev_resume in drivers/base/sys.c that start calling

__sysdev_resume in the same file to resume type 'cpu' and it works OK,
but when it is called to resume type 'timer' (actually the timer0) it
seems to take too long.

See the related portion of my messages.log below

Is this the expected behavior? Should I try to debug deeper in the
calling sequence?

Best,

Paulo

--- extract of my messages.log file ---


May 10 16:25:00 trinity kernel: [   85.124000] **** Calling
device_power_up.
May 10 16:25:00 trinity kernel: [   85.124000] **** In device_power_up.
May 10 16:25:00 trinity kernel: [   85.124000] **** Calling
sysdev_resume.
May 10 16:25:00 trinity kernel: [   85.124000] *** Entering sysdev
resume
May 10 16:25:00 trinity kernel: [   85.124000] **** Resuming type 'cpu':
May 10 16:25:00 trinity kernel: [   85.124000] **** cpu0
May 10 16:25:00 trinity kernel: [   85.124000] **** In __sysdev_resume,
calling class specific resume.
May 10 16:25:00 trinity kernel: [   85.124000] ****  Done
May 10 16:25:00 trinity kernel: [   85.124000] ****  Aux:
May 10 16:25:00 trinity kernel: [   85.124000] ****  Done
May 10 16:25:00 trinity kernel: [   85.124000] ****Done cpu0
May 10 16:25:00 trinity kernel: [   85.124000] **** cpu1
May 10 16:25:00 trinity kernel: [   85.124000] **** In __sysdev_resume,
calling class specific resume.
May 10 16:25:00 trinity kernel: [   85.124000] ****  Done
May 10 16:25:00 trinity kernel: [   85.124000] ****  Aux:
May 10 16:25:00 trinity kernel: [   85.124000] ****  Done
May 10 16:25:00 trinity kernel: [   85.124000] ****Done cpu1
May 10 16:25:00 trinity kernel: [   85.124000] **** Resuming type
'timer':
May 10 16:25:00 trinity kernel: [   85.124000] **** timer0
May 10 16:25:00 trinity kernel: [   85.124000] **** In __sysdev_resume,
calling class specific resume.
May 10 16:25:00 trinity kernel: [ 9002.124000] ****  Done
May 10 16:25:00 trinity kernel: [ 9002.124000] ****Done timer0
May 10 16:25:00 trinity kernel: [ 9002.124000] **** Resuming type
'i8259':
May 10 16:25:00 trinity kernel: [ 9002.124000] **** i82590
May 10 16:25:00 trinity kernel: [ 9002.124000] **** In __sysdev_resume,
calling class specific resume.
May 10 16:25:00 trinity kernel: [ 9002.124000] ****  Done






-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel

Reply via email to