Complete system freeze usually after suspend/resume

Bug #684164 reported by Clayton Dillard
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This usually occurs after a suspend/resume. I'm running Ubuntu 10.10 on an HP Elitebook 8530w with Intel wireless and Nvidia Quadro with Nvidia drivers.

Steps to reproduce:
1. Boot up the computer
2. Suspend
3. Resume
After some period of time the computer will completely freeze and no combination of keystrokes will recover it. The fan is running as fast as it can and high heat is noticed. The CPU seems maxed out but no way to really tell. If you have an SSH session open from another computer to the Ubuntu 10.10 computer that is locked there is no longer any interaction so you cannot tail the logs. The only way to recover is to hold down the power button and turn off the computer. This did not happen on Ubuntu 10.04.

Often after this happens and I power off the computer, turning it back on results in another freeze minutes after logging in. I can turn it back off and turn it on and usually work for hours without the freeze until the next time I suspend/resume.

I've tried plugging and unplugging the power cord repeatedly but this does not seem to cause the freeze.

This is a painful bug for obvious reasons for those of us who use Ubuntu as our primary business OS.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-generic 2.6.35.23.25
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cdillard 1923 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 47'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30e7,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 18
   Simple ctrls : 11
Date: Thu Dec 2 08:27:01 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/sda5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: Hewlett-Packard HP EliteBook 8530w
PccardctlIdent:
 Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=677597b2-db17-475e-b673-7657c738465b ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 06/08/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.12
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.27
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Clayton Dillard (claytondillard) wrote :
Brad Figg (brad-figg)
tags: added: acpi
Revision history for this message
Clayton Dillard (claytondillard) wrote :

Some on Ubuntu Forums suggest that they've downgraded pm-utils to the Lucid version and that this has resolved the freeze issue.

Revision history for this message
Clayton Dillard (claytondillard) wrote :

Just confirmed that downgrading pm-utils does NOT solve this issue. A couple of suspend/resume attempts and a disconnect/reconnect of the power cord causes another freeze.

Revision history for this message
Clayton Dillard (claytondillard) wrote :

When I ran the Update Manager to upgrade the Lucid version of pm-utils to the Maverick version that I had previously downgraded my computer froze during the install/configure stage. This hints that the issue with the freezing is related to ACPI and power management.

tags: added: kernel-series-unknown
Revision history for this message
bealer (robertbeal) wrote :

Removing pm-utils seems to solve the issue for me, but means I have very little power management.

Revision history for this message
Choong Wei Tjeng (choong) wrote :

This freeze occurs when wlan0 enters powersaving mode for me (RaLink RT2561/RT61 with rt61pci driver). Quick workaround: touch /etc/pm/power.d/wireless. This will prevent /usr/lib/pm-utils/power.d/wireless from executing. Downside is you will no longer be able to run your wireless card in powersaving mode.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Probably the same bug here on the same hardware (Elitebook 8530w). Sometimes, but less often, the freezes also occur without suspend / resume. I got the impression that attached USB devices (harddrives etc) increase the "freeze frequency" and that most freezes happen while I'm using firefox. This problem appeared with the upgrade to ubuntu 10.10 for me.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

I tried now Choong's suggestion with touch /etc/pm/power.d/wireless and will report the results.

Revision history for this message
Springnuts (simon-springnuts-orangehome) wrote :

Happens for me - full reproducible as follows.

Start Ubuntu 10.10 on battery, or on mains then unplug mains.

Attempt to log on to wireless network.

Machine freezes as the wlan card connects.

I am using the temporary work around from http://www.uluga.ubuntuforums.org/showthread.php?p=10327529 : "sudo iwconfig wlan0 power off" before trying to connect to wlan. That thread too is pointing to problems with pm-utils 1.4.

Regards,

Springnuts.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

touch /etc/pm/power.d/wireless

did not solve the problem for me. I will now switch to cable LAN at home and report back, whether wifi usage affects the problem. Well, it is so annyoing, I'm thinking about switching away from Ubuntu after years. :(

Revision history for this message
jmrk (joergen-kornfeld) wrote :

@Springnuts: This does not reproduce it for me!

Revision history for this message
Springnuts (simon-springnuts-orangehome) wrote : Re: [Bug 684164] Re: Complete system freeze usually after suspend/resume
Download full text (4.7 KiB)

Not sure if this is the same bug - to reproduce mine:

