Ubuntu
linux package

suspend hangs forever

Bug #715865 reported by Teo on 2011-02-09

This bug report is a duplicate of: Bug #670685: suspend usually fails. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Sometimes, when I suspend (either by selecting "suspend" from the panel menu or by closing the lid of my laptop), the system hangs forever and never finishes to suspend, nor does it let me resume in any way. I am left with the only option to force power down by holding the power button.

Happens only from time to time.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-28-generic 2.6.32-28.55
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: teo 1579 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 22'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,10430000,00100001 HDA:10573055,10431316,00100700'
   Controls : 19
   Simple ctrls : 13
Date: Wed Feb 9 17:09:06 2011
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.3
SourcePackage: linux
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Tags:

Revision history for this message

Teo (teo1978) wrote on 2011-02-09:

AlsaDevices.txt Edit (644 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (397 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (274 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (52.8 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (8.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (145 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (598 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (17.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (717 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (603 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.4 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (124.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (247.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (124.8 KiB, text/plain; charset="utf-8")

Brian Murray (brian-murray) on 2011-03-01

tags:

added: regression-release
removed: regression-potential

Brad Figg (brad-figg) on 2011-04-07

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Teo (teo1978) wrote on 2011-04-22:

I'm confused. There are a lot of issues describing the same problem, but when I commented on one of them, I was told that I had to open a new bug, because kernel issues are specific to every hardware combination and the policy is that every single person experimenting the problem should open a new bug - that's what i was told. So I opened a new bug and now it is marked as duplicate...

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #670685 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package