Random system freeze at window operations

Bug #62747 reported by Laszlo Kupcsik
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

This bug is reproducible, but I could not find out what triggers it. Sometimes after few hours, sometimes after several days the whole system freezes. There is no report in the logfiles. It only happens, when the X is in use. E.g. resize, switch between windows, or even pressing buttons in a browser. Disabling drm, glx or recompiling the kernel did not fix the issue. When the system hangs no remote login is possible, and if there is a sound playing, the buffered part of it is looped. The CPU usage is probably 100%, because if I wait, then the fan starts up. Could it be an endless loop or something? Only hard reset helps.

Dell Inspiron 8100 with ATI Radeon Mobility 7500
OS: Latest Dapper (started after upgrading from Breezy)
Using ati driver.

Laszlo Kupcsik (koopac)
description: updated
Revision history for this message
Laszlo Kupcsik (koopac) wrote :

Also see Bug #50687 (found it later :/ )

Revision history for this message
Bryce Harrington (bryce) wrote :

Thank you for reporting this bug in Ubuntu. Could you please test and see if this still occurs in Feisty or newer? Also, please let us know if you know for certain that this is a duplicate of bug 50687.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Laszlo Kupcsik (koopac) wrote : Re: [Bug 62747] Re: Random system freeze at window operations

> Thank you for reporting this bug in Ubuntu. Could you please test and
> see if this still occurs in Feisty or newer?
The problem disappeared after upgrading to Edgy. Since then I changed
computers, so I don't know about Feisty. I think it was
Dapper-specific, because it did not happen before or after.

> Also, please let us know
> if you know for certain that this is a duplicate of bug 50687.
Sounds exactly like my bug, although the guy did not try the things I
did (drm, glx etc). It was surely something with the X, or the ati
driver. But because it seemed to be random, and there were no reports
in log files, it was hard to describe it. So I can not say for certain
that it is the same.

I discussed it in a forum, and some people there had similar
experience with various graphic cards, so it might not be ATI (Radeon)
specific.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for getting back so quickly. Good to hear that it no longer occurs for you. The bug 50687 is marked fixed, so on the hunch this is a dupe of that, I'm marking this one fixed as well.

Changed in xorg:
status: Incomplete → Fix Released
Revision history for this message
Laszlo Kupcsik (koopac) wrote :

Cool! Bug squashed.

Is the closed status based on this comment?
"Well, i think we can close this bug, as it's not happening anymore in
edgy, right?"
Dapper is LTS release, and as such, upgrading to Edgy does not solve
the problems of people in production environment, where they use LTS.
As for myself, I'm content with the "fix".

On 7/18/07, Bryce Harrington <email address hidden> wrote:
> Thanks for getting back so quickly. Good to hear that it no longer
> occurs for you. The bug 50687 is marked fixed, so on the hunch this is
> a dupe of that, I'm marking this one fixed as well.
>
> ** Changed in: xorg (Ubuntu)
> Status: Incomplete => Fix Released
>
> --
> Random system freeze at window operations
> https://bugs.launchpad.net/bugs/62747
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
|_|o|_| MSN: <email address hidden>
|_|_|o| ICQ: 330898228
|o|o|o| Skype: koopac

Revision history for this message
Bryce Harrington (bryce) wrote :

Right, if someone in a production environment needs this fix in Dapper LTS, a bug should be opened with a request for backporting the fix.

Revision history for this message
Robert Abraham (abraham-robi) wrote :

Solution:
Disable special CPU/motherboard/IO services. I mean: append kernel parameters with this:
acpi = off noapic nolapic
This can be done before booting, but it's the best to create a new, "safe system start" entry in your grub menu (read manual to do this).

For me this always solved the problem, but it was never a complete solution, because other new problems occured:
1. No more wireless LAN support;
2. Ubuntu is no longer able to turn computer off when trying to;
3. USB devices working slower, especially when connecting USB 2.0 device on USB 1.0 port; this means an exponential-slowing-down.

I haven't test it with wired LAN, but it may be affected too. If you can live with these limitations then your system will be atomic-secure and stable, but your system will feel like an old 3.86/4.86 PC in the 90's.

I wonder when this bug will be fixed finally, because I might have given enough informations about the source of the problem in the beginning of this comment (IO/APIC).

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.