X freezes when compiz is enabled on ATI X300

[tamagoji]

i just installed the new ubuntu 7.4 on my laptop toshiba m40x with ati x300.
i've enabled desktop effects with no window wobbling and with cube rotation.
it works quite well but sometime, without any clear reason, the desktop freezes completely (happened simply moving the mouse on an icon or opening a new application):
the mouse moves but can't interact with the desktop
no chance to ctrl-alt-bksp, or to change console (ctrl-alt-f1), keyboard is not responding
i have to shout down the computer from the power button. (restarting everything works again but occasionally some new bugs appear)
Don't know how to give more informations.

there are a number of other minor but annoying bugs correlated, i don't know if they have to be posted here or in the compiz bugsite.
they happen quite frequently and are:
after maximizing a window it is not possible to unmaximize from the title bar icon (only from the bottom panel)
the number of workspaces resets to 1 and the cube is not able to rotate
some windows are not refreshed and the content is not visible (as bug 91810)
some windows are visible in every workspace
and more..

[Note]
There are numerous unrelated -ati errors that can cause freezes in X that are particular to specific hardware or usage scenarios. The original bug reporter's specific issue was resolved, so if you are also experiencing an X freeze it is probably unrelated to this bug. PLEASE REPORT YOUR ISSUE AS A SEPARATE BUG. Don't reopen or add confirmations onto this one.

[Ed (ed-redhat-bugs)]

Description of problem:
After enabling "desktop effects", display experiences random lockups during
display of said effects, and occasionally compiz will fail to start upon login.

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.6.3-1.fc6

How reproducible:
Just about every time.

Steps to Reproduce:
1. Buy a Lenovo ThinkPad T43p (http://www.thinkwiki.org/wiki/Category:T43p for
hardware specifications, I have the 15" 1600x1200 TFT).
2. Enable desktop effects using the xorg radeon driver.
3. Use desktop for a while, possibly log out and back in again.

Actual results:
On login, compiz will *sometimes* fail to start; disabling and then re-enabling
desktop effects fixes this. However, after several minutes to several hours of
use, the desktop will eventually hang (always in the middle of displaying a
fade, wobble, or other effect).

Expected results:
The same stability I got out of the non-AIGLX desktop. ;-) This was actually a
very stable setup prior to trying out AIGLX, with both the radeon driver and
with fglrx.

Additional info:
Here's the lspci info for my video card (I'll attach the full lspci output in a
moment, along with the xorg.conf I'm using and a relevant Xorg.0.log):

01:00.0 VGA compatible controller: ATI Technologies Inc M24 1T [FireGL M24 GL]
(rev 80) (prog-if 00 [VGA])
        Subsystem: IBM Unknown device 0570
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort+ >SERR- <PERR-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 169
        Region 0: Memory at c0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 3000 [size=256]
        Region 2: Memory at b0100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at b0120000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
                Device: Latency L0s <256ns, L1 <4us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
                Link: Latency L0s <256ns, L1 <2us
                Link: ASPM L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x16
        Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [100] Advanced Error Reporting

[Ed (ed-redhat-bugs)]

Created attachment 143639
xorg.conf

[Ed (ed-redhat-bugs)]

Created attachment 143640
Xorg.0.log

Log from a typical session that freezes.

[Ed (ed-redhat-bugs)]

Created attachment 143641
lspci -vvv output

[Ed (ed-redhat-bugs)]

Also note that the system itself does not freeze; only the display. When this
happens, I'm able to ssh back into the laptop from another machine and
"gracefully" shut things down, but the screen never returns to normal until the
system is rebooted.

[Christopher (christopher-redhat-bugs)]

Created attachment 145205
lspci -vvv output

[Christopher (christopher-redhat-bugs)]

Created attachment 145206
xorg.conf file

[Christopher (christopher-redhat-bugs)]

Created attachment 145207
Log from aiglx enabled sessions

[Christopher (christopher-redhat-bugs)]

I see this also. This on a Thinkpad T42. See above attachments. Workaround is
obviously to disable desktop effects however given that it took me a while to
find the (probable) cause I would ask this to be re-prioritised upwards as there
is likely to be a number of folks who are banging their heads into walls/screens
on this one.

[Christopher (christopher-redhat-bugs)]

Edward,

Could you please test with the latest flash plugin (ie. 9 final) as I believe
this to be the source of our problems.

Regards
Chris

[Steph (stephspam)]

I have the same freeze problem with Desktop effects enable (Window & cube) on a Toshiba M40 PSM42 laptop with ATI Mobility Radeon X600 SE.
Very annoying, as described above, the desktop sometimes freeze, the mouse can be moved, but nothing else worked! Keyboard is not responding, impossible to select anything on the screen with the mouse. Only solution, the power button.

[Jorge García (jorgegarciar)]

Hi,
     Here is exactly the same. Mine is an Acer Aspire 1652 LMI with an ATI Mobility Radeon X300. I hadn't this problem with Dapper. It's just happening with Feisty Fawn. If I stop Desktop-effects, the problem disapears. I tried to insall Beryl instead of Compiz (current desktop-effects in Feisty) and I get again the same mistake after a while (it can be 5 minutes or a whole day). It's quite anoying... and the only possible solution in press the Shutdown button cause keyboard is not woking at all (even Shift, bloq. shift, ...).

     Any clue?

Thanks.

[grumpybuffalo (whozadumbstuff)]

Hello,
      I have a similar problem using beryl. Oftentimes, some/all applications will not redraw, but they have not frozen. This means that if I click on the logout button, it shows nothing happening, but then if I click where the log out button *would* be, it logs out and I can log back in. If only one window is refusing to redraw, I can minimize it and unminimize to redraw it; however the problem will still be there.
      The problems stay the same when I use compiz instead of beryl. I am using an HP compaq nc6000. If anyone can figure this out, please let me know.

      Thanks,
      Grumpy Buffalo

[Travis Watkins (amaranth)]

All of these users have an ati card, looks like a driver issue.

[Bryce Harrington (bryce)]

Can you test if the issues go away when you add the following in your /etc/X11/xorg.conf?

Section "Module"
# Load "dri"
 # Load "glx"
        Disable "dri"
        Disable "glx"
EndSection

Please also attach your /var/log/Xorg.0.log.old file after restarting after experiencing a lockup.

[Erkin Bahceci (cornelius1)]

