laptop does not suspend after kernel update

Bug #621834 reported by Thomas Mayer
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a Dell Inspiron 6000 with Intel Centrino (Pentium-M), 32bit. ATI X300 graphics. No fglrx drivers.

I updated my system from karmic to lucid. Using jaunty, it was very very seldom that suspend to ram did not work. Same behavior with lucid. System was updated frequently.

Since I installed a kernel update from 2.6.32-23 to 2.6.32-24 in the last days, I can't suspend to ram reproducibly. The system halts before it sleeps or is switched off. I have to hard reset the system then. After rebooting, all network connections are switched off and I have to reenable them using NetworkManager.

Using 2.6.32-23, I also can't suspend to ram any more. A few days ago, this worked fine in most cases. However sometimes I had the same behavior as now (about one in 10 times it did not suspend).

When I reboot my system using kernel 2.6.32-22, suspend to ram work fine. Reproducibly. Only very very seldom it did not work with same behavior (system halted and network connections had to be enabled again).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.41
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 2376 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with STAC9752,53 at irq 16'
   Mixer name : 'SigmaTel STAC9752,53'
   Components : 'AC97a:83847652'
   Controls : 30
   Simple ctrls : 20
CheckboxSubmission: 8f12e98536291f59719792d89958b124
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sat Aug 21 17:52:08 2010
HibernationDevice: RESUME=UUID=1afd8712-66c3-44d4-9a1f-36d4761111cb
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Inspiron 6000
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=b29172d6-f392-4749-8397-c5ccbddcb980 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 09/28/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/28/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 6000
dmi.sys.vendor: Dell Inc.

Revision history for this message
Thomas Mayer (thomas303) wrote :
Revision history for this message
Thomas Mayer (thomas303) wrote :

I successfully tested suspend/hibernate using the current mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

No problems there. Kernel version is:

Linux i306 2.6.36-999-generic #201008190908 SMP Thu Aug 19 10:19:31 UTC 2010 i686 GNU/Linux

Revision history for this message
Kevin Smith (thirdwiggin) wrote :

I have the same problem on 10.04 with my Inspiron 6000. Suspend-to-RAM worked fine until recently, and now fails every time. I require a hard reset, and networking is disabled on reboot. My kernel is 2.6.32-25.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
summary: - laptop does not suspend/hibernate after kernel update
+ laptop does not suspend after kernel update
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Thomas Mayer, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Thomas Mayer (thomas303) wrote :

Thanks for this first activity in nearly 2 years.

I think s2ram is too important to ignore such bug reports that long and wait until they are obsolete (even on a still supported LTS release). Having to hard reset the laptop after s2ram can be considered as bad as a kernel crash.

I will see if I still can reproduce the bug on my old laptop (which has been replaced by a new one in between).

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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