Toshiba Setellite U205-S5067 Suspend to RAM
Quoted 42 lines · Ross Patterson
Quoted 30 lines · Ross Patterson
Quoted 28 lines · Ross Patterson
Quoted 26 lines · Paulo J. S. Silva
I am not a kernel hacker, but I have tried to add some printk as suggested by Pavel (I haven't used udelay, I was not sure what it did (Is there a good explanation anywhere?). I added one printk to
state_storefunction inmain.cfile (inkernel/power/directory of course) to make sure that the process was starting, and many inenter_statefunction.What I could see, at first, is that something was taking long while the kernel was trying to disable the non-boot CPU. Here is the important log snippet (mine printk start with ****):
Quoted 11 lines
May 6 12:44:44 trinity kernel: [ 704.412000] ****Receiving request to power sa ve: mem May 6 12:44:44 trinity kernel: [ 704.412000] . May 6 12:44:44 trinity kernel: [ 704.412000] **** starting enter_state. May 6 12:44:44 trinity kernel: [ 704.412000] **** Preparing system for mem sle ep May 6 12:44:44 trinity kernel: [ 704.416000] Disabling non-boot CPUs ... May 6 12:44:44 trinity kernel: [ 704.552000] CPU 1 is now offline May 6 12:44:44 trinity kernel: [ 704.552000] SMP alternatives: switching to UP code May 6 12:55:00 trinity kernel: [ 704.552000] CPU1 is downYou see? Something took 10 minutes between the last two lines.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
I then thought that SMP was the problem. I have then disabled the second CPU during boot using "noapic nosmp" options. But I still get the same long wait before suspending. Moreover, something weird happens. There is no more delay in the sequence of messages related to suspend. But the whole sequence of messages, even the first sentence that says that the system is calling the function
state_store, is only written to the disk when the system is waked up and not before the suspend take place. The same thing happen if I disable the second CPU in the bios, instead of using "noapic nosmp". What should I try now?
Quoted 3 lines
I was wondering if anyone has any thoughts on what we might try from here? I think there are at least two willing, if not knowledgable :), testers here.
Well, I'm afraid no one has any idea. Otherwise, someone would have responded. ;-)
I've added more appropriate lists for your problem report to the CC list. Also, it probably would be a good idea to file a bug report at
http://bugzilla.kernel.org, in the ACPI->Power-Sleep-Wake category (please add my address to the bugzilla entry's CC list if you do that).
Greetings,
Rafael
Quoted 42 lines · Ross Patterson
Quoted 30 lines · Ross Patterson
Quoted 28 lines · Ross Patterson
Quoted 26 lines · Paulo J. S. Silva
I am not a kernel hacker, but I have tried to add some printk as suggested by Pavel (I haven't used udelay, I was not sure what it did (Is there a good explanation anywhere?). I added one printk to
state_storefunction inmain.cfile (inkernel/power/directory of course) to make sure that the process was starting, and many inenter_statefunction.What I could see, at first, is that something was taking long while the kernel was trying to disable the non-boot CPU. Here is the important log snippet (mine printk start with ****):
Quoted 11 lines
May 6 12:44:44 trinity kernel: [ 704.412000] ****Receiving request to power sa ve: mem May 6 12:44:44 trinity kernel: [ 704.412000] . May 6 12:44:44 trinity kernel: [ 704.412000] **** starting enter_state. May 6 12:44:44 trinity kernel: [ 704.412000] **** Preparing system for mem sle ep May 6 12:44:44 trinity kernel: [ 704.416000] Disabling non-boot CPUs ... May 6 12:44:44 trinity kernel: [ 704.552000] CPU 1 is now offline May 6 12:44:44 trinity kernel: [ 704.552000] SMP alternatives: switching to UP code May 6 12:55:00 trinity kernel: [ 704.552000] CPU1 is downYou see? Something took 10 minutes between the last two lines.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
I then thought that SMP was the problem. I have then disabled the second CPU during boot using "noapic nosmp" options. But I still get the same long wait before suspending. Moreover, something weird happens. There is no more delay in the sequence of messages related to suspend. But the whole sequence of messages, even the first sentence that says that the system is calling the function
state_store, is only written to the disk when the system is waked up and not before the suspend take place. The same thing happen if I disable the second CPU in the bios, instead of using "noapic nosmp". What should I try now?
Quoted 3 lines
I was wondering if anyone has any thoughts on what we might try from here? I think there are at least two willing, if not knowledgable :), testers here.
Well, I'm afraid no one has any idea. Otherwise, someone would have responded. ;-)
I've added more appropriate lists for your problem report to the CC list. Also, it probably would be a good idea to file a bug report at
http://bugzilla.kernel.org, in the ACPI->Power-Sleep-Wake category (please add my address to the bugzilla entry's CC list if you do that).
Greetings,
Rafael
Quoted 47 lines · Rafael J. Wysocki
Quoted 42 lines · Ross Patterson
Quoted 30 lines · Ross Patterson
Quoted 28 lines · Ross Patterson
Quoted 26 lines · Paulo J. S. Silva
I am not a kernel hacker, but I have tried to add some printk as suggested by Pavel (I haven't used udelay, I was not sure what it did (Is there a good explanation anywhere?). I added one printk to
state_storefunction inmain.cfile (inkernel/power/directory of course) to make sure that the process was starting, and many inenter_statefunction.What I could see, at first, is that something was taking long while the kernel was trying to disable the non-boot CPU. Here is the important log snippet (mine printk start with ****):
Quoted 11 lines
May 6 12:44:44 trinity kernel: [ 704.412000] ****Receiving request to power sa ve: mem May 6 12:44:44 trinity kernel: [ 704.412000] . May 6 12:44:44 trinity kernel: [ 704.412000] **** starting enter_state. May 6 12:44:44 trinity kernel: [ 704.412000] **** Preparing system for mem sle ep May 6 12:44:44 trinity kernel: [ 704.416000] Disabling non-boot CPUs ... May 6 12:44:44 trinity kernel: [ 704.552000] CPU 1 is now offline May 6 12:44:44 trinity kernel: [ 704.552000] SMP alternatives: switching to UP code May 6 12:55:00 trinity kernel: [ 704.552000] CPU1 is downYou see? Something took 10 minutes between the last two lines.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
I then thought that SMP was the problem. I have then disabled the second CPU during boot using "noapic nosmp" options. But I still get the same long wait before suspending. Moreover, something weird happens. There is no more delay in the sequence of messages related to suspend. But the whole sequence of messages, even the first sentence that says that the system is calling the function
state_store, is only written to the disk when the system is waked up and not before the suspend take place. The same thing happen if I disable the second CPU in the bios, instead of using "noapic nosmp". What should I try now?Quoted 3 lines
I was wondering if anyone has any thoughts on what we might try from here? I think there are at least two willing, if not knowledgable :), testers here.
Quoted 6 lines
Well, I'm afraid no one has any idea. Otherwise, someone would have responded. ;-)
I've added more appropriate lists for your problem report to the CC list. Also, it probably would be a good idea to file a bug report at
http://bugzilla.kernel.org, in the ACPI->Power-Sleep-Wake category (please add my address to the bugzilla entry's CC list if you do that).
http://bugzilla.kernel.org/show_bug.cgi?id=8456
Thanks!
Ross
-------------------------------------------------------------------------
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/
Quoted 47 lines · Rafael J. Wysocki
Quoted 42 lines · Ross Patterson
Quoted 30 lines · Ross Patterson
Quoted 28 lines · Ross Patterson
Quoted 26 lines · Paulo J. S. Silva
I am not a kernel hacker, but I have tried to add some printk as suggested by Pavel (I haven't used udelay, I was not sure what it did (Is there a good explanation anywhere?). I added one printk to
state_storefunction inmain.cfile (inkernel/power/directory of course) to make sure that the process was starting, and many inenter_statefunction.What I could see, at first, is that something was taking long while the kernel was trying to disable the non-boot CPU. Here is the important log snippet (mine printk start with ****):
Quoted 11 lines
May 6 12:44:44 trinity kernel: [ 704.412000] ****Receiving request to power sa ve: mem May 6 12:44:44 trinity kernel: [ 704.412000] . May 6 12:44:44 trinity kernel: [ 704.412000] **** starting enter_state. May 6 12:44:44 trinity kernel: [ 704.412000] **** Preparing system for mem sle ep May 6 12:44:44 trinity kernel: [ 704.416000] Disabling non-boot CPUs ... May 6 12:44:44 trinity kernel: [ 704.552000] CPU 1 is now offline May 6 12:44:44 trinity kernel: [ 704.552000] SMP alternatives: switching to UP code May 6 12:55:00 trinity kernel: [ 704.552000] CPU1 is downYou see? Something took 10 minutes between the last two lines.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
I then thought that SMP was the problem. I have then disabled the second CPU during boot using "noapic nosmp" options. But I still get the same long wait before suspending. Moreover, something weird happens. There is no more delay in the sequence of messages related to suspend. But the whole sequence of messages, even the first sentence that says that the system is calling the function
state_store, is only written to the disk when the system is waked up and not before the suspend take place. The same thing happen if I disable the second CPU in the bios, instead of using "noapic nosmp". What should I try now?Quoted 3 lines
I was wondering if anyone has any thoughts on what we might try from here? I think there are at least two willing, if not knowledgable :), testers here.
Quoted 6 lines
Well, I'm afraid no one has any idea. Otherwise, someone would have responded. ;-)
I've added more appropriate lists for your problem report to the CC list. Also, it probably would be a good idea to file a bug report at
http://bugzilla.kernel.org, in the ACPI->Power-Sleep-Wake category (please add my address to the bugzilla entry's CC list if you do that).
http://bugzilla.kernel.org/show_bug.cgi?id=8456
Thanks!
Ross