I have the same random freeze problem with the current gutsy. It happens with desktop effects enabled within 1/2 hour of use. I am using the default "ati" open source driver. This is on an X300 Mobility Radeon. Disabling dri and glx effectively disables desktop effects and "fixes" the problem. But if I want to use compiz, the open source driver is a no go for me, which is pretty bad since fglrx has its own problems (it won't make this laptop suspend). So running compiz is not feasible on gutsy with any driver on this Dell Inspiron 6000 + X300 Mobility.

[Travis Watkins (amaranth)]

Can all of you having this problem attach the output of `lspci -n`?

[Erkin Bahceci (cornelius1)]

X300 Mobility Radeon here

$ lspci -n
00:00.0 0600: 8086:2590 (rev 03)
00:01.0 0604: 8086:2591 (rev 03)
00:1d.0 0c03: 8086:2658 (rev 03)
00:1d.1 0c03: 8086:2659 (rev 03)
00:1d.2 0c03: 8086:265a (rev 03)
00:1d.3 0c03: 8086:265b (rev 03)
00:1d.7 0c03: 8086:265c (rev 03)
00:1e.0 0604: 8086:2448 (rev d3)
00:1e.2 0401: 8086:266e (rev 03)
00:1e.3 0703: 8086:266d (rev 03)
00:1f.0 0601: 8086:2641 (rev 03)
00:1f.2 0101: 8086:2653 (rev 03)
01:00.0 0300: 1002:5460
03:00.0 0200: 14e4:170c (rev 02)
03:01.0 0607: 1180:0476 (rev b3)
03:01.1 0c00: 1180:0552 (rev 08)
03:01.2 0805: 1180:0822 (rev 17)
03:03.0 0280: 8086:4223 (rev 05)

[Travis Watkins (amaranth)]

Sorry, I meant `lspci -vn`.

[Erkin Bahceci (cornelius1)]

Here

[Erkin Bahceci (cornelius1)]

Did the output help? Is this bug fixed? Is there anything else you need to know?

Thanks.

[Angelo Lisco (angystardust-gmail)]

Sadly, same here...after 1 year of testing, this bug is not yet resolved... X freezes but the laptop is still alive: in fact, I can do a clean reboot with sysrq+alt+S, sysrq+alt+U and sysrq+alt+b
I will enable an ssh server on this laptop so next time I can catch the

However, this bug is really really CRITICAL!
Please blacklist this video card or (better) make up your mind and revert back the decision of leaving compiz on by default!
Just think about all the users who have an Ati Xxxx card: they will think linux (and ubuntu) is not better then windows...

Manufacturer: Acer, inc.
Product Name: TravelMate 8100
Video Card: ATI Technologies Inc Radeon Mobility X700 (PCIE)

[Enryfox (enryfox)]

Same problem on an IBM t43p with ATI fireGL mobility v3200. One question: to use compiz-fusion i can only rely on open source driver, if i install the restricted closed source driver i cannot use 3d effects; when i try to enable them in appearence prefs pane it says there is no compostion extension... what's wrong ?
thanks

[Angelo Lisco (angystardust-gmail)]

Enryfox, i noticed the same thing: it's clearly a big design flaw...we all know that in order to have compiz working with Ati cards, the only solution is to use the open source driver but restricted manager suggests to install the ATI proprietary driver which breaks compiz!!!
I use ubuntu from warty and I think that gutsy will be the worse release ever because of the insane decision about compiz: what a pity...all the good work done will be obscured by the critical bugs created by compiz.

Technical board, please reply...

[Thomas Raffler (thomas-rafflers)]

I experienced many Hard Locks on my Samsung X20 Notebook (ATI X600 Mobility).
If the opensource driver is used together with compiz-effects (Live-CD configuration), the system freezes completely after some minutes.

Disabling the effects is sufficient for stable use and installation (!) of the Live-CD!

[Enryfox (enryfox)]

Things are getting worst ... I have the same freezing if I start internet explorer within crossover Office 6.1. I'm using the fglrx driver latest version (gutsy updated on 1/10/07). I think it is ok if IE6 crashes, but it can't freeze Xorg !

[Angelo (angelo-redhat-bugs)]

Hi guys...sadly, same problem in ubuntu:
https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-ati/+bug/108527

[Matěj (matj-redhat-bugs)]

*** Bug 242151 has been marked as a duplicate of this bug. ***

[Lungten (joycoz-deactivatedaccount)]

I have got the same problem on ThinkPad T43p.

[Lungten (joycoz-deactivatedaccount)]

Sorry, I forgot to mention the video card. Its ATI M24GL [Mobility FireGL V3200].

[Michael Roy (mikemlp)]

I am also experiencing freezes. See http://ubuntuforums.org/showthread.php?p=3508187#post3508187
Some users have reported that their mouse cursor still moves. Mine does not, so my symptoms appear to be slightly different. Uptime when using compiz ranges from 1 minute to 23 hours. Uptime appears to be unlimited when I use metacity only. I have been using Compiz / Beryl / Fusion for over a year, and have only experienced freezes like this in Gutsy. Will try the steps here: https://wiki.ubuntu.com/DebuggingXorg and report back.

Unlike the OP, I do not experience any of the further bugs, such as not being able to minimize windows. Additionally, I have noticed this bug in Tribe 5. I moved back to Feisty for a while, and found the same bug present in 7.10 Beta.

Limited Specs:
IBM Thinkpad T42
ATI Mobility 9600
AIGLX on Free ATI driver

Please let me know what I can do to help debug.

[Michael Roy (mikemlp)]

lspci -vn

[Angelo Lisco (angystardust-gmail)]

So Michael Vogt has just released a new version of compiz package which blacklist some ati mobility cards (X300,X600,X700).
I think this was the right way to go since the problem cannot be easily fixed.
Thank you, Michael

compiz (1:0.6.0+git20071008-0ubuntu1) gutsy; urgency=low
 .
   * New git snapshot:
     - properly fix bug to never stack under the desktop window (LP: #147943)
     - fixes in the internal stack representation, this fixes the issue
       that sometimes windows are put over or under panel windows
   * debian/patches/026_fix_stacking:
     - dropped, now part of upstream
   * debian/patches/028_compiz_manager_blacklist:
     - blacklist ati mobility X300,X600,X700 freezes (LP: #115283)

[Erkin Bahceci (cornelius1)]

Just wanted to add that I experienced the same X freeze (where mouse can still move) with the fglrx driver too (v8.37), with compiz enabled.

[Ramesh Dharan (rrdharan)]

This happens for me all the time with the Gutsy RC: screen freezes up *except* the mouse cursor, and the machine is still alive but I have to power-cycle it.

I have the same hardware as MikeMLP: T42, Mobility 9600 (M10). I'm running the stock Gutsy configuration, and free/oss ati/radeon driver, with all desktop effects enabled.

I experience the hang quite regularly with both the stock 2.6.22-14 kernel as well as my hand-built 2.6.23.1. I'm happy to run any tests or provide logs or whatever else is needed if it will help resolve this problem.

[Emmanuel Touzery (emmanuel-touzery)]

i also saw that, with moving mouse cursor on a radeon 7000/VE.
since i read about it happening when opening windows (for me it happened several times when switching workspaces, i'm using the wall desktop plugin for that, but maybe also a window was opening in the background, not sure), and since some people mentioned that increasing AGP aperture helped, i thought it might be too little texture memory to store all the windows? I tried increasing my AGP aperture in the BIOS (from 64 to 128Mb), I'll see if it helps.

[Ramesh Dharan (rrdharan)]

I very much doubt the AGP aperture has anything to do with it. FWIW, my AGP aperture has been at 256MB the whole time.

The crashes seem to be entirely unpredictable in nature. Several of the times it has happened, I have only had one window open, with no wobbling or cube transitions or anything else crazy going on - e.g. I was just clicking on an OK button, and it would freeze

[Jens Gottfried (jug)]

Happens on an X800 as well.
Freezes in different situations: opening/closing/resizing/moving windows, rotating the cube, spontaneous - it's absolutely random and I see no way to reliably reproduce this.

[bigdoby (bigdoby-gmail)]

this is the last annoying bug for me in gutsy... ati open source driver with
9700 mobility... i want to help solving this bug, what can i do?

On 10/16/07, jug <email address hidden> wrote:
>
> Happens on an X800 as well.
> Freezes in different situations: opening/closing/resizing/moving windows,
> rotating the cube, spontaneous - it's absolutely random and I see no way to
> reliably reproduce this.
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Provo un intenso desiderio di rientrare nell'utero. Di chiunque (Woody
Allen)

Darth Vader: The ability to destroy a planet is insignificant next to the
power of the Force.

[bootsbradford (mark-bradford1)]

I have an ATI Mobility Radeon X600. I have been experiencing this problem with Compiz on Feisty - X freezing, except for mouse cursor movement and music continuing to play. Works absolutely fine with effects disabled.

I was hoping that the problem would be solved with Gutsy and Compiz-Fusion, but had my first crash after upgrading yesterday.

Is there really nothing that can be done about this??!!

[Michael Roy (mikemlp)]

Since posting, I have had freezes both with and without the mouse cursor still able to move. Usually, the mouse cursor is still able to move, and usually I am able to reboot with alt+sysrq rseiub. My uptime is basically unlimited with effects turned off. Since I've used Compiz for over a year without this problem, my best guess is that the bug that I am experiencing is located within the new version of X in Gutsy. I wish I could help pin it down more though.

[Arngren (arngren)]

From the more or less duplicate bug (#115283), I mentioned the animations plugin to be the potential cause. That would make some sense, since having "random animations for all event" enabled means the animations plugin is activated quite offent and can be responsible for these random crashes. Initially I disabled the plugin and experienced no problems, now I have tried to re-enable it and turning off the "focus animation" (by recommendation from Cornelius, thanks!) and is still not seeing any problems :-)

[bigdoby (bigdoby-gmail)]

this trick doesn't work for me.. even disabling the focus animation it still
freeze....

On 10/18/07, Arngren <email address hidden> wrote:
>
> >From the more or less duplicate bug (#115283), I mentioned the
> animations plugin to be the potential cause. That would make some sense,
> since having "random animations for all event" enabled means the
> animations plugin is activated quite offent and can be responsible for
> these random crashes. Initially I disabled the plugin and experienced no
> problems, now I have tried to re-enable it and turning off the "focus
> animation" (by recommendation from Cornelius, thanks!) and is still not
> seeing any problems :-)
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Provo un intenso desiderio di rientrare nell'utero. Di chiunque (Woody
Allen)

Darth Vader: The ability to destroy a planet is insignificant next to the
power of the Force.

[yemu (yemu)]

i've been using compiz with animations disabled for a couple of hours yesterday and it didnt't crash. earlier there was a crash after about 1 hour of usage. i'll be checking it later and report here.

[Adrovane Marques Kade (adrovane)]

Hi. I have an IBM Thinkpad T43 with an ATI Mobility Radeon X300 video card. I had this problem in Feisty, and I thought it would be fixed in Gutsy. Sadly, it was not. This is not a big deal to me, because I can live without Compiz.

But I do agree with some people here that it was an error from Ubuntu people to enable Compiz by default in Gutsy.

Yes, I do think Compiz is attractive, but it is too unstable (at least for me) for being enabled by default. It should be disabled by default, with a warning: "Compiz can hangs your system. Use it at your own risk." Allow me to say that it will not be a pleasure to hear people saying "hey, I tried that Ubuntu thing you always talk about, but it just hanged my machine like Windows do!".

I'm sending in the lspci -vn output. Please, let me know if there is anything I can do for help debugging this.

Regards,

Adrovane.

[Erkin Bahceci (cornelius1)]

The problem might possibly be caused by the animations plugin as you have observed, since I'm doing stuff (that might be going into some very rare infinite loop) while handling the ConfigureNotify X event, which gets fired on every mouse click. But why this would only happen on this specific group of hardware and only with the open source ati driver, I'll never know (it works fine with fglrx, which was the driver I was using all along). I'll do some debugging to pin down the bug (if it's in my plugin). Luckily I'm on a Mobility X300, and I can observe the freeze.

[Giuseppe Pantanetti (sep)]

I have the same problem on a IBM Thinkpad T43 (Model 2668Y3U) with an ATI Radeon Mobility X300 with a fresh install of Gutsy. I had the same problem on Feisty.

I thought it was a GPU temperature issue but this not the case: I reached 67 Celsius during glxgears but I couldn't reproduce the problem. I experienced freezes when CPU and GPU temperatures were under 50 Celsius.

Disabling desktop effects resolves the problem... I'm, sadly, thinking that enabling compiz by default wasn't a brilliant idea...

I've attached my lspci -vn output.

[Arngren (arngren)]

In the gutsy beta RC with updates I had not experienced any problems with the Animations plugin, but now with the Gutsy released version I get freezes very often (every 20 min. or so). I have tried to disable most plugins incl. the animations plugin but the freezes persist.

The only thing that seems common in the freeze I experience is that they always seems to happen when some windows or tooltip need to be opened, so I suspect the error could be in some of the windows management plugin, just a guess. I'll try to enable / disable different plugins every time I get a freeze and see if I can pinpoint it further.

[ilektron (robotoman)]

I have the same freezing problem on a Dell Inpsiron 6000 with an ATI Mobility x300. Mouse is responsive, ssh still works. alt sysreq works to reboot.

I had compiz-fusion working in feisty and don't recall having these problems.

Tried the gutsy beta and system was unusable. Froze after about 5 minutes each time. The actual release isn't going much better. Think I'll try the fglrx driver. Oh, what a way to dash my hopes when I thought my gpu worked with the open source drivers.

[Jens Berke (jensberke)]

IBM Thinkpad R52 with X300: Gutsy Release Candidate, clean install and upgraded to all latest packages as of today.

Freezes appear as well, sometimes pretty quick after a few minutes, but at least after about 20 minutes. I use the ati open source driver. lscpi output is attached.

Remembering that the Gutsy RC *live* system seemed to work pretty well on my laptop with compiz enabled I tried that again today: I started the Gutsy 7.10 Final live system from CD and played around with compiz four more than half an hour. No freeze! Maybe that's a hint for someone?

[Jens Berke (jensberke)]

The previous attachment is the "lspci -n" output only. This is the right one now, sorry.

[Erkin Bahceci (cornelius1)]

Mine takes hours to freeze, so can someone who gets quick freezes (in less than an hour), try disabling all non-crucial plugins in compiz to see if the problem persists? If it still freezes, then we can look somewhere other than the plugins. If it doesn't freeze, can you systematically enable the plugins enabled by default in gutsy (maybe doing a binary search on the set of plugins :) ) to see which plugin is the root of the problem?
Thanks.

[Arngren (arngren)]

As an attempt to remedy the problem I installed and enabled the restricted ATI driver "xorg-driver-fgrlx" and corresponding "xserver-xgl" via synaptic. After reboot I did not experience any freezes, but saw that rotating the cube suddenly consumed more processing time than before (I guess it must use sw rather than hw to render). So I decided to revert back to the open-source driver (uninstalling both packages) and I have not seen any freezes yet. I have slowly enabled various plugins (not the animations yet though) and are still not experiencing freezes.

I'll keep testing and trying different configurations and return with more info :-)

[ghepeu (ghepeu)]

Not a Ubuntu user, but I used to had the same problem with my Radeon X550. After the upgrade to xorg-server 1.4, mesa 7.0.1 and xf86-video-ati 6.7.xxx the freezes disappeared. I've been using compiz/compiz-fusion 0.5.2 full-time (with EXA, to use the new zero-copy-tfp) since September 14 without a single problem.

[quodlibetor (quodlibetor)]

I'm getting the same problem, but i don't have compiz or ati. It won't _let_ me use compiz, even though it was working in feisty.

Symptoms are the bad ones: Everything freezes for no apparent reason, with no apparent regularity and with no warning. Mouse doesn't work, neither does ctrl+alt+backspace. I left it frozen for 2+ hours once just to check if it would start back up on its own, but no such luck.

My Setup:
Some HP from January.
Intel Core2duo
Intel Integrated graphics (Intel Corporation 82G965 Integrated Graphics Controller (rev 02) )

Software:
Like i said, no compiz.
Everything installed from repositories. The only config that i've done that i could even imagine having this effect is that when i installed imwheel i touched xorg.conf, but nothing visual, just the mouse stuff. I followed the instructions on this thread: http://ubuntuforums.org/showthread.php?t=388161

[ghepeu (ghepeu)]

@quodlibetor: if you don't have an ATI card nor compiz installed it's a different problem and you should open a new bug report instead of adding noise here.

[Michael Roy (mikemlp)]

To those of you who were experimenting with different plugins:

I ran a test today, enabling Compiz with _no_ plugins. Navigation was a bit difficult, though entirely doable. The computer froze after several hours running Compiz with _no_ plugins enabled. alt sysrq did not work, and the mouse cursor would not move.

I do not think that the issue lies with Compiz or its plugins. I am fairly certain that the issue is with the new version of x.

[Erkin Bahceci (cornelius1)]

Yeah, as far as my debugging goes, the freeze isn't happening at least within the animation plugin code. And it's apparently not an infinite loop, since the cpu usage remains minimal.

So, reading GhePeU's comment, I guess the problem will go away with xserver 1.4. Will there be any chance of that appearing in gutsy backports?

[quodlibetor (quodlibetor)]

Yeah, I read all the comments before i posted mine and since nobody had said anything that suggested that this was actually limited to ati i was trying to say that i think the bug name is inaccurate. If you look at this thread: http://ubuntuforums.org/showthread.php?t=570184 you'll see that people are having this problem on all sorts of hardware configurations. It does seem like compiz makes it worse, though.

[Matt Sachtler (supersack56)]

I'm having the same problem, and it's driving me nuts! X300 Mobility on a Dell Inspiron 6000. Attached the output of `lspci -vn`.

[merou_ (ub-tofz)]

Same for me here with a X350 Radeon 9600. too bad, everything worked fine with Feisty, but after a painful upgrade to Gutsy i had 8 crashes in the same 8 hours ... By the way did everyone upgrade like me from feisty, or did some of you fellow reporters experience the problem with a fresh Gutsy install ?

I hope the cause of this problem will be identified soon !

[Tom (me-twpedersen-deactivatedaccount)]

My ATI Radeon 9600 (AGP) freezes already when the display-manager was starting (just after the UBUNTU welcome splash-screen - loading the OS).

I managed to start in recovery mode and turn off the modules (dri and glx) listed in the beginning of this thread and it seems to work again.

[Bryce Harrington (bryce)]

There are some additional tips for troubleshooting X freezes and crashes at https://wiki.ubuntu.com/DebuggingXorg. It sounds like the next step needing to be taken here is to get a backtrace with gdb.

If anyone can reproduce the issue using the steps described above, and then attach the information, that could give us a start on isolating this issue.

It may also be necessary to step through the code a bit to find exactly which line is causing the trouble. It generally helps to ssh into the box from a 2nd machine, so you can cut'n'paste the stuff up to the freeze after the system has frozen.

[Matt Sachtler (supersack56)]

I attached gdb and got a backtrace- it didn't seem to crash in gdb, but i Ctrl+C'ed in gdb after it had frozen up and took a backtrace. Looks like the last thing it did was move the cursor around (which is what i was doing when it froze up)

[merou_ (ub-tofz)]

I successfully rolled back my xserver to :
http://archive.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-3ubuntu8_i386.deb
(feisty version, because everything worked fine in feisty for me)

I'll try at my next login and will keep you informed. If everything runs smoothly then it's probably driver-related.

[kyleabaker (kyleabaker)]

I couldn't find a report for this with nvidia cards, but I'm having the exact same problems. I've had three different types of freezes..
1. Complete freeze. Mouse won't move and keyboard is not responsive.
2. Mouse moves, but windows are not responsive and keyboard is only occasionally responsive.
3. Freezes and unfreezes. Similar to #2 when frozen, then it works for a second (long enough to restart x server) then it starts back unless I restart x server. Then it doesn't come back for a little while.

I have Ubuntu Gutsy x64 installed to dual boot with Vista. I did a fresh install since upgrading Feisty didn't work at all. NVidia 7300LE graphics card with restricted drivers enabled. Dual Samsung SyncMaster 914v monitor setup at 1280x1024@60 TwinView. AMD processor x64. Let me know if you need more information. My "lspci -vn" print-out should be attached.

[Giuseppe Pantanetti (sep)]

I've got two identical desktop pcs with an ATI Radeon X300.

The first one was fresh installed with Ubuntu Gutsy alternate CD and X freezes after few minutes (same symptoms: all blocked except mouse pointer).

The other one was upgraded from Feisty to Gutsy and it doesn't freeze!

Attached you can find my two "lspci -vn" output (that one with freeze is the one who freezes ;)

Is there something - mainly differences between the two - I can check that can be interesting?

[DonQuichot (donquichot)]

I have the same random freeze problem with the current gutsy and an ATI Mobility Radeon X700 on an acer Extensa 4101.

[Piotr Gawrysiak (pgawrysiak)]

Confirming the same happening on Thinkpad T42 (ATI Radeon 7500). Desktop locks up, usually with just mouse cursor moving (and some visual artifacts on top of the screen). I noticed however, that usually it is possible to put the keyboard in raw mode (Alt-SysRq-R) and then switch to a text console ( eg. Alt-Ctrl-F1). From here it is at least possible to restart X (btw - any chance of restarting window manager / X etc. without killing open applications?...) The output of top shows compiz.real consuming ~100% CPU time...

[merou_ (ub-tofz)]

I found what seems to be a temporary solution to the problem !

Reversing the package xserver-xorg-video-ati to the version 1:6.6.3-2ubuntu6 (from feisty, available here http://archive.ubuntu.com/ubuntu/pool/main/x/xserver-xorg-video-ati/ ) seems to fix the problem !

Been running it for 4 hours without a freeze so far, will keep posted if anything goes wrong.

[P4man (duvel123)]

@ GhePeU

I think quodlibetor has the same concern I have: this may not be a ATI+Compiz bug which is why he posted and why I post here as well.

I have the same freezing issue on 2 different machines: one desktop with a 7900GS nVidia card (restricted driver, no compiz!) the other a laptop with onboard X300 (opensource driver, compiz enabled). A third laptop with nVidia 8600GT and Compiz enabled has no problems. The only real difference is that this third machine is a Gutsy Tribe 5 installation with all updates, the two others are fresh Gutsy release installs.

FWIW, I have seen 3 different kind of freezings on both freshly installed Gutsy machines:
- total graphical corruption. only saw this once on my nvidia desktop (no compiz, or desktop effects enabled)
- total freeze, including mouse, caps lock and scroll lock LEDs blinking (most frequent, this has even happened in the live CD environment with nothing installed or changed!!)
- freeze mouse still moving, but not even ctrl+alt+backspace did anything.

Log files don't show any obvious problems.

I had no such issues with Feisty on any of these 3 machines.

[Timo Jyrinki (timo-jyrinki)]

Please everyone keep reports of fglrx usage out of this particular bug report. Fglrx is a closed source driver that cannot be supported or fixed by Ubuntu. Also, specifically keep NVIDIA cards to their own bug report(s), and they are always currently using closed source driver for 3D. And if you're using Ubuntu 7.04, try Ubuntu 7.10. Thank you.

That said, compiz has worked fluently and without any problems here on Radeon X800 with the (default) open source driver.

After filtering NVIDIA users and fglrx driver users out, which people using Ubuntu 7.10 do have hanging and which Radeon cards do they have? It seems Mobility Radeon X300 / X700 are one, but I thought X300 was already blacklisted for gutsy because of some earlier report? And one 9600 AGP user. It also would seem like not all users of such cards experience hangs, so the actual problem might be eg. in the motherboard AGP/PCI-E support.

[Piotr Gawrysiak (pgawrysiak)]

I am using Mobility Radeon 7500 (in built card in Thinkpad T42), open source driver. So far 2 freezes on Gutsy. Definitely happens not frequently, so this might be a very difficult thing to track...

[Emmanuel Touzery (emmanuel-touzery)]

I am using the free driver and experiencing hands on a radeon 7000/VE.

[Martin Emrich (emme)]

Running gutsy i386 on a Thinkpad T41p, FireGL T2, open source ati driver.

[DonQuichot (donquichot)]

FYI
Reversing the package xserver-xorg-video-ati to the version 1:6.6.3-2ubuntu6 crashes X with the same behaviour in my case.
I'm using a Mobility Radeon X700 with the default open source driver and remove the card from blacklist manually for testing.

[merou_ (ub-tofz)]

ATI Technologies Inc RV350 AP [Radeon 9600]

and the freezes happening as frequently as once an hour !

[merou_ (ub-tofz)]

Maybe it works for me with a rollback to feisty's video-ati driver because I use my feisty's xorg.conf file accordingly ? (with mergefb and lots of glx related options)

[P4man (duvel123)]

> Timo Jyrinki wrote : After filtering NVIDIA users and fglrx driver users out, [...]
>would seem like not all users of such cards experience hangs, so the actual problem might be eg. in the motherboard AGP/PCI-E support.

Or much more likely, it has simply nothing to do with either ATI cards, drivers or even compiz for that matter.

I've had this freezing+blinking led issue since Gutsy on various machines, without compiz or desktop effects, even in a live cd envorinment with nothing extra installed, with both ati and nvidia cards, running opensource, binary and even vesa drivers!. Also, be careful also thinking you cured it when you changed something, on my machines the bug can bite several times per hour, and then without changing anything, the machines can work flawlessly for days without trouble. I can't spot any pattern in it.

So I really don't know who classified this bug as "ATI+Compiz" or why, but I see no reason to assume it is directly related to either. Its just that the original reporter happened to have an ATI card and did enable Compiz. That doesnt prove anything. Then filtering out users suffering what appears to be exactly the same problem that do not have ATI or do not have Compiz makes no sense to me.

[Enryfox (enryfox)]

P4man,

I am sure the issues you are experiencing are, in your case, un-related to Compiz and ATi driver; but maybe it is you who selected the wrong bug :). This thread reports of many ubuntu users who, like me, have no issue at all just disabling Comiz/Fusion in the gnome appearence pane. I have been using my ubuntu for quite sometime and with compiz disabled i have never experienced a single freeze; with compiz enabled it is just a matter of hours...

Let's keep concentrated on the bug issue: there is something not working with Compiz and ATI opensource driver; it might be the kernel module, the xorg server or whatever, but it is restricted to the situation as in bug description.

thanks
cheers

[Emmanuel Touzery (emmanuel-touzery)]

"So I really don't know who classified this bug as "ATI+Compiz" or why,
but I see no reason to assume it is directly related to either."

freeze happens when compiz is enabled, within a couple of hours of use, does not happen when compiz is disabled, for me and some others. QED.

[tamagoji (rpompei)]

It can be or not.
In any case, disabling desktop effects makes ubuntu work for weeks without any problem.
enabling them it freezes in 20 minutes.
the bug can be in compiz, in ati or invidia driver, in xorg or wherever... what is certain for me is that it shows itself only when visual effects are on.
Furthermore, I have the feeling that this is connected to the bug related to the to the ati proprietary driver too.. for every boost in the video property tends to freeze the system. It is like there is a bad interface between video drivers and rest of the system. (and if the video driver is not working properly compiz can not work as well).. but I am only guessing..

take care

[tamagoji (rpompei)]

I forgot..
The problem appeared in ubuntu 7.4 and is exactly the same in 7.10.
rollbacks can be guessed only with earlier versions...

[bigdoby (bigdoby-gmail)]

I disabled the "animations" plugin as suggested a lot of post ago and it's
about 2 weeks i don't have freeze on my 9700 mobile with free drivers.. if
more people can confirm this we are already at good point...

On 10/26/07, tamagoji <email address hidden> wrote:
>
> I forgot..
> The problem appeared in ubuntu 7.4 and is exactly the same in 7.10.
> rollbacks can be guessed only with earlier versions...
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Provo un intenso desiderio di rientrare nell'utero. Di chiunque (Woody
Allen)

Darth Vader: The ability to destroy a planet is insignificant next to the
power of the Force.

[Matt Sachtler (supersack56)]

I disabled the animations plugin on my laptop (mobility x300), and I've been going for almost a day without any issues. I'll post an update if it freezes up again, but this is the longest I've gone yet -- until now, it's been a max of about 15 minutes before a freeze.

[Chris Hollenbeck (chris-hollenbeck)]

I have seen the 'freezing' problem frequently on a Thinkpad T42 with a Radeon 9600 Mobility card (64MB) when desktop effects are enabled and when using the 'ati' driver. The output of lspci -vn is attached. Strangely enough, I have not seen the problem on my desktop, which has a Radeon 9600 XT card (128MB). I don't know if it makes a difference, but the laptop install was done from the release version of 7.10, while the desktop install was done starting at Gutsy Tribe 5 and then upgrading packages with auto update.

I will attach the output of lspci -vn from my desktop shortly.

[Chris Hollenbeck (chris-hollenbeck)]

Attached is the xorg.conf from my Thinkpad T42. The name of the device in xorg.conf is "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]"

[Chris Hollenbeck (chris-hollenbeck)]

Attached is the output of lcpci -vn for my desktop, which uses a Radeon 9600 XT (128MB) video card.

[Chris Hollenbeck (chris-hollenbeck)]

Sorry for the constant emails for those subscribed. It might help if I actually attached the file :)

