Desktop temporarily freezes

Bug #384884 reported by Octavio Alvarez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

The desktop is constantly freezing.

I haven't pinpointed the problem yet. It may happen any moment for no apparent reason. I haven't found a way to reproduce the problem yet.

It is very weird. Some apps freeze before others, but it is different each time. For example the system is frozen as I'm typing this. I can tell because the system monitor applet is not scrolling. The clock and link-monitor-applet is updating, though. Other than this window, no other windows are responding. I *can* switch to other workspaces, but windows don't repaint except this one. Sometimes it looks like a soft lockup.

I read about other bug reports, and, some don't fit because my system does NOT have an ext4 partition and not using an Intel graphics card. I am NOT using Compiz. I am using the open source ATI driver, though.

I opened a different report because I haven't seem any that describes unfreezeng after > 5 minutes. Though it unfreezes, it takes so long that it appears that a hard reset is the only way. So it *may* be a duplicate of another bug.

There are some constants:

1. After 5 to 15 minutes, the system unfreezes. Otherwise, it looks like it's locked (except that mouse moves).
2. While the system is frozen, you can't use CTRL+ALT+Fx switch to the tty.
3. CPU is not busy. It is 99% idle, as usual.
4. RAM looks normal.
5. Keyboard and mouse events don't get lost.
6. Network looks normal. I can SSH to the host. I put a laptop in between to monitor the network traffice (as maybe a DNS request was blocking some critical system component) but everything came out normal.
7. Nothing goes in the logs during the freeze (I put some tails -f to logs from Xorg, messages, debug and a watch to dmesg and it didn't show anything). Sometimes a "Resetting GPU" comes up in the logs, but I think this is a consequence (of the system being unresponsive) rather than the cause.

I made the following tests in order to try to isolate the problem, but the system didn't freeze:

1. find /
2. 2 x burnP6
3. 3 x burnP6 + 2 x find /
4. swapoff -a; swapon -a, asuming (swap_usage < free RAM + disk_buffers).
5. Loade 15 gnome-terminals with full scrollback buffers (~60 MB each) and making all of them read a big log file at the same time.

However, I found that CPU never went past 25% in a quad-core. I assumed all of them used the same core, so I loaded a couple of xterms too besides the gnome-terminals and still it didn't go over 25%.

Revision history for this message
Octavio Alvarez (alvarezp) wrote :

As suggested by other bug reports, I upgraded to a different kernel (I used 2.6.29.4 from mainline). I have two days without a single freeze.

Revision history for this message
Gilles Pietri (gilou) wrote :

That makes me think of the bug I still have on 9.04, ubuntu kernel: https://bugs.launchpad.net/ubuntu/+bug/376168

Not sure if it's related, anyway, I'll try a kernel upgrade too..

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Octavio Alvarez (alvarezp) wrote :

Fabio, sorry for not replying sooner. As I stated in comment #1, I upgraded the kernel. This actually fixed the problem.

I would assume the kernel entered a waiting condition of some sort in its core, which got fixed by upgrading to a different minor kernel revision.

I have not experienced this problem since, and it did not return after upgrading to 9.10 or 10.04.

Please consider closing the bug. Thank you for your interest.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Octavio
Thanks for the reply

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 ubuntu:
status: Incomplete → 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.