Bug 28132 - Suspend does not work anymore
Suspend does not work anymore
Status: CLOSED CODE_FIX
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend
All Linux
: P1 high
Assigned To: power-management_other
:
Depends on:
Blocks: 7216
  Show dependency treegraph
 
Reported: 2011-02-03 17:20 UTC by remi
Modified: 2011-07-09 09:47 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.32-25+
Tree: Mainline
Regression: Yes


Attachments

Description remi 2011-02-03 17:20:12 UTC
Hello,

Starting from linux kernel version 2.6.32-25, I cannot put my laptop in sleep mode. In version 2.6.32-24, it worked.
I am using Ubuntu 10.04 LTS, here are my system details:

~$ sudo lshw
    description: Notebook
    product: A6JC
    vendor: ASUSTeK Computer Inc.
    version: 1.0

Could you please fix this bug ?

Thanks !

Rémi
Comment 1 Rafael J. Wysocki 2011-02-03 18:48:51 UTC
First, please explain what _exactly_ you mean by "cannot put in sleep mode"?

Does it crash during suspend or during resume?  Or does it suspend, but fails
to resume?

We rather won't be able to fix the problem without your assistance.
Comment 2 remi 2011-02-03 21:14:00 UTC
Sorry, I forgot to mention the wrong behavior.

When I put my PC in sleep mode, it goes into sleep mode for a very short moment (less than one second), but it resumes just after that. There is no log or anything in the console.
It seems to me that some kind of event is triggered that makes the PC leave sleep mode.

Thanks.
Comment 3 Rafael J. Wysocki 2011-02-03 21:58:35 UTC
Do you see this problem in a kernel that's based on 2.6.32?
Comment 4 remi 2011-02-04 19:28:59 UTC
Yes, this problem appears also on 2.6.32
Comment 5 remi 2011-03-31 18:05:00 UTC
Is there any update on this bug?

Thanks !
Rémi
Comment 6 remi 2011-07-05 20:34:05 UTC
Bug still occurs with kernel 2.6.32.32.38.
Comment 7 remi 2011-07-09 08:32:32 UTC
Problem does not happen anymore with kernel version 2.6.32.33.39.
Comment 8 Rafael J. Wysocki 2011-07-09 09:47:53 UTC
Good, thanks.  Closing.

Note You need to log in before you can comment on or make changes to this bug.