[Matthias Himber (nomar)]

I have the same problem on a ThinkPad T40p (ATI FireGL M9). Output of lspci -vn is attached. The problem appears to be triggered by any use of 3D accceleration, I managed to provoke it by playing neverball without having compiz enabled. While X freezes completely, other apps seem unaffected, I had Amarok playing streaming internet radio several times when the freeze occured. I don't have a second machine right now to ssh into my laptop, so I can't attach any gbd output.

[getaceres (getaceres)]

Using Gutsy on a Radeon 9700 I get the same behavor. X hangs when Compiz is enabled and I have to reset the machine. Also X hangs sometimes even when I'm not using Compiz at all.
Booting the Gutsy Live CD I get the same. When Gnome is starting, it gets hanged when Compiz is started leaving me with a black screen and a cursor that I can move but nothing more. Also the CD stops spinning.
Using the Beta Live CD (Gutsy) I can start GNOME and I have compiz working.

[daves (daves-dse)]

I've also had frequent lock ups with Gusty and Feisty with ati x600 using both the open ati driver and fglrx. I can confirm that it's not related to compiz, though obviously compiz does seem to aggravate the problem. (I've completely removed all compiz related packages from my system). As mentioned above, I also find Neverball can lock it up. However, I've also had lock ups with simpler games like Solarwolf which doesn't use 3d acceleration (Or I assume not, since it's just a 2d arcade-style game.)
 Earlier with Dapper+Beryl+fglrx+Xgl, I had no problems.

[Andrew M (andrew-miniatureworldmaker)]

I have a PPC g3 ibook 800 which I know is not officially supported, but it uses the ATI 7500 mobility radeon and completely Free drivers (ati don't do ppc ones anyway). I experience this issue too.

I have disabled AIGLX, RenderAccel, Composite and a host of other ATI specific settings and none of them seem to help.
I can 100% trigger it by running glxgears though.

[P4man (duvel123)]

I withdraw all my previous comments.

As I suspected, my case had nothing to do with either Compiz or ATI, but it had also nothing to do with Gutsy! I finally discovered that increasing "IDE drive strength" in the BIOS cured all my woes.

My system has been rockstable since doing that. By accident it seems like the drive I installed Gutsy on had more troubles with the too low "drive strenght" (whatever that might be) than my other disks. That is why Windows was stable, as was Feisty. I already replaced the disk but the new one had the same problem -but it also showed in windows since I created a FAT32 partition on it that I used in both OSs. Thats how i found out.

any Asrock dual VSTA 775 owners with such trouble, try doing what I did (and don't update your BIOS beyond 1.3 or you will lose speedstep).

Sorry folks, and good luck with your bug :)

[Emmanuel Touzery (emmanuel-touzery)]

i also got now a moving mouse freeze with compiz disabled. i just had firefox, thunderbird and totem playing an OGG file with the GOOM visual effects.

so it means that compiz makes the freeze appear much faster, but it's there also without compiz. so this bug happens also in the default configuration of gutsy, even if compiz is disabled by the graphics card detector of gutsy.

[Matt Sachtler (supersack56)]

I just had it freeze up sans compiz, as well. I had pidgin, thunderbird, and exaile! open, none of which were doing anything. I was out of the room when it froze, so I wasn't doing anything that might have triggered it. It definitely happens quicker with Compiz enabled, but it froze up entirely without it.

[Emmanuel Touzery (emmanuel-touzery)]

FWIW, i was also out of the room when it froze without compiz.
one possibility could be a 3d screensaver being initialized and freezing the box trying to display some 3d... note that there was no trace of screensaver on my desktop at all... but that would not be impossible, I guess. Most of the time, screensavers do work though, including 3d ones. (I am set on random screensaver)

[johnny9537 (k9537)]

I too am having this issue. I have a Gateway 7405 with an ATI Mobility Radeon 9600. It randomly freezes when running compiz. I tried turning off the animations and right after I did that, I changed desktops and it froze again. I also notice it happens a lot when I try to drag the cube around... I turned that off and now I will wait and see if that helps. It seems like there is an unusually large amount of laptop users with this problem... One other silly idea I have is to try settings other than the custom ones. Go with the preset settings and see what happens. I will try that next if this does not work. I will go to no compiz if it is still doing it after that. I will post with my results.

[johnny9537 (k9537)]

Okay so I have been running almost a day using my computer a lot and it has not frozen yet (compared to every hour)! I disabled the Desktop Cube and reverted back to Desktop Wall (animations still on but I did turn off the focus animation)... Can others that are having the same issue try this and post your results??? I will keep the computer going and see if it freezes but I am optimistic. I will refrain, for now, from stating that it looks like the bug is in the Desktop Cube ;)

John

[tccom (antonio-cozzolino)]

Hi,
I have a suggest. Follow these steps:

1) install feisty
2) upgrade feisty installation
3) verify all is ok (also graphical effects like cube and exposè)
4) upgrade distribution to gutsy with System->Administration->Updates Manager

These 4 steps work for me in 3 configuration: 2 with ATI graphic cards (Radeon X300 PCIE, Raedon Mobility X600) and one with Nvidia graphic card (geforce 7200 GS 256 mb PCIE). For Nvidia card, i've enabled suggested restricted driver (with System-administration->restricted drive manager); i have NOT enabled that driver for ATI cards.

i hope this helps

Antonio

[bigdoby (bigdoby-gmail)]

it probably doesn't help... it's the way i did in first place but freeze
still appears...
i disabled the animations plugin and it's a lot better, still it's not the
solution of the problem because sometimes it freeze...

