Resume no works after suspend

Bug #154342 reported by unai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal-info (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi.

This is my first bug report and i can't speak good english, therefore i hope i do it fine, and the report could be useful. Sorry if not.

I installed ubuntu gutsy. I can suspend but, when i try to resume, the computer freezes. With festy and edgy versions i didn't found problems.

Then i follow the steps from: https://wiki.ubuntu.com/DebuggingKernelSuspend.

Now i have dmesg.txt , lspci-vvnn.log and uname-a.log

Revision history for this message
unai (unai) wrote :
Revision history for this message
unai (unai) wrote :
Revision history for this message
unai (unai) wrote :
Revision history for this message
unai (unai) wrote :

I suppose that's the important info you need:

[ 10.848591] Magic number: 0:432:626
[ 10.848594] hash matches /build/buildd/linux-source-2.6.22-2.6.22/drivers/base/power/resume.c:28
[ 10.848792] hash matches device 0000:00:1b.0

Revision history for this message
Guiodic (Guido Iodice) (guido-iodice) wrote :

I have the same problem and the same hash matches that is the sound card (intel) on mi acer notebook.
So, if I unload the sound modules, resume works but screen in also black. But if I give a commad (ie shutdown -r now) it works.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Need dmidecode and lshal output separately as attachments.

Changed in acpi:
status: New → Incomplete
Revision history for this message
unai (unai) wrote :
Revision history for this message
unai (unai) wrote :
Revision history for this message
unai (unai) wrote :

Now i'm using same computer, but different OS (kubuntu 8.10). I hope dmidecode and lshal are still usefull.

Revision history for this message
Martin Pitt (pitti) wrote :

Seems hal-info already knows about your computer:
  power_management.quirk.s3_bios = true (bool)
  power_management.quirk.s3_mode = true (bool)

so apparently this isn't sufficient. Maybe you can play around with the other quirks and see whether one combination makes it work? http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-debug.html provides excellent guide for this. Thanks!

Revision history for this message
Martin Pitt (pitti) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hal-info:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.