1) Boot from cold, not connected physically to network.
2) Disconnect from mains power
3) Enter keyring password (so keyring can connect to wireless)
4) System freezes

 Regards,

Springnuts
+ + + + + + + + + +

The Revd Simon Springett
Tel: 01752 248341 (home)
http://springnuts.org/

----- Original Message -----
From: "jmrk" <email address hidden>
To: <email address hidden>
Sent: Monday, January 17, 2011 4:31 PM
Subject: [Bug 684164] Re: Complete system freeze usually after
suspend/resume

@Springnuts: This does not reproduce it for me!

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/684164

Title:
  Complete system freeze usually after suspend/resume

Status in “linux” package in Ubuntu:
  New

Bug description:
  This usually occurs after a suspend/resume. I'm running Ubuntu 10.10
  on an HP Elitebook 8530w with Intel wireless and Nvidia Quadro with
  Nvidia drivers.

  Steps to reproduce:
  1. Boot up the computer
  2. Suspend
  3. Resume
  After some period of time the computer will completely freeze and no
combination of keystrokes will recover it. The fan is running as fast as it
can and high heat is noticed. The CPU seems maxed out but no way to really
tell. If you have an SSH session open from another computer to the Ubuntu
10.10 computer that is locked there is no longer any interaction so you
cannot tail the logs. The only way to recover is to hold down the power
button and turn off the computer. This did not happen on Ubuntu 10.04.

  Often after this happens and I power off the computer, turning it back
  on results in another freeze minutes after logging in. I can turn it
  back off and turn it on and usually work for hours without the freeze
  until the next time I suspend/resume.

  I've tried plugging and unplugging the power cord repeatedly but this
  does not seem to cause the freeze.

  This is a painful bug for obvious reasons for those of us who use
  Ubuntu as our primary business OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-generic 2.6.35.23.25
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
  Uname: Linux 2.6.35-23-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
   **** List of PLAYBACK Hardware Devices ****
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
   **** List of CAPTURE Hardware Devices ****
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: cdillard 1923 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 47'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e7,00100400
HDA:11c...

Read more...

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Turning wifi off, does not solve the problem for me! I disabled wifi via the hardware switch at the 8530w. It makes this thingy very mysterious ;).

Revision history for this message
Clayton Dillard (claytondillard) wrote :

I followed the suggestion in #50 above with no luck. I upgraded to the pm-utils in the Natty release several days ago and have not had a problem since.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Hi Clayton,

thanks for the hint. How did you do the pm-utils upgrade? Is there a ppa? I don't wanna jump to the whole natty yet...
Thanks!

Revision history for this message
Clayton Dillard (claytondillard) wrote :

jmrk -
It's not a fix. I have now had system freezes a few times since my last post. I am at a loss and wish that the Ubuntu team would hurry up and fix this.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Alright, testing now the natty mainline kernel RC6 and we will see...

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Ok.. I don't want to be too optimistic, but no crash with the new kernel yet.. It also runs already pretty smoothly on the 8530w and I could not see other problems popping up.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

Very promising! No more crash since I updated to RC7 and I used suspend a lot!

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

Ok, not so promising as I thought. The freeze frequency went down (meanwhile, I switched to the final release of the mainline kernel, but I don't think that this makes a difference here compared to RC7), but there are still freezes all few days. Often during wakeup from suspend, but also while working.

Revision history for this message
Pablo Gil (pgilmon) wrote :

Touching /etc/pm/power.d/wireless did NOT work for me.

Donwgrading pm-utils to Lucid version did.

Revision history for this message
jmrk (joergen-kornfeld) wrote :

No success with downgrading to Lucid or Lucid-Updates package. The only freezes that still happen (talking about Natty package now) are unsuccessful wake-ups from suspend (every 4-10 th wake-up).

Revision history for this message
Marek Bardoński (bdfhjk) wrote :

Bug still appear on both my computers - notebooks (MSI GT780DX and SAMSUNG NC10).

I will provide necessary informations which You need.

Thanks in advance in fast solving this issue. It is important to me. I will assist as much I can (I'm a c++ programmer)

Revision history for this message
little bobby tables (little-b-tables) wrote :

I experienced similar hang-ups with this machine running the preinstalled windows 7. It might not be an Ubuntu bug.

However, I'd be very pleased if some reliable workaround could be found for this annoying issue.

Revision history for this message
penalvch (penalvch) wrote :

Clayton Dillard, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel 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
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.