On Nov 7, 2007 9:40 AM, tccom <email address hidden> wrote:

> Hi,
> I have a suggest. Follow these steps:
>
> 1) install feisty
> 2) upgrade feisty installation
> 3) verify all is ok (also graphical effects like cube and exposè)
> 4) upgrade distribution to gutsy with System->Administration->Updates
> Manager
>
> These 4 steps work for me in 3 configuration: 2 with ATI graphic cards
> (Radeon X300 PCIE, Raedon Mobility X600) and one with Nvidia graphic
> card (geforce 7200 GS 256 mb PCIE). For Nvidia card, i've enabled
> suggested restricted driver (with System-administration->restricted
> drive manager); i have NOT enabled that driver for ATI cards.
>
> i hope this helps
>
> Antonio
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Provo un intenso desiderio di rientrare nell'utero. Di chiunque (Woody
Allen)

Darth Vader: The ability to destroy a planet is insignificant next to the
power of the Force.

[Piotr Gawrysiak (pgawrysiak)]

Refto desktop cube - I am using default desktop wall, but still experience freezes :( Last one yesterday - after activating "show desktop" (but I am not saying that the bug is related to this particular plugin, I think it is somewhere in the compiz core as it obviously manifests itself also while "using" other special effects).

One curious observation - after the freeze I again have been able to switch to virtual console (after "unfreezing" keyboard with Alt-Sysrq-R). compiz.real was consuming nearly 100% cpu. I killed it, and when I switched back to X display (i.e. Alt-F7) I noticed that the gui is no longer frozen (I was downloading something in firefox, and I could see that the download window was showing increasing download progress etc.). I was however unable to "click" on anything with the mouse (but I guess that is normal behaviour fater terminating compiz.real process) or use the keyboard.

Hope it helps...

[Giuseppe Pantanetti (sep)]

I tried Piotr's procedure with Alt-Sysrq-R and killing compiz.real but:

1. Alt-Sysrq-r didn't unfreeze the keyboard (on syslog my attempts were recorded as "SysRq : Keyboard mode set to XLATE
")
2. I ssh-ed to my machine during the freeze and neither Xorg nor compiz weren't consuming a considerable amount of CPU percentage
3. I sent a SIGKILL to all my processes (using Alt-SysRq-i) and _after that_ Xorg (which wasn't killed) took all my CPU resources

I'll attach my xorg.conf and Xorg.0.log*

[johnny9537 (k9537)]

Okay so I really don't know what else I can add besides telling you what worked for me... I have been running for a few days now and it has been perfectly stable. The only thing I did was turn off the cube. I know this does not fix everyone's problem but maybe if you are running the ATI Mobility Radeon 9600 it will work for you, at least until someone can find a fix for this problem. I hope so as I like to show off my 3D cube in orbit around the earth ;)

John

[Giuseppe Pantanetti (sep)]

I don't think is a 3D cube plugin's fault for these reasons:

1. In a fresh installation (start from zero: all disk formatted) of 7.10 (Gusty) the 3D cube isn't enabled by default. I had freezes with just finished installation on three different pcs: 2 desktops with ATI Radeon X300 and 1 laptop with ATI Radeon Mobility X300; none of the three had 3D cube plugin enabled.

2. I reinstalled one of my pc (one desktop with ATI Radeon X300) following tccom's procedure (basically an upgrade of Feisty after having enabled desktop effects); using this method you obtain a Gutsy with desktop effects _and_ 3D cube plugin. Till now (2 days) I didn't experience freezes.

2b: I tried the tccom's installation method on a Thinkpad T43 (ATI Radeon Mobility X300) and, unluckily, I am continuing to get freezes.

I have to add one little bit of new information:
* during freezes I managed to unfreeze the keyboard (as proposed by Piotr) with Alt-SysRq-r
* with the unfrozen keyboard I could switch to one console (with Ctrl-Alt-F1). Important: I didn't see the console as the screen remain frozen, but I could (blindly) login in the console and reboot to the system (not too much but better than a reset ;). There were no way I could kill Xorg and unfreeze the screen.

[Allan Beaufour (beaufour)]

> I don't think is a 3D cube plugin's fault

If it is the same I'm experiencing then I agree (I'm using nvidia though), because I've disabled compiz altogether and still freeze/crash. I'm think that it's related to GL and textures. https://bugs.launchpad.net/bugs/108527

[Allan Beaufour (beaufour)]

Eh, cut'n'paste error, I meant to link to this bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/161828

[AlckO (alckox)]

same problem for me...from feisty to gutsy

[AlckO (alckox)]

sorry for prev post

[Jakob Malm (malmjakob)]

I have an ATI Radeon X600 using the open source radeon driver. I updated from Feisty, but in the upgrade changed from Compiz-Fusion repositories to the official Ubuntu packages. I have experienced the freezes described above, especially when doing something window management related, like putting a window to back (with middle mouse button).

After I *switched off the animations plugin*, I haven't had any freezes. This is going on a couple of days now without any problems. (And I can really do without the animations plugin anyway...) Only switching focus animations off was not enough.

[Michael Roy (mikemlp)]

I did a test by running Compiz and turning off _all_ of the plugins (Window management was slightly difficult :) ). The machine froze with _no plugins_ running after a few hours. I am on a Thinkpad T42 with a Radeon Mobility 9600.

Right now, my uptime is nearly 8 days (on the same machine) with no stability problems... but I have all Compiz effects off, and am only using Metacity.

[Jakob Malm (malmjakob)]

Switching off the animations plugin did NOT solve it. I've had two freezes since my post above. One was when I moved my mouse to the close button on a window title bar. When the tool tip came up X froze. So I turned off the plugin "Tonande fönster" in Swedish. It makes windows smoothly appear and disappear.

It then froze again, when Bluefish was started, exactly when the splash window opened up.

[Emmanuel Touzery (emmanuel-touzery)]

using the version 6.6 as suggested by _merou stopped the freezes i had. in my case (7000/VE) I even had freezes without any 3d going on. I think it was also freezing when doing Xv. not sure. anyway... going to 6.6 fixed the problem.
I didn't try compiz though.

If others want to try, you can get the file suggested by _merou in this bug, and type this on the file:

sudo dpkg -i <file>

[horizontaleight (mbyoung)]

Hello All,

I know it has been suggested by some to keep those using the fglrx drivers out of this bug report, but from searching I believe the issue may likely to both the open source driver and fglrx. I currently have a Radeon 9700 Pro running Compiz in Gutsy and have been experiencing the random freezes with no mouse movement. I can recreate the issue by running XMMS and loading a playlist. After a few songs while using Firefox (or sometimes doing nothing but listening), a freeze will occur. I am using the flgrx driver but that is the only one I have had success enabling Compiz with. I will try a variety of scenarios including reverting back to the open source driver and disabling Compiz.

[horizontaleight (mbyoung)]

I should also note that the freezes are not a separate issue relating specifically to XMMS. I have seen the freeze playing video as well. In XMMS, when the freeze occurs, the current song in the playlist will finish playing, but the next song in the playlist will not start once the freeze has occured. I have been unable to test SSH access to my machine but will do so.

[Andrew Martin (werdz)]

I experience this sort of behaviour on a regular basis using the open source ati/radeon driver, on an Acer aspire 5500 with an ATI X700 Mobility GPU (64MB video RAM).

The problem is *far more frequent* with compiz (or beryl) enabled, however it has happened once or twice with all compositing window managers disabled (but not DRI in the xorg config). Disabling DRI in the xorg config eliminates the problem (but also disables all 3D).

I've been experiencing the same issue since Edgy, through Feisty and now in Gutsy also.

fglrx doesn't have the same problem.

[Andrew M (andrew-miniatureworldmaker)]

 "Disabling DRI in the xorg config eliminates the problem (but also disables all 3D)."

This doesn't work for me. I've disabled GLX and DRI and the problem still exists on my ibook 7500 mobility radeon using the FOSS drivers.

I'm assuming the reports on here are getting pushed upstream to X.org developers . Is this the case or should we report them somewhere else ?

[Jakob Malm (malmjakob)]

With Compiz disabled, running TORCS, an OpenGL racing car game, I have
experienced the same screen freeze. The mouse can move, but clicking doesn't
do anything. I am unable to kill the X server with Ctrl-Alt-Backspace or
switch to a different virtual console with Ctrl-Alt-F1.

I am beginning to suspect this has something to do with hardware
acceleration, rather than Compiz.

[horizontaleight (mbyoung)]

After further testing, I am still experiencing the same issues with Compiz disabled running the fglrx driver. No mouse, no keyboard. However, when I disable Compiz, the freezes happen much less often (but still do occur from time to time).

[Arngren (arngren)]

I am getting amazed by the time it takes to fix this error. It has been going on for almost 2 months now and is affecting a lot of people. I switched to Ubuntu some 3 months ago, but are seriously considering going back to xp. Both because this error prohibits any normal work and also shows how slow the error fixing process is. I am not saying that MS are any faster, because they are not, but xp is at least stable to the point of not freezing randomly (everyhting else in xp is crap, I agree). Right now I am not recommending anyone to switch to Ubuntu, because of this error.

I think whoever is looking into this (if any?) should focus on the changes/updates made during the beta period of Gutsy (sometime mid. Oct.), where the Compiz engine among other things where updated. This is where the error first introduced and shortly after the X700 card was blacklisted. Secondly someone in the forum (can not remember who) suggested this might be rooted in the 3D video memory being filled up and not released. This is why the Compiz engine is usually being pointed at as it uses the 3D engine a lot.

Sorry for my outbreak, but I sincerely hope this error can be fixed soon, so the world can be convinced that Linux and especially Ubuntu IS a better alternative to Windows.

[horizontaleight (mbyoung)]

Hello, I switched to the open source radeon driver and I noticed one slight difference in the random freezes (which still occur as I suspected). Now with the open source driver, I have the ability to move the mouse upon lock up, but that is it. No ctrl+alt+backspace, nothing. Previously, the fglrx driver would provide no mouse movement, but still locked the system completely. The freezes still occur with both drivers at random times.

There also seems to be little activity in the bug report lately. Is it possible that this issue is being discussed elsewhere and if so, can anyone point me in the right direction? This is a high priority bug as it completely destroys the notion of system stability, and I am really desperate to work this issue out. Thanks.

[Timo Jyrinki (timo-jyrinki)]

It might be useful to install xserver "dbg" packages (search for dpkg in synaptic and install X related dbg packages), then use gdb as instructed on http://www.x.org/wiki/Development/Documentation/ServerDebugging from another machine and get a backtrace. This is of course only if you think you know how to follow those instructions.

Please note that again traces etc. when using fglrx driver are next to useless, since those bugs can only be fixed by AMD.

I'm also fairly sure that various people reporting in this bug have different kind of bugs with their specific ATI models / hardware combinations. As for the open source ati driver, I myself am running them without any problems on a Mobility Radeon 9000 (a laptop) and a Radeon X800 GTO PCI-E card (a desktop computer).

[Timo Jyrinki (timo-jyrinki)]

Search for "dbg", I meant, sorry.

[Olivier (olivier-lacroix)]

Hi !

I had this problem under gutsy. I upraded to hardy alpha1 and it's gone : no more freeze so far !!

You may want to install the Xserver from hardy and see if it helps

[Matěj (matj-redhat-bugs)]

Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]

[AlckO (alckox)]

The bug still remains in hardy alpha 1 in my pc ....
Where is the fix!!!!!???

[Jorge García (jorgegarciar)]

As I posted some months before, I had the same problem with Feisty + Compiz Fusion. (ATI X300 Mobility Radeon), i86, acer aspire 1652LMi
I have recently updated to Gutsy with ATI propietary drivers (but not the newest ones: the ones in restricted repository). I've been using intesinvely my computer for a month and everything is working perfectly, no more freezes.
The only different in the configuration of my PC is that I have just 2 Desktops with the cube instead of 4. It's not as amazing showing a wall as showing a cube, but I don't need more.
I'll try to set 4 up and check what's going on.

Luck,

Jorge.

[Daniel (daniel-redhat-bugs)]

I can confirm the same issue with both Fedora 7 and 8 on a HP Compaq nx8220
laptop. The video card is:
01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility
X600]

Enabling desktop effects causes freezes, with them disabled I have no problems
at all...

[Matěj (matj-redhat-bugs)]

Could we get please updated X server config file (/etc/X11/xorg.conf) and X
server log file (/var/log/Xorg.*.log) attached to the bug report as individual
uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

[Daniel (daniel-redhat-bugs)]

Created attachment 290647
Requested file: xorg.conf

[Daniel (daniel-redhat-bugs)]

Created attachment 290648
Requested file: Xorg.0.log

Xorg.o.log copied after the freeze, X started with the xorg.conf previously
attached.

[Daniel (daniel-redhat-bugs)]

Created attachment 290649
Requested file: Xorg.0.log

Xorg.0.log copied after the freeze, X started without any xorg.conf file.

[Daniel (daniel-redhat-bugs)]

For these tests I enabled desktop-effects and rebooted to make sure AIGLX and
compiz were there from the start.

The first time the screen froze after about 20 minutes of use (the test with the
xorg.conf file in place, as it usually is). The second time (without the
xorg.conf file) it froze after about 5 minutes of use. Both times the screen
froze completely except for the mouse pointer which still moves but can't click
anywhere. The keyboard freezes also.

Logging to the laptop from another machine via ssh works fine, this is how I
copied the logs. Here is some extra info taken after the second freeze:

[root@dragon ~]# uptime
 21:03:10 up 15 min, 3 users, load average: 0.00, 0.10, 0.17
[root@dragon ~]# free
             total used free shared buffers cached
