Random freezes after system has been suspended at least once

Bug #480850 reported by Andreas Berger
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am getting random freezes after the system has been suspended at least once. Sometimes the freezes occur directly upon resume, sometimes hours later. They never occur without the system having been suspended before.
The Freezes usually start off with one application becoming unresponsive, then gradually extend (compiz, panel, desktop..) until everything is frozen. ctrl+alt+f1, alt+print+k do not work, alt+print+REISUB works.

I have tried the following things without effect:

-Disabling compiz

-Installing the 2.6.32-rc6 kernel

-SSHing into the frozen system, as suggested here:
https://wiki.ubuntu.com/X/Troubleshooting/Freeze#How%20to%20Get%20a%20Batchbuffer%20Dump%20%28-intel%20only%29
did not work, out of two attempts, once the system did not respond at all, once it stopped responding after the password prompt

-The following xorg settings, one by one:
    * Option "AccelMethod" "xxx" - Try "XAA", "EXA", and (on recent -intel) "UXA"
    * Option "Accel" "Off"
    * Option "DRI" "Off"
    * Option "AIGLX" "Off"
    * Option "PM" "Off"
    * Option "NoMTRR"

Ubuntu release: 9.10 "karmic"
Kernel: 2.6.31-15, also 2.6.32-rc6
Package name: linux? xorg?

Please give me instructions as to how to proceed!

Revision history for this message
Andreas Berger (andi-berger) wrote :

oh, and one more thing, i don't know if it means anything, i found the following line in my pm-suspend.log:
/usr/lib/pm-utils/sleep.d/99video resume suspend: Returned exit code 1.

description: updated
description: updated
description: updated
Revision history for this message
Andreas Berger (andi-berger) wrote :

i just made a new observation, keeping a terminal with top on top of all windows waiting for the next freeze: this time the first application to become unresponsive was hydrogen, and according to top it started using 100% cpu (one of 2 cores), then the gnome-panel became unresponsive, then gnome-terminal.

what causes random innocent applications to use 100% cpu?

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Andreas Berger (andi-berger) wrote :

update: this time gnome-screensaver went 100%. i killed it, but parts of the system were already unresponsive and i had to REISUB again

Andy Whitcroft (apw)
tags: added: kernel-series-unknown
Revision history for this message
Scott Albertine (mechaphoenix25) wrote :

I can confirm this bug, on Dell Inspiron 1501, AMD 3500+ 1.8GHz, ATI Radeon Xpress 200m, default xorg.conf, 1GB ram. This bug started on a clean install of karmic, (I've been using Ubuntu since Gutsy Gibbon, never seen it break like this before) and was even present when running the liveCD. The app-freezing order doesn't appear to have a pattern, or happen after any set time post-resume, but never occurs without resuming from suspend first. The faults also, when I can get to the logs after them, show that apparently processes (or subprocesses) are failing on paging requests, which indicates to me that some kind of memory corruption is occurring here. It's also appearing on both my ATI chipset and Andreas's Intel chipset. I'm left with the conclusion that it's an X-based bug, and the desire that I had some other system with this latest version of X to test on.

I don't get the
/usr/lib/pm-utils/sleep.d/99video resume suspend: Returned exit code 1
that Andreas got, instead I have the oddness of
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 3 success.
on suspend.

Any help is appreciated, this is one of two remaining bugs I have with Karmic

Revision history for this message
Andreas Berger (andi-berger) wrote :

@Andy Whitcroft: is that your way of saying i should include information about the kernel? Please be a little more verbose :-)

description: updated
tags: added: karmic lucid
removed: kernel-series-unknown
Revision history for this message
Andy Whitcroft (apw) wrote :

@Andreas -- heh no that is a robot which looks at bugs and marks the ones we cannot programatically tell the original reported series for. Though it does seem to have had the right effect.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Andreas,

Can you run the following command to gather and attach additional debug information for us:

apport-collect -p linux 480850

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Andreas Berger (andi-berger) wrote :

there seems to be a problem:

andreas@aspire:~$ apport-collect -p linux 480850
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
Bug title: Random freezes after system has been suspended at least once
Collecting apport information for source package linux...
Uploading additional information to Launchpad bug...
   short text data...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 173, in <module>
    upload(report, bug)
  File "/usr/bin/apport-collect", line 52, in upload
    subject='apport-collect data')
  File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", line 448, in __call__
    args[key] = simplejson.dumps(value, cls=DatetimeJSONEncoder)
  File "/usr/lib/pymodules/python2.6/simplejson/__init__.py", line 237, in dumps
    **kw).encode(obj)
  File "/usr/lib/pymodules/python2.6/simplejson/encoder.py", line 194, in encode
    return encode_basestring_ascii(o)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 1756: unexpected code byte

i should maybe mention that i just booted into this system for the first time since the time i made this bug report. i am happy to provide any information you ask and try whatever you suggest, but i am no longer *actively* pursuing this issue since i am no longer using ubuntu.

@Scott: could you try the same?

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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