suspend to RAM does not work anymore after upgrade to Maverick Meerkat 10.10

Bug #664161 reported by Laurent Martin-Borret
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading from Ubuntu 10.04 to 10.10, suspend to RAM does not work anymore (was working fine with 10.04).
When going to sleep state, screen becomes dark (with blinking cursor in up left corner), but the system never goes to power-off.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.34
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lmartinb 1770 F.... pulseaudio
 /dev/snd/pcmC0D0p: lmartinb 1770 F...m pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7ff8000 irq 49'
   Mixer name : 'Nvidia MCP77/78 HDMI'
   Components : 'HDA:10ec0663,10431893,00100001 HDA:10de0003,10de0101,00100000'
   Controls : 21
   Simple ctrls : 10
CheckboxSubmission: 7db099b98e09bff1316dc37221c33b99
CheckboxSystem: 8a3837bb37f8ad6b84de837b38edb33e
Date: Wed Oct 20 22:53:22 2010
HibernationDevice: RESUME=UUID=b727cb1f-34aa-4217-bc3a-0ca313b458ce
MachineType: ASUSTeK Computer Inc. M50Vc
ProcCmdLine: root=UUID=db9087dd-ec0b-489d-9ec6-dc7d9ed44911 ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 10/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M50Vc
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.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vc:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M50Vc
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Laurent Martin-Borret (laurent-martin-borret) wrote :
Revision history for this message
Laurent Martin-Borret (laurent-martin-borret) wrote :

After updating to "initscripts 2.87dsf-4ubuntu19", it seemed to have fixed the issue.
Can someone with the right privilege close it ?

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Laurent Martin-Borret, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → 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.