Mem: 1034820 714744 320076 0 36076 301340
-/+ buffers/cache: 377328 657492
Swap: 1048568 0 1048568
[root@dragon ~]# vmstat
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
 r b swpd free buff cache si so bi bo in cs us sy id wa st
 0 0 0 320032 36080 301352 0 0 355 32 310 893 9 3 80 8 0

[root@dragon ~]# ps ax | grep comp
 2867 ? S 0:02 compiz --sm-client-id default1 glib gconf
 3799 pts/3 S+ 0:00 grep comp
[root@dragon ~]# strace -p 2867
Process 2867 attached - interrupt to quit
select(5, [4], [], NULL, NULL

Hope it helps...

[Matthias Himber (nomar)]

This bug magically disappeared on my machine when I upgraded xserver-xorg-video-ati to version 1:6.7.196-2 (hardy), plus dependencies.

[AlckO (alckox)]

Same for me! Bug seems to be fixed O_o

xserver-xorg-video-ati version 6.7.197

[Erkin Bahceci (cornelius1)]

Would it work on Gutsy too? If so, would a backport/update be possible for Gutsy?

[Jakob Malm (malmjakob)]

How did you do that?

2008/1/4, Matthias Himber <email address hidden>:
>
> This bug magically disappeared on my machine when I upgraded xserver-
> xorg-video-ati to version 1:6.7.196-2 (hardy), plus dependencies.
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[horizontaleight (mbyoung)]

Jakob, To upgrade to the Hardy drivers, you must edit /etc/apt/sources.list and add:
deb http://archive.ubuntu.com/ubuntu hardy main restricted

You can then download and install the driver from http://launchpadlibrarian.net/11082821/xserver-xorg-video-ati_6.7.197%2Bgit20071227.bfa22d-0ubuntu0tormod1_i386.deb

It should automatically install dependencies. You may need to remove the previous version of the driver by doing:
sudo apt-get remove xserver-org-video-ati

Unfortunately for me, however, I see no change in the issue and I am still tearing my hair out. To date, I have tried the following to resolve this issue (with an ATI Radeon 9700 pro):

-setting the AGPMode in my xorg.conf to various options. I can only change between 8x and 4x and the issue still persists under both modes. I have no BIOS option to set to a lower agp mode and I can not force the card into AGP 1x mode
-setting BusType "PCI" (gives horrible performance and has still locked)
-Option "RenderAccel" "0"
-Option "MergedFB" "off"
-Option "UseFastTLS" "0"
-setting the agpgart size to 64
-both the hardy and gutsy build drivers of 6.7.197 from tormod's PPA
-disabling DRI and desktop effects
-cursing at my video card and trying about 60,000 other combinations

If anyone has any ideas, I will be incredibly appreciative. My system locks within an hour on average, and video/GL only speeds the issue up. Tormod, if you have any ideas or insight toward this problem, I will build several churches in your name.

[Emmanuel Touzery (emmanuel-touzery)]

if it's fixed in hardy, it might be a combination of newer X *and* newer ATI driver.
keep in mind that xorg is newer in hardy.

for gutsy, i think the simplest solution is just to use the feisty ATI driver. it completely stopped the lockups for me. you just install the feisty ATI driver, *no* other dependency.

just check
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/108527/comments/53
and https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/108527/comments/102

[komplexitee (komplexitee)]

"Random" freezes occurred after a few minutes of use with the receipt of a NMI interrupt. The display and keyboard were frozen but the mouse cursor moved. This happened twice. The computer had run Fedora Core 8 and Windows XP Pro within the week without any problems.

I installed the ATI driver version (restricted) suggested by Ubuntu and haven't had the problem since (about 18 hours of use). No other changes by me.

Factoids:

Ubuntu 7.10, clean install with patches applied.
Added Eclipse and Java SDK 6.
The computer is a Dell 4700 with an ATI Radeon X300.

The last kernel messages before the freeze were:
kernel: [ 533.620610] Uhhuh. NMI received for unknown reason b1 on CPU 0.
kernel: [ 533.620617] You have some hardware problem, likely on the PCI bus.
kernel: [ 533.620619] Dazed and confused, but trying to continue

(I have the full syslog sequence for the pre-crash and post-fix boots if that is of interest.)

(Ubuntu newbie guess follows...) This makes me wonder whether the problem is a glitch on the PCI bus (that is being driven hard by the video card + open source driver), causing the NMI interrupt, and leading to the "Dazed and confused" video display behavior that follows. This could happen more frequently on certain computers and with certain video cards; small driver changes might fix some computers but not others? Maybe the ATI driver knows how to back off the bus loading and/or recover from this problem???

ATI configuration info:
$ lspci -n | grep 0300
01:00.0 0300: 1002:5b60
$ lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]

-- Jim

[Garth (garth-tilefile)]

Seeing this as well on non ATI machines. (AMD64, NVidia).
Xorg freezes (seemingly randomly), always in the same place in the kernel:

[ 1871.080030] Xorg D ffff810037930540 0 5246 5241 (NOTLB)
[ 1871.080034] ffff81002c33fe68 0000000000000082 0000000000000000 ffff81002e8c7000
[ 1871.080037] ffff81002c33fc78 0000000000000000 ffff8100379a14a0 ffffffff8052d3c0
[ 1871.080041] 0000000000010d5e ffff8100379a1650 0000000000000292 00000001000b7425
[ 1871.080044] Call Trace:
[ 1871.080066] [<ffffffff8803981c>] :usbcore:usb_hcd_unlink_urb+0x18c/0x1b0
[ 1871.080080] [<ffffffff8803a54a>] :usbcore:usb_kill_urb+0xba/0x110
[ 1871.080085] [<ffffffff8024b2b0>] autoremove_wake_function+0x0/0x30
[ 1871.080091] [<ffffffff8039dc31>] input_close_device+0x51/0x70
[ 1871.080096] [<ffffffff803a0729>] mousedev_release+0xc9/0x130
[ 1871.080100] [<ffffffff8029a3f1>] __fput+0xc1/0x1e0
[ 1871.080107] [<ffffffff80297364>] filp_close+0x54/0x90
[ 1871.080111] [<ffffffff80298ae6>] sys_close+0x96/0xf0
[ 1871.080115] [<ffffffff80209e8e>] system_call+0x7e/0x83

[Severun (sev-95)]

I am having the same problem. Travelmate 4670, Intel Centrino Duo and ATI mobility x1400

I can consistantly reproduce this by starting a session from GDM, then opening an xterminal and typing
glxinfo.

At that point, I can still focus on Windows, but I cannot click on buttons, or drag or scroll. I can still restart X w/ a ctrl-alt-backspace. I can also switch screens with ctrl-alt-F1, F2, etc.

The only thing that seems to work is to start up w/out Compiz.

Let me know if I can test or can provide more info to help.

-Scott

[Severun (sev-95)]

Forgot to Add, I've got Ubuntu Gutsy, and latest and greatest Compiz and Xorg and using fglrx.

I've also got another machine w/ an Nvidia 8800 GT w/out Dual SLI and an EVGA Mobo and Quad Core CPU (Intel) that runs all of this find.

[Erkin Bahceci (cornelius1)]

Just tried out Hardy Alpha 3. Unfortunately the issue is still there. It locked up after about 30 minutes, freezing everything but the mouse pointer. This was on a Dell Inspiron 6000.

lspci output:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M22 [Mobility Radeon X300] [1002:5460]
01:00.0 0300: 1002:5460 (prog-if 00 [VGA])
 Subsystem: 1028:2003
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at d0000000 (32-bit, prefetchable) [size=128M]
 I/O ports at de00 [size=256]
 Memory at dfdf0000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at dfd00000 [disabled] [size=128K]
 Capabilities: <access denied>

[Textureglitch (textureglitch)]

I can confirm a similar issue on a fresh installation of Gutsy. I have the ATI card FireGL V7200 and dual monitors. I cannot set a higher resolution than 800x600 on these screens without using the proprietary ATI drivers. Even the drivers in the Restricted Manager or in Synaptic do not work at all, I have to 'compile' the original proprietary drivers downloaded from ATI's website using the instructions on the Linux ATI Wiki: http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#Method_2:_Install_the_Catalyst_7.12_Driver_Manually

I have the problem that Compiz freezes completely (no Ctrl+Alt+Backspace, no Ctrl+Alt+F1 to a terminal) after about 30 seconds after logging in. The mouse is still active and can move around, but cannot interact with the desktop at all.
The only solution is to hard reboot the computer on the power button and usually after two or three attempts, everything works perfect and continues to do so all day. (!)

In other words, the freeze ONLY occurs right after login, or it does not occur at all. And it ALWAYS occurs after a PROPER shutdown.
I can only assume that when the computer freezes and I cut the power and reboot, something that was not loaded properly the last time goes into some failsafe or default mode, which actually makes Compiz work as it should.

I have never managed to get Compiz working after a proper shutdown on this machine, it's only when I reboot it in mid-login that it has a (small) chance of working correctly on the next startup.

[kungmidas (ih82b)]

Have the exact same problem. Not sure I can add something new, but here's what I know...

- Random freezes, often within less than an hour.
- Any ongoing animation freeze in place, sometimes with graphical glitch
- Mouse cursor still moves, but can't click anything.
- Everything else (music etc) keep going, but display is frozen
- Occurs with ATI X300SE (open source driver) -- does NOT occur on Intel 965G-something (otherwise identical hardware)
- Occurs with Compiz enabled -- does NOT occur with Compiz disabled
- I'm running Gutsy

Also attaching "lspci -vn" output.

[Erkin Bahceci (cornelius1)]

This might be fixed with the latest changes in compiz-fusion-plugins-main. I'm not observing it anymore with latest compiz-fusion git (been going fine for a day now, earlier it would freeze within an hour).

Can someone check if this is still an issue in Hardy with the latest packages?

[Ghaith Hachem (ghaith)]

hey,
Just for the record, i'm facing this problem on my laptop, thinkpad z60m with x300 ati, compiz enabled with the default effects, i'm not however facing it on my desktop with ati x300se, actually i sometimes keep the desktop running for weeks with no slowdowns..
on another note, i previously had faced some lockups on my laptop while playing warcraft, and once with worms 3d, so it might after all be a driver issue not a compiz one no?

[Angelo Lisco (angystardust-gmail)]

Hi Cornelius,
Today I was playing a bit with the last release of Elisa Media Center (great
software) and it crashed my system after 10 min of use...just like when I
enable compiz!
Ghaith is right...this isn't a compiz bug but an ATI driver issue (the
open-source one).

2008/1/26, Ghaith Hachem <email address hidden>:
>
> hey,
> Just for the record, i'm facing this problem on my laptop, thinkpad z60m
> with x300 ati, compiz enabled with the default effects, i'm not however
> facing it on my desktop with ati x300se, actually i sometimes keep the
> desktop running for weeks with no slowdowns..
> on another note, i previously had faced some lockups on my laptop while
> playing warcraft, and once with worms 3d, so it might after all be a driver
> issue not a compiz one no?
>
> ** Attachment added: "lspci.txt"
> http://launchpadlibrarian.net/11576147/lspci.txt
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchpad.net/bugs/108527
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Erkin Bahceci (cornelius1)]

Never mind. I had two random within-an-hour freezes today with the latest Compiz running. In one freeze I could move the pointer, in the other I couldn't. ssh'ing in from another machine, both times CPU was at ~0% and backtraces (gotten by attaching gdb to compiz) looked like it didn't happen in Compiz.
That one time earlier this week, same version of compiz ran for almost 2 days without any crashes. I guess I was just lucky.

[daves (daves-dse)]

I've just done a clean install of hardy alpha3 (+ updates) and the problem definitely persists. In its current state, my laptop has been almost unusable for important work under ubuntu for far too long, and i've about had it. It even locked up the first time I tried to post here. Anyway, if it isn't resolved by the time hardy is released, I'm afraid I'll have to abandon ubuntu. While it is nice to have the new splashy 3d features, when systems crash with the severity, frequency, and duration before a solution we have here, I feel that things should be rolled back to the last know stable version. Yes, it may require other packages to be downgraded, but IT WILL WORK. The other solution is to add a notice during installation "Sorry, Ubuntu does not work with your hardware. Please install Windows or try another distribution."

(Sorry for the rant -- not that helpful I know, but as I said, I've basically had it. I do (did) like ubuntu and have been basically linux-only for a decade and I hate having to think "maybe I should boot up Windows to get some work done since at least it won't crash" :) )
Good luck tracking this issue down!

[Arngren (arngren)]

I complete agree with daves post. What good is Ubuntu if it can not work with some of the most common hardware configurations, like ATI graphic cards. Ubuntu is brilliant in so many areas, but is inferior in the most basic operations - things that Microsoft mastered decades ago is still the hardest nut to crack for Ubuntu, I am amazed!. This bug is also the reason I am going back to XP (sorry guys I know it is blasfemia) as I can not do any serious work with an Ubuntu distribution anymore. Neither am I recommending Ubuntu for anyone because of this error.

Again I agree with dave, roll back to previous packages where Ubuntu didn't freeze and work your way up. Boil the problem down as for any problem in the software debugging business. Verify any buffers are not suffering from under- or overrun etc.

Sorry for the harsh words, but I hope this gets solved very soon - Good luck debugging :-)

[Textureglitch (textureglitch)]

@Arngren and Daves

Wait, so.. because the 3D bling-bling desktop doesn't work, you're recommending people use Windows XP? Did I completely misunderstand something, or are you actually spouting gibberish?

Damn, if I had abandoned Windows every time something broke down, I wouldn't have made it past Win 3.11.

If you can't get work done because Compiz keeps crashing, here's an idea: DISABLE COMPIZ!
It's not like it's a vital part of Ubuntu, especially on a freakin' laptop with integrated graphics chips. Oh, and just for the record, ATI's proprietary drivers for Windows aren't much better. It appears that ATI just doesn't understand their own hardware well enough to actually write a driver for it.

As for an OS being inferior with regards to basic operations that others have mastered decades ago, I have just one word: Viruses.

Good day, sir!

[hronir (hronir)]

Yes, Textureglitch, but why beryl was perfectly working on Feisty?
Damn!

[Emmanuel Touzery (emmanuel-touzery)]

>Wait, so.. because the 3D bling-bling desktop
> doesn't work, you're recommending people use Windows XP?

sorry, but you didn't read the comments properly. at least for me (radeon 7000/VE, r100), the computer freezes after 20min-1 hour of use even when I don't use compiz nor any other 3d application.
it was fine on feisty. the only solution for my problem was to downgrade to feisty's ATI driver (version 6.6 as opposed to gutsy's 6.7). otherwise i would have to downgrade to feisty because my computer is useless with the 6.7 driver.

[Pierpaolo Follia (pfollia)]

@hronir
Maybe because beryl was not using some OpenGL feature that now makes the driver freeze the machine.

@Arngren and Daves
Guys, what damn are you saying? Textureglitch is right...disable compiz, or, if don't want to disable it, try using closed driver. I'm using it right now (because of this bug), and they are working good. There are problems with suspend and resume (already solved in hardy), but the system does not freeze.

[Arngren (arngren)]

I have disabled Compiz ages ago - love the effects and all, but it makes the system even more unstable as freezes occur more frequently. For me it is not question of bling bling or other fanzy effects, but right now I just like to have an Ubuntu that is stable and actually useful.

In my opinion, this error also reveals how slow the debugging is going with Ubuntu. I mean the system freezes for a lot of users for some 4-5 months now (I think this forum proves that) and still there is no update or fix available. I am wondering if anyone is actually looking into this error. Again if this is the rate errors are debugged and fixed in Ubuntu environment, then I must say I'd prefer XP on that point. I mean what happens next time an error of this size hits the fan, must we all wait 6 months with a useless Ubuntu meanwhile, before the error is fixed - I certainly hope not.

Right now people are using various kinds of workarounds by reverting back to old drivers and packages etc. depending on their hardware configuration, just to survive in Ubuntu.

I am not to happy to revert to XP, but at least it is stable to the point of not freezing the entire system spontaneously.

Sorry for my outburst again, but Ubuntu IS better that this :-))

[Emmanuel Touzery (emmanuel-touzery)]

> try using closed driver. I'm using it right now (because of this bug),
> and they are working good.

for what it's worth, even if i wanted to use the closed source driver (and i'd rather use an outdated ubuntu), i can't because my graphics card is not supported anymore by that driver.
As hardy has a new X, I fear that the old 6.6 driver won't work at all on hardy and therefore i wouldn't be able to use my computer with hardy anymore (except going to VESA but i don't have a LCD screen so the 60Hz are not workable for me).

[pappalardo (yp84)]

Any good solutions on this yet?

I'd really like to use Compiz. Just disabling it would be quite lame.

[Bryce Harrington (bryce)]

This bug is getting pretty thick with comments. :-)

The title of this bug is a bit general, and I think some of the people reporting here are actually having unrelated issues, that really should be filed as new bugs.

For troubleshooting this problem, ssh into the box from a second machine and run Xorg within gdb; when it freezes, try to get a backtrace. Info on how to do this is at https://wiki.ubuntu.com/DebuggingXorg. Then please file a NEW bug (don't attach it to this one), along with your Xorg.0.log, Xorg.0.log.old, xorg.conf, and the output of lspci -vvnn.

We'll be focusing only on the original bug reporters' issue in this bug report, so unless you're absolutely sure you have exactly the same issue as him, please file a new report (we can always mark it a dupe later if it proves to be so).

[Bryce Harrington (bryce)]

tamagoji,

A number of people have reported that this issue was solved some time after your comments - could you please test against a newer Ubuntu (Hardy if possible) and let us know if the issue is still happening for you?

If it is, please attach your xorg.conf, Xorg.0.log, and Xorg.0.log.old?

[tamagoji (rpompei)]

Hi,
Currently I cannot test on my machine if the newer Ubuntu runs better.
In few weeks I will have a new internet connection and then I will try. Also, is it pretty difficult for me to find another computer to retrive the mentioned files when mine is frozen.
Anyway, if I find a way to do that I will open a new bug with all the requested files.
(In the mean time I suppose some one else with the same problem could do that..)

bye

[Kris (kris333)]

I can confirm that this is still a problem on Hardy (unless the 2008-02-21 updates to the various xorg packages fix anything--I guess we'll wait to see). I was running all installable updates at the time of the last crash (2008-02-19). I'm running the open source ati driver on a ThinkPad T40 with a Radeon RV250 [Mobility FireGL 9000]. xorg.conf, Xorg.0.log, and lspci -vnn are attached for reference.

[luis (luis-montes)]

I was actually going to open a new bug report, but even though I can't possibly be certain it's the same bug, it's darn nearly the same. So, I got a radeon X800 card, with the open source driver, when I enable compiz it freezes randomly after about one hour, mouse moves but X is in deep freeze otherwise, I have to reboot, I can't kill X. I did follow the instructions on how debug the crash, that is, I installed the debug package for everything related with xorg, restarted the system and attached to Xorg using a laptop (via a serial cable, actually). After about 8 hours, with compiz enabled, while moving a window, the screen froze. Gotcha! I thought. Went to the laptop, and gdb had stopped because it caught a signal (broken pipe). Got the backtrace anyway and typed cont, and X continued fine, with the window missing, but otherwise functional. Actually I'm typing in that same session. Did installing the debug packages somehow helped, or unning under gdb make the signal handler behave differently? I meant, but didn't, add the NoTrapSignals option.
Mind you that I couldn't find xserver-xorg-core-dbgsym, apt-get install failed with:
The following packages have unmet dependencies:
  xserver-xorg-core-dbgsym: Depends: xserver-xorg-core (= 2:1.3.0.0.dfsg-12ubuntu8) but 2:1.3.0.0.dfsg-12ubuntu8.3 is to be installed
So it was trying to install the debug symbols for an earlier version. I noticed that most packages had a -dbg sibling, and that's what I installed.

I'm attaching the backtrace, but as I'm not sure it's the same problem since the system now seems much more stable. Are the -dbg packages and -dbgsym packages equivalent, or is the code in the -dbg packages actually changed from the released code? It seems that, really, a watched pot never boils.

[luis (luis-montes)]

lspci -vvnn

[luis (luis-montes)]

xorg.conf. Should have mentioned that I'm running a multiseat setup, but the second seat is not dri capable, so all testing is done on the first seat, Seat0. The second seat actually remains unaffected by all this.

[Forlong (forlong)]

Hi, I did what Bryce said earlier and started a report on X freezing when Compiz is enabled on ATI Radeon Mobility: https://bugs.launchpad.net/bugs/195051

So if you have the same symptoms, please go there and add all the information you have.

[warmrobot (imfrolov)]

Confirmed this bug. Which logs I must attach?

[emil.s (emil.s)]

Hi everybody!

I'm having the same problem on my Hardy testing machine, and it's almost not even usable... I'm having a Radeon X300 (not mobility), and I'm using the "ati" driver.
It seems as you have a lot of resources, but if there is something you want me to try, just tell me! Having a machine just for testing here. :)

[Forlong (forlong)]

emil.s - can you confirm you have the same symptoms as described in bug #195051 ?

If so, then not only mobility users would be concerned and therefore just blacklisting laptops using the ati driver would not be enough. This is getting pretty serious.

[emil.s (emil.s)]

Nick:
I can... :-/ lspci -v for the card:
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
 Subsystem: ATI Technologies Inc Unknown device 0303
 Flags: bus master, fast devsel, latency 0
 Memory at dfdf0000 (32-bit, non-prefetchable) [size=64K]
 Capabilities: [50] Power Management version 2
 Capabilities: [58] Express Endpoint IRQ 0

And no, this isn't pretty serious, it's critical. ;-) What will new Ubuntu users think about when the desktop just freezes... :-/

[Forlong (forlong)]

I'm sorry, I don't know which version of the radeon driver is in debian's xserver-xorg-video-ati packages, I hope you can help me out here.

Anyway, here's the problem:
On xserver-xorg-video-ati versions greater than 1:6.6.3 (like in Debian Lenny or Ubuntu Feisty) the X server freezes when using Compiz or other 3D applications like tuxracer.

With Compiz on Gutsy (xserver-xorg-video-ati 1:6.7.195) or Hardy (1:6.7.0) it takes about 20 minutes until it freezes, sometimes less.
X freezes immediately when trying to run a 3D game.

This is not the case on a current install of Debian testing (Lenny) or Ubuntu Feisty.

I started a bugreport on Launchpad with additional information: https://bugs.launchpad.net/bugs/195051

And here's another report for that issue: https://bugs.launchpad.net/bugs/108527

I couldn't find any information if the problem is already known around here.
Please let me know if you need any further informations.

[humufr (humufr-deactivatedaccount)]

I have exactly the same problem with Gutsy + 6.8.0

I'm using the ppa packages:

http://ppa.launchpad.net/tormodvolden/ubuntu/

Thank you for the driver. Good luck.

N.

[Kris (kris333)]

I can confirm this with Ubuntu Hardy (current as of 2008/03/21) on two systems, both using the xserver-xorg-video-ati driver. One is a ThinkPad T40 with the ATI Mobility 9000 (ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000]), and the other is a workstation with an ATI X600 (ATI Technologies Inc RV380 [Radeon X600 (PCIE)]).

Both exhibit the freezing behaviour described above, usually leaving only the mouse cursor active. The system is unresponsive to mouse clicks or keyboard events other than Alt+SysRq which can be used to "safely" restart the system.

I haven't been able to reproduce this bug with any reliability. It seems to happen randomly when using Compiz.

[humufr (humufr-deactivatedaccount)]

it's seems that this problem is driver related and a dupe of this one:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/195051

so perhaps that will be a good idea to go to this bug for the ati driver:

http://bugs.freedesktop.org/show_bug.cgi?id=15096

There are no reaction from the devs right now but perhaps if a lot of people are expressing their concern to have this solve that will help.

[warmrobot (imfrolov)]

I am on latest Hardy and I can confirm that bug is GONE! :-) I am sure that it was related to proprietary ATI driver. This is a history about my experience:

1) Enabling compiz was freezing my computer. Neither mouse nor keyboard does not work. Only remote connection or Reset button working. :-( It was on free (NOT-proprietary) Radeon driver, because when I use proprietary driver all the thing start running slowly. And I didn't khow why. But now I think I khow.
2) When Compiz was updated and its requirements were using only proprietary driver I got White Screen of Death.
3) And the happy end. Proprietary driver was updated and now everything is fine.

This is my opinion: when I click on "Use proprietary driver" system use WESA instead. This is why everything was so slow. And using free driver takes me to PC freezing. And when they fixed proprietary driver it solved the problem. Big thanks for developers!

I am using Radeon x550 plus.

[Kris (kris333)]

I'm glad to hear that you're having better luck with the proprietary ATI drivers, but this doesn't constitute a bug fix. The problem is know to exist specifically in the free xserver-xorg-video-ati driver. Like Nicolas mentioned, it would probably be helpful to post feedback on the freedesktop.org bugzilla:

http://bugs.freedesktop.org/show_bug.cgi?id=15096

[Bryce Harrington (bryce)]

@luis, thanks for the backtrace; it is interesting that this does not match the backtrace posted by Matt (comment #52), although they're both ending with "#0 0xffffe410 in __kernel_vsyscall ()".

For everyone else, the #1 most important thing you can post to help with this specific bug is backtraces (see https://wiki.ubuntu.com/DebuggingXorg). lspci, Xorg.0.log, and xorg.conf don't give the info we need here (although it doesn't hurt to post them).

@luis, the -dbg and -dbgsym packages aren't the same thing, but for our purposes either will suit our needs, and -dbg are typically fine for Xorg. From your backtrace, all function calls are displayed so you've done the correct thing. It is not unknown for issues to change when a debug package is installed - sometimes this affects the timings and can delay things long enough for deadlocks to break, or race conditions to disappear. However those are rare, and I doubt will affect our debugging.

This particular backtrace is describing a fault during output flushing. I suspect this is a secondary issue (i.e., X failed on our unknown issue, then you connected and told it to keep going, and it did for a bit, but the original issue left the system in a bad state, so it crashed again later). So what we need is a backtrace for that original lockup.

@luis, please see if you can capture a few more backtraces, perhaps taking them in different ways (such as immediately after attaching, before doing cont).

I was sort of able to reproduce a lockup on an ATI R350 9800 using firefox 3, without Compiz enabled. In this case, I was able to switch to a virtual terminal (ctrl-alt-f1) and pkill firefox, and everything came back. I could reproduce that situation at will (seems to have something to do with ff3's URL autocomplete dropdown). After re-reading through every comment on this bug, I suspect that perhaps it is a client application triggering this bug (screensavers, games, office applications, proprietary software, compiz, etc. all are potential suspects). So a secondary troubleshooting approach after this problem occurs might be to go to a vt and kill apps, and see if that unlocks the system. If it does, then attaching to that process (just like in the DebuggingXorg procedure) and getting a backtrace may be of use.

Ultimately, what we're looking for is a common function call and/or invalid function parameters that result in jamming up the system. After that, we can then explore what in the driver is failing under those circumstances.

For those of you who haven't given up and gone back to 'doze and that are willing to help in this work of troubleshooting down deep, thanks ahead of time!

[bigdoby (bigdoby-gmail)]

when the system freeze, also the keyboard is frozen, so it's not possible to
switch to another virtual terminal... but if you have another pc you can
connect via ssh to the frozen one.. are you sure it's the same bug even if
you were able to go to another vt?

On Sat, Mar 22, 2008 at 3:52 AM, Bryce Harrington <email address hidden>
wrote:

> @luis, thanks for the backtrace; it is interesting that this does not
> match the backtrace posted by Matt (comment #52), although they're both
> ending with "#0 0xffffe410 in __kernel_vsyscall ()".
>
> For everyone else, the #1 most important thing you can post to help with
> this specific bug is backtraces (see
> https://wiki.ubuntu.com/DebuggingXorg). lspci, Xorg.0.log, and
> xorg.conf don't give the info we need here (although it doesn't hurt to
> post them).
>
> @luis, the -dbg and -dbgsym packages aren't the same thing, but for our
> purposes either will suit our needs, and -dbg are typically fine for
> Xorg. From your backtrace, all function calls are displayed so you've
> done the correct thing. It is not unknown for issues to change when a
> debug package is installed - sometimes this affects the timings and can
> delay things long enough for deadlocks to break, or race conditions to
> disappear. However those are rare, and I doubt will affect our
> debugging.
>
> This particular backtrace is describing a fault during output flushing.
> I suspect this is a secondary issue (i.e., X failed on our unknown
> issue, then you connected and told it to keep going, and it did for a
> bit, but the original issue left the system in a bad state, so it
> crashed again later). So what we need is a backtrace for that original
> lockup.
>
> @luis, please see if you can capture a few more backtraces, perhaps
> taking them in different ways (such as immediately after attaching,
> before doing cont).
>
> I was sort of able to reproduce a lockup on an ATI R350 9800 using
> firefox 3, without Compiz enabled. In this case, I was able to switch
> to a virtual terminal (ctrl-alt-f1) and pkill firefox, and everything
> came back. I could reproduce that situation at will (seems to have
> something to do with ff3's URL autocomplete dropdown). After re-reading
> through every comment on this bug, I suspect that perhaps it is a client
> application triggering this bug (screensavers, games, office
> applications, proprietary software, compiz, etc. all are potential
> suspects). So a secondary troubleshooting approach after this problem
> occurs might be to go to a vt and kill apps, and see if that unlocks the
> system. If it does, then attaching to that process (just like in the
> DebuggingXorg procedure) and getting a backtrace may be of use.
>
> Ultimately, what we're looking for is a common function call and/or
> invalid function parameters that result in jamming up the system. After
> that, we can then explore what in the driver is failing under those
> circumstances.
>
> For those of you who haven't given up and gone back to 'doze and that
> are willing to help in this work of troubleshooting down deep, thanks
> ahead of time!
>
> --
> X freezes when compiz is enabled on ATI cards
> https://bugs.launchp...

[Forlong (forlong)]

Bryce,

I have to say I'm confused about what you said earlier about starting a "clean" new bugreport. I did that (bug #195051) and it seems like you didn't even had a look at it.

Then after nobody answered to it, I started the one over at fd.o and this one gets added here.
If we are to continue here, "my" report is obviously just a duplicate of this one.

I think it would be more wise to close this one because it has been overcrowded with problems that have nothing to do with the actual issue.
If you disagree, that's fine by me but right now having two reports on the same issue is just disadvantageous.

Regards,
Nick

[Nervous (nervous)]

Also have this problem (freeze with mouse still moving) and freeze in any 3D app soon after launch.
Radeon 8500 LE, Gutsy

[warmrobot (imfrolov)]

The bug exists on Hardy Heron Beta when booting up from LiveCD. When it happens, neither keyboard nor mouse does not working. Of course, disabling compiz is only the way.
Radeon x550 plus.

[Bryce Harrington (bryce)]

@bigdoby, actually I suspect *most* people's issues reported here are unrelated bugs, and people are adding their comments here because they have symptoms that match the (generic) title of this bug. But we won't know until we see some backtraces that we can match up.

@Nick, Nervous, warmrobot, please post backtraces from your freezes and Xorg.0.log. We have more than enough confirmations so there's no need for more, unless accompanied by a backtrace. See my comment #160.

[Bryce Harrington (bryce)]

As suggested by #162, I'm closing out this bug; I believe the original issue has long since been addressed, and this bug report has been just accumulating stray bugs with similar sounding symptoms. Normally not a big problem, but this bug got milestoned so it's showing up unnecessarily on the release list.

If anyone else has freezes on ATI systems with compiz enabled, please file a new bug. Don't forget to include your Xorg.0.log and a full backtrace!

[Emmanuel Touzery (emmanuel-touzery)]

i can't understand why you close this bug.. when tons and tons of people confirmed a problem of freeze with the open drivers and ATI cards, also in Hardy (personally I can only confirm it in 7.10).

the most recent would be comment #146, up-to-date as of 2008-02-21, on hardy.

and of course who cares about the problem on 7.10. but i expected that. i was at least hoping it would get some developer attention for hardy.

yes, this bug was hijacked by people having problem with proprietary ATI drivers, which have nothing to do with the problem with the open driver. but there is a problem with the open driver, at least in 7.10 (and it was fine in 7.04).

nevermind.

[Emmanuel Touzery (emmanuel-touzery)]

OK, I assume the bug to follow is now #195051. I subscribed to it now. That would mean that closing this bug is an administrative/cleanup action and that developers acknowledge that there is a bug (which there is). Fine with me then.

[Giuseppe Pantanetti (sep)]

I'm sorry, I agree with Emmanuel: I can't understand the closing of this bug.

Is this bug resolved? If so, why opening the new #195051 bug? Beside that, what about applying the patch for Gutsy too (maybe would be useful to anyone who can't swith to the Hardy beta or try Hardy as soon as it's released)?

If this bug isn't resolved, why closing? Where can we follow the resolution of the problem?
If there's a more specific bug, why not marking this as a duplicate?
The bug is related to ATI open source driver? Let's open a new one with "X freezes when compiz is enabled on ATI open source driver" and mark all related bugs as duplicates! The #195051 is "X freezes in drmCommandWrite() when Compiz is enabled on ATI Radeon Mobility 9600", I say: it should be marked as a duplicate.

@Bryce, You said you were "sort of able to reproduce a lockup on an ATI R350 9800 using firefox 3, without Compiz enabled...", you kill firefox3 by switching to a vt and everything comes back... I think this is not a reproduction of this bug: the system freezes with a clean install of Gutsy (and Feisty with compiz) - all of them without Firefox 3 - and it's impossible to switch to a vt... Besides that, I don't think it's a "client application" related bug: I tried to send "a SIGKILL to all my processes (using Alt-SysRq-i)" and X remained freezed.

[Forlong (forlong)]

I agree marking this as "Fix Released" is confusing, it should be marked as "Invalid".
See comments #143 (Bryce's) and #162 (mine) why.

There should also be a clarification in the original report why this has been closed and that the issue is not fixed.
Additionally it should state clearly what Bryce said in comment #143.
The more input the devs get the better, so everyone please do what Bryce told you there.

I'm reluctant to edit other people's reports myself, though – am I allowed to do that?

[Bryce Harrington (bryce)]

This is also in Ubuntu bug https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/195051 , which has some backtraces and additional information on the bug.

[Bryce Harrington (bryce)]

I talked with Alex at XDC2008 yesterday about this. He felt it was due to wrongly guessed registered back before the AMD documentation releases, that can now be fixed up by redoing those mappings; this is work he plans to undertake within the next 3-6 months.

Backtrace (while running Bubble3D screensaver): http://launchpadlibrarian.net/12894430/backtrace-bubble3d

Backtrace (while running Extreme Tuxracer game): http://launchpadlibrarian.net/12895009/backtrace-etracer The music continues playing, but the X screens are frozen

Backtraces (without full symbols):
* http://launchpadlibrarian.net/12863959/backtrace2
* http://launchpadlibrarian.net/12177917/Xorg-lockup.txt
* http://launchpadlibrarian.net/12172793/gdb

Sample Xorg.0.log's:
* http://launchpadlibrarian.net/12433344/Xorg.0.log
* http://launchpadlibrarian.net/12172839/Xorg.0.log

Workarounds (not widely verified):
* Option "AGPMode" "1" - but hinders performance

[Kris (kris333)]

Frustrated by the freeze in Ubuntu Hardy (current), I decided to try Fedora 8 to see if there was any difference. In three weeks of running Fedora 8 with Compiz enabled, I have yet to see the freeze. The Fedora version of the driver is also 6.8.0-1, although I have no idea if they've modified it in any way. Has this bug been confirmed on any distributions other than Ubuntu 7.10 and 8.04?

[Daniel Faulkner (daniel-faulkner)]

I'm also having this same problem on my hardy heron installation. It's upto date at time of writing and uses an ATI Radeon 9800pro and the opensource ATI driver.

It will seemingly randomly lockup everything is unresponsive apart from the mouse cursor, i have accessed the computer in this state as SSH seems to still work and running the top command shows compiz.real using up all available cpu and using sudo kill -9 i'm able to regain use of that pc again (just loosing the window decorations).
If there is anything needed to further aid the resolution of this bug please ask and i can try to help (but with the freezes being quite random and my time limited i might not be able to check this report to regularly).

PS: I'm currently only assuming this issue is related to the driver, it could be compiz itself but reading this bug description and the related launchpad.net bug it seems more likely my problem is the same as described here.

[Forlong (forlong)]

(In reply to comment #5)
> Has this bug been confirmed on any distributions other than Ubuntu 7.10 and
> 8.04?
>
I was able to reproduce this bug on Debian sid (xserver-xorg-video-ati 1:6.8.0) and Arch Linux (xf86-video-ati 6.8.0).

[Blido (inseyn)]

Doesn't know if this helps:

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu9)
Current Operating System: Linux stefan-laptop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686
Build Date: 15 April 2008 05:26:17PM

 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 23 18:43:45 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Configured Monitor"
(**) | |-->Device "Configured Video Device"
(**) |-->Input Device "Synaptics Touchpad"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "Generic Keyboard"
(==) The core pointer device wasn't specified explicitly in the layout.
 Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
 Using the first keyboard device.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81dc500
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.3
 X.Org Video Driver: 2.0
 X.Org XInput driver : 2.0
 X.Org Server Extension : 0.3
 X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 1.4.0.90, module version = 1.0.0
 ABI class: X.Org Video Driver, version 2.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,5950 card 1025,0080 rev 01 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 1002,5a34 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:06:0: chip 1002,5a38 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1002,5a39 card 0000,0000 rev 00 class 06,04,00 hdr 0...

[agd5f (agd5f)]

Has anyone tested with xf86-video-ati from git master and the drm from git master?
There are several commits to both that may help.

Relevant commits:
http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=0a96173cc38e506728d4c3f2dd383ba56e856578
http://cgit.freedesktop.org/mesa/drm/commit/?id=1674d2817929fe4ee4e1c4762e89600119dbdc50
http://cgit.freedesktop.org/mesa/drm/commit/?id=753a4bdf1b554490f7b288c0203050b5114433c3

[humufr (humufr-deactivatedaccount)]

I try this morning and the problem is still there. Freeze after some time of using compiz.

[Samuel (samuel-redhat-bugs)]

I'm using latest F8 and I tend to get a lot more time before it freezes. I do
have some details though. The problem appears to be in the kernel, or the
interaction between the kernel and the X server.

kernel-2.6.24.4-64.fc8
compiz-0.6.2-3.fc8
xorg-x11-drv-ati-6.8.0-4.fc8

Doing strace on "chvt 1" from an ssh connection hangs at the following point:
open("/dev/tty0", O_RDWR) = 3
ioctl(3, KDGKBTYPE, 0xbfd23c77) = 0
ioctl(3, VIDIOC_G_COMP or VT_ACTIVATE, 0x1) = 0
ioctl(3, VIDIOC_S_COMP or VT_WAITACTIVE <unfinished ...>

Doing strace on X gives endlessly repeating:
ioctl(9, 0x40046457, 0xa3fdff4) = -1 EINTR (Interrupted system call)
--- SIGALRM (Alarm clock) @ 0 (0) ---
sigreturn() = ? (mask now [])
ioctl(9, 0x40046457, 0xa3fdff4) = -1 EINTR (Interrupted system call)
--- SIGALRM (Alarm clock) @ 0 (0) ---
sigreturn() = ? (mask now [])
ioctl(9, 0x40046457 <unfinished ...>

A gdb backtrace on X gives:
#0 0x00110402 in __kernel_vsyscall ()
#1 0x00609c29 in ioctl () from /lib/libc.so.6
#2 0x04ce549b in drmCommandWrite () from /usr/lib/libdrm.so.2
#3 0x00af833e in ?? () from /usr/lib/dri/r300_dri.so
#4 0x00b269b8 in ?? () from /usr/lib/dri/r300_dri.so
#5 0x0018ab85 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so
#6 0x0018a09a in ?? () from /usr/lib/xorg/modules/extensions//libglx.so
#7 0x0018eb16 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so
#8 0x08150d3e in ?? ()
#9 0x0808881a in Dispatch ()
#10 0x0807054a in main ()

[Andi (pfannschmidt)]

I've got the same Problems.

See:

https://bugs.launchpad.net/bugs/219993

[Andi (pfannschmidt)]

And this:

https://bugs.launchpad.net/bugs/222442

[Samuel (samuel-redhat-bugs)]

I installed debuginfo packages and this is the result:

#0 0x00110402 in __kernel_vsyscall ()
#1 0x00609c29 in ioctl () from /lib/libc.so.6
#2 0x04ce549b in drmCommandWrite (fd=9, drmCommandIndex=23, data=0xa3aa77c,
    size=4) at xf86drm.c:2227
#3 0x00af833e in radeonWaitIrq (radeon=0xa3aa728) at radeon_ioctl.c:116
#4 0x00b269b8 in _mesa_Finish () at main/context.c:1676
#5 0x0018ab85 in __glXDisp_CopySubBufferMESA (cl=0xa29d098,
    pc=0xc08f1f8 "\201\020\b") at glxcmds.c:1679
#6 0x0018a09a in __glXDisp_VendorPrivate (cl=0xa29d098,
    pc=0xc08f1f8 "\201\020\b") at glxcmds.c:2322
#7 0x0018eb16 in __glXDispatch (client=0xa22b040) at glxext.c:561
#8 0x08150d3e in XaceCatchExtProc (client=0xa22b040) at xace.c:299
#9 0x0808881a in Dispatch () at dispatch.c:457

[Orlando Stein Junior (osteinjr)]

I confirm this problem with my Gateway with ATI X600.

I solve my problem using:

Section "Device"
    Driver fglrx
    Option "VideoOverlay" "on"
    Option "OpenGLOverlay" "off"

[Orlando Stein Junior (osteinjr)]

Please ignore my last email,

After 26 hours my notebook freezed. So this Options didn´t have efect.

[Bryce Harrington (bryce)]

Re-closing bug. Guys, the problem here is that the original bug report was labeled with a generic title that described a symptom - "X freezes with compiz" - that is common to many, many different bugs. A lot of different kinds of coding errors in the -ati driver lead to X freezes when using composited functionalities, often these are particular to a given driver model, or to a specific user action or condition.

I talked about the compiz-related crashes with Alex Deucher at XDC2008 the other week, and he gave some additional detail. Long ago before ATI released their documentation, developers simply had to make guesses about what registers on different ATI cards mapped to functionality-wise. By and large these guesses were wrong, with the result that the driver is riddled with mis-mapped registers, which will result in a wide range of different kinds of bugs on different cards. The good news is that now that docs are available, these issues can be investigated one by one and sorted out through reference to the documentation.

These different bugs can have seemingly the same result - a frozen or crashed X. This particular bug report was titled in such a way that all these bugs have gotten lumped together, even though they almost certainly have nothing at all to do with one another. I've heard this referred to as a "confirm storm" - so many people reporting they have the "same" issue, that it actually becomes difficult to figure out what the problems are. Also, many times commenters will believe they have the problem (when they don't, and instead have a unique problem) and unfortunately decide not to leave any details, believing that others have already given enough info and that once the original bug is fixed, their problem will go away too; yet without those details it's impossible for anyone to determine if they had the original bug or something unique, and makes it impossible to troubleshoot their issue - thus their problem receives no attention and unfortunately remains unfixed.

This is why we so strongly encourage each person to report their issue separately. It aids in tracking, so even if you do have exactly the same bug as person A, we can handle it by duping your bug report to theirs; some times it turns out that it really is not a dupe, and this lets us easily un-dupe the bug and treat it normally.

Furthermore, the way we can get these bugs fixed is through forwarding them upstream. To get them closed most efficiently, the reports need to be clear, complete, and specific. A bug report like this one (108527) with a jumble of different reporters, incomplete information, and likely a combination of different issues, would not be accepted by them.

So, in reality, having this bug open may actually *hinder* getting the issues resolved, for all of the above reasons. Please do not reopen this bug or add comments if you're having an X freeze - open a new bug. If you've already opened a bug but it's not getting attention, please be patient, we have a lot of bugs to go through but we do intend to get to all of them. De-blacklisting ATI in compiz is a high priority for Intrepid.

[agd5f (agd5f)]

Do either of the following options help?

Option "BusType" "PCI"
Option "AGPMode" "1"

[Matt Ziegelbaum (mziegelbaum)]

I flipped on EXA last night, and it seems to have solved the issue (that or some Ubuntu bug pushes). Anyway, here's my relevant information:

Ubuntu Hardy Heron 8.04 (fully updated)

uname -r: 2.6.24-16-generic

dpkg -l | grep xserver-xorg-video-ati:
ii xserver-xorg-video-ati 1:6.8.0-1 X.Org X server -- ATI display driver

Xserver version: 1.4.0.90

I'm running an ATI FireGL v3200 (M24 GL 3154 PCIE) on a Thinkpad T43p. The relevant part of my xorg.conf is:

Section "Device"
        Identifier "ATI Technologies Inc M24GL [Mobility FireGL V3200]"
        Driver "radeon"
        VendorName "IBM ThinkPad"
        Option "DynamicClocks" "on"
        Option "XAANoOffscreenPixmaps" "true"
        Option "AddARGBGLXVisuals" "true"
        Option "AccelMethod" "EXA"
        Option "RenderAccel" "true"
        Option "EnablePageFlip" "true"
        Option "ColorTiling" "on"
        BusID "PCI:1:0:0"
EndSection

The only thing I've changed myself is that I added AccelMethod EXA yesterday, and its hte first time I've gone more than 24 hours without Compiz causing a hardlock.

Hope that helps...

[Forlong (forlong)]

(In reply to comment #10)
> Do either of the following options help?
>
> Option "BusType" "PCI"
> Option "AGPMode" "1"
>

Both seem to work around the freeze. At least after a quick tuxracer test.

"BusType" "PCI" is painfully slow, though.

"AGPMode" "1" results in a somewhat playable tuxracer (but then again, the radeon driver never worked for me satisfactorily when it comes to 3D games) -- I don't have anything to compare, though, because without the option, it (still) freezes instantly.

[Forlong (forlong)]

I just did another test, where I replaced

 Option "AGPMode" "1"

with

 Option "DynamicClocks" "on"
 Option "XAANoOffscreenPixmaps" "true"
 Option "AddARGBGLXVisuals" "true"
 Option "AccelMethod" "EXA"
 Option "RenderAccel" "true"
 Option "EnablePageFlip" "true"
 Option "ColorTiling" "on"

and tuxracer immediately froze again.

Maybe I shouldn't have copied *all* of Matt's options but frankly I'm not in the mood for any more trial and error.
But Alex, if you need me to do any further testing, just ask.

I will stick to "AGPMode" "1" for now and report back if I stumble across any issues.

[Forlong (forlong)]

Sorry for the multiple posts but I just did another test where I only used

 Option "AccelMethod" "EXA"

because it was recommended in my report over at Launchpad.

The result was a much more fluent tuxracer that was actually playable.
The downside however, is a much slower 2D rendering. For example when moving a window over an area of the desktop with icons, the background flickers.
Also moving a window from one viewport to another on Compiz will result in a pretty rough transition.

It would be great if we could have the best of both worlds.
Adding both options unfortunately doesn't do the trick.

[agd5f (agd5f)]

(In reply to comment #14)
> Sorry for the multiple posts but I just did another test where I only used
>
> Option "AccelMethod" "EXA"
>
> because it was recommended in my report over at Launchpad.
>
> The result was a much more fluent tuxracer that was actually playable.
> The downside however, is a much slower 2D rendering. For example when moving a
> window over an area of the desktop with icons, the background flickers.
> Also moving a window from one viewport to another on Compiz will result in a
> pretty rough transition.
>
> It would be great if we could have the best of both worlds.
> Adding both options unfortunately doesn't do the trick.
>

EXA preforms pretty well with the latest ati driver from git a recent X server.

The root of this problem in your case is that AGP sucks. There are just too many combinations of agp cards and chipsets that only work at specific settings (some only work at 1x, others only work at 4x or 8x, etc.). We've tried both defaults in the driver, but someone's combination always breaks.

[Daniel (daniel-redhat-bugs)]

After a fresh install of Fedora 9 (only kept /home untouched, formatted
everything else) I am still getting exactly the same behavior. A few minutes
after enabling desktop effects the screen froze.

[Samuel (samuel-redhat-bugs)]

I just reproduced this on F9 as well. It took a little longer than a few
minutes, but it did eventually happen. I've noticed that it always seems to
happen with a fading effect. In this last case, I was using the Applications
menu and it froze while fading in one of the submenus. Before it has happened
while changing the volume, the volume display is semi-transparent or fades.

My laptop integrated video card is:
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]

[Matěj (matj-redhat-bugs)]

Does anybody see this on Fedora 9 and lower? (Rawhide doesn't count)

[Samuel (samuel-redhat-bugs)]

Yes, I said that in comment #22. I tested it again recently and it still happens.

[Daniel (daniel-redhat-bugs)]

Yes, I also see this in Fedora 9 and saw it before in F8 and F7. I tried several other times since I posted comment #21, after kernel or X.org upgrades with the same behaviour. I haven't tried again after the latest upgrades though. I will try as soon as I can and post the results.

[Samuel (samuel-redhat-bugs)]

A further note is that it only happens on my laptop with the integrated video. I have two desktop computers with video cards that I've run compiz on with no problems. I do have a couple of desktop computers at home with "RS690 [Radeon X1200 Series]" integrated video that I could test on if that would help. But I'm guessing from the reports in this bug that it's only the X300 with the problem.

[Daniel (daniel-redhat-bugs)]

Mine is a X600 and has the same problem. My desktop at home has an nvidia card and works fine.

[Samuel (samuel-redhat-bugs)]

A further data point. One of my desktop systems that doesn't have a problem is an X300 on PCI Express.

01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]

I don't know why it has two entries.

[Jóhann (jhann-redhat-bugs)]

There have been bunch of bug fixes

Could you retest with the latest kernel
( -132 at the time of this writing )

You can get the latest kernel build here
http://koji.fedoraproject.org/koji/buildinfo?buildID=72270

And with the latest xorg-x11-drv-ati.
( -60 at the time of this writing )

You can get the latest xorg-x11-drv-ati build here
http://koji.fedoraproject.org/koji/packageinfo?packageID=95

And report back if it either improves or fixes this issue..

Thanks.

[François (franois-redhat-bugs)]

The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present. Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.

[Samuel (samuel-redhat-bugs)]

Now that bug #473307 is fixed, I can turn on desktop effects again and see if this bug is fixed as well.

[Samuel (samuel-redhat-bugs)]

I've had no hangs so far, so it appears to be fixed.

[Forlong (forlong)]

I am on the beta of Ubuntu 9.10 (Karmic) and I'm glad to tell you this issue seems to be gone for good.
I did not need to create a xorg.conf and set something manually this time.
Compiz works out of the box and does not cause X to freeze.

I even tried running "Extreme Tuxracer" and while the game runs horribly slow, it does not freeze.

According to my Xorg.0.log, I am using the radeon driver so I consider this fixed.
Thank you.

[Forlong (forlong)]

Sorry, I obviously spoke too soon. After a couple of days without a problem, X froze just now using Openoffice (and Compiz enabled).

reopening...

[agd5f (agd5f)]

Is this still an issue with kms or a newer version of the driver?

[Manuel-lauss (manuel-lauss)]

(In reply to comment #18)
> Is this still an issue with kms or a newer version of the driver?

I still experience hard systen freezes with latest drivers. Only workaround
is to disable AGP completely (radeon.agpmode=-1). Starting KDE4 with OpenGL
compositing enabled freezes the system every time; with firefox it takes a while. This started happening with xf86-video-ati git releases around mid-april 2008, with and without KMS. (Mobility 9700, intel 855PM).

[agd5f (agd5f)]

This may be a duplicate of bug 28402

[Aaalmosss (aaalmosss)]

I also experienced random freezes after a 3d application ran, but only with kernels newer than 2.6.33. The solution was to change preemption model from preemptible kernel to voluntary kernel preemption. Might this be related?

[nfsd (in4mer+launchpad)]

This is present in 12.04 as of 12/18/2012, current on all Ubuntu updates.

Mouse moves, mouse cursor changes as movement across existing (but non-redrawn) window borders, buttons, etc. Clicking causes normal behavior (besides the window not redrawing).

Moving a window will cause all mouse cursor change functionality to stop.

This normally happens after my monitors go into ACPI power save mode. Screensaver is disabled.

Radeon 6950. Two of them, though only one is usable in this marginal OS.

[In4mer+freedesktopbugzilla (in4mer+freedesktopbugzilla)]

I can confirm that this has been happening on Ubuntu 12.04 as of 12/17/2012.

This usually occurs using compiz when the monitors go into ACPI power save mode. This occurs using both the open source ATI driver, and fglrx.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #22)
> This usually occurs using compiz when the monitors go into ACPI power save
> mode.

If it only happens at DPMS power save, it's probably not this bug but bug 49761.

[In4mer+freedesktopbugzilla (in4mer+freedesktopbugzilla)]

Nope, don't think so

[Michel Dänzer (michel-daenzer)]

(In reply to comment #24)
> Nope, don't think so

Why not? Have you tried the fix for that?

[In4mer+freedesktopbugzilla (in4mer+freedesktopbugzilla)]

As I said earlier, it happens identically with both fglrx and xorg-video-ati. If a patch to xorg-video-ati fixes a bug while using fglrx, that would be surprising indeed.

[agd5f (agd5f)]

(In reply to comment #26)
> As I said earlier, it happens identically with both fglrx and
> xorg-video-ati. If a patch to xorg-video-ati fixes a bug while using fglrx,
> that would be surprising indeed.

Does the patch for xf86-video-ati fix xf86-video-ati?

[Michel Dänzer (michel-daenzer)]

(In reply to comment #26)
> If a patch to xorg-video-ati fixes a bug while using fglrx, that would be
> surprising indeed.

The component field of this report says Radeon. It's unlikely for fglrx and radeon to be affected by one and the same bug. It's possible that fglrx has a similar bug though.

[nfsd (in4mer+launchpad)]

Does not appear to exist in 12.10/3.5.0-21-generic, either using radeon or fglrx.

As I've upgraded, I won't be available for further testing.

BTW, IIRC this issue started at 3.2.0-30, and -29 was okay. HTH. (radeon)

[Martin-peres-n (martin-peres-n)]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/3.