system freeze when using ati radeon 7000 with xorg "ati" driver

Hi,
my system freezed often when using gnome since I upgraded to hoary. I have an
AMD Athlon XP 2600+, 512 MB takems memory, an CLUB-3D Radeon 7000 and a PC-Chips
M848A.

I exchanged everything excluding my graphic card, my motherboard and my cpu.

Now, I edited my /etc/X11/xorg.conf file and changed the Driver entry in the
Device section from "ati" to "vesa". Now my system doesn't freeze. That's
because I think that it's a bug in the xorg package in Ubuntu.

It would be great when you fix it.

Thanks,
Martin

This sounds like what I'm encountering. The lockup seems random, but so far we
have not been able to go for more than an hour or so without it occuring. I have
tried a Radeon 7000 and a Radeon 7200 in this system; both cause a lockup. With
a Radeon 9200, the problem does not occur.

The system is an Athon 64 3200+, but we are running Hoary x86 on it. Motherboard
is an Epox E9NDA3+, which uses the nForce 3 chipset. I will attach a sample
Xorg.log and xorg.conf. It didn't seem to me that there were any clues in the
Xorg.log.

Martin: It might be interesting to know if you can reproduce the lockup if you
switch back to the ati driver, but set the UseFBDev option in xorg.conf.
(Unfortunately that's going to help me, as this system uses MergedFB.)

Created an attachment (id=2490)
xorg.conf used with Radeon 7000/7200

Created an attachment (id=2491)
Xorg.log when running Xorg with a Radeon 7000

Hi,
I just edited my xorg.conf, added UseFBDev, changed the driver to "ati" again
and now the system isn't freezing anymore.

Thanks,
Martin

Hi,
it isn't right what I just said. It freezed after adding comment #4 so the
UseFBDev option in xorg.conf didn't help at my computer.

Martin

I believe I'm hitting this bug as well. The system freezes (no kernel panic or
anything) shortly after starting the X server with the "ati" driver. Using the
"vesa" driver hasn't shown this. I have only found one possible clue. With the
"ati" driver, I start gdm. Then at the login screen I hit ctrl-alt-backspace.
I get this in /var/log/messages:

Jun 21 10:58:55 neasw3 kernel: __iounmap: bad address ffffff0010223000

Each time I ctrl-alt-backspace I get the same error with the same address. With
the "vesa" driver, I think I got this once, but not in response to anything, and
I can't seem to replicate it. Hopefully soon I'll get some time to try newer
xorg versions and other things. Is there any combinations of kernels and
whatnot that would be more useful for me to test?

uname -a : Linux neasw3 2.6.10-5-amd64-xeon #1 SMP Tue Jun 7 08:58:02 UTC 2005
x86_64 GNU/Linux
lspci :
0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09)
0000:00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0
(rev 09)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1
(rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2
(rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI
Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100
Storage Controller (rev 02)
0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage
Controller (rev 02)
0000:01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09)
0000:01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A
(rev 09)
0000:01:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09)
0000:01:00.3 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller B
(rev 09)
0000:02:04.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet
Controller (rev 05)
0000:04:03.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet
Controller (rev 05)
0000:04:0d.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE]

I'll attach dmesg output and /var/log/Xorg.0.log.

Created an attachment (id=2810)
dmesg showing restarting gdm

Created an attachment (id=2811)
Xorg.0.log with vesa driver

Created an attachment (id=2812)
Xorg.0.log with ati driver

This is curios:
(WW) RADEON(0): Bad V_BIOS checksum

the 'bad VBIOS checksum' warning isn't anything to worry about. the fix for
this has been committed to X.Org HEAD, so should be in Breezy soon.

Not fixed in Breezy yet.

I have the same problem, mine only happens on SMP kernels. I used to have this
problem with fedora but they solved there. I followed the bug in the fedora
bugzilla system when (I just recently turned to the Ubuntu). Also I think that
the bug 15433 (http://bugzilla.ubuntu.com/show_bug.cgi?id=9126) is the same as
this one.

I have the same problem.. here
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152648 I think it is the
same problem and they seem to have fixed it.. I'am a newbie so I don't really
know what to do.. This seems also an interesting page:
https://bugs.freedesktop.org/show_bug.cgi?id=1912. Just look at it!

Thanks

fixed in dapper

Is there a possibility to backport the solution to "breezy"? How can I get my
machine to work now?

The bug also appears in Dapper Drake.

The bug still appears in Dapper, it is a must fix!

Just reopened upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=1912

Disabling the dri solves the problem. Any chance to disable dri automatically when a radeon 7000 card is detected?

Here (FedoraCore 4 with Radeon RV100 QY [Radeon 7000/VE]), I had lots of crashes, specially while using v4l driver (TV). Diasbling DRI didn't do the trick for me.
I've switched to VESA driver and now there's no longer any freeze.
Anyway, XVideo cannot be used with VESA driver, so I needed to switch to XVIDIX video output plugin with Mplayer in order to watch Mulitmedia videos and TV.

I have the very same problem. Im using a radeon 7000 in breezy and my pc has been hanging then crashing for a very long time. It does not do this when using the VESA driver, but does when using ati and radeon drivers. I'm a gamer so I really would like the dri enabled but I can't stand this driver! Well I hope you guys figure this out.

So it does not freeze when you use ati or radeon without dri?

I have not run ati or radeon without dri becuase I need it to play games. However when I used the VESA driver I discovered that it won't use dri, but the VESA driver does not crash X.

Could you please try to use ati or radeon without dri for testing purposes?

I have seen something similar. When I use Ctrl-Alt-F1 to switch to a console, the monitor goes blank. When I use Ctrl-Alt-F7 to go back to X, it remains black. I don't think the system is crashing (maybe just the card), because ctrl-alt-del will reboot the system.

When I comment out the "Load dri" line in xorg.conf, things work properly.

This only happens when I have more than 1 Radeon 7000 card in the system. When I have 1 card installed, things work, even with the 'dri' loaded.

I'll get rid of load dri and try and reproduce the problem.

After I removed dri my pc would not crash. I tested with 10 firefox windows open to diferant sites. Then I switched back and forth between all of them. There was a lot of hanging but no crash like I would get from 2 windows open when im using dri.

Okay, thank you for trying it. So the issue seems to be dri related.

Wow! finally other people having this problem I have been trying to fix it for over a week!. I do not use ubuntu but clearly you all have the same issue with a Radeon 7k and X.org as I do. anyways it crashes the kernel driver and then the screen remains blank. I can clearly still use the computer however as I have blindly rebooted the system after this occurs by typing ctrl F1 and typing reboot in a terminal I had already opened.

Without loading dri everything runs fine, I had discovered this early on as I would switch to my other computer and read the X logs from a putty window which is how I found the kernel driver crash. I hope someone fixes this problem soon :)

There are a few things to try here.

First, make sure you have the very latest ati driver from dapper (ubuntu4).

If the problem persists and your card is not AGP, please report. If the card is AGP, make sure you don't have enabled AGP fast write in your config file. If that is the case, then try forcing to PCI mode (option "BusType" "PCI") and report if that helps or not.

Also, when the crash happens, can you send me the X and kernel logs ?

I have the same problem, with dri the system freeze, but without loading dri system runs fine.

My car is a MOBILITY™ RADEON™ 7000 IGP and have the latest driver from dapper.

I will try the PCI options this evening and let you know the results.

I have the same problem, with dri the system freeze, but without loading dri system runs fine.

My card is a RADEON™9200 on AGP and have the latest driver from dapper.

I have tried the PCI (option "BusType" "PCI") and that not work.

I have also try with <Option "AGPFastWrite" "true">

I have been using Dapper for a few days and have not had any of the abover problems since I switched. I geuse this is fixed now. If only someone could figure out how to make it run at more than 10fps....

It seems to be fixed for me, too.

Could everybody who uses Dapper and who had this problem please try if the problem is fixed now (after a dist-upgrade and a x restart)?

Closing because it seems to be fixed now.

If you do not agree here because it happens for you at an up-to date Dapper installation, please reopen.

Reopening.. Happened just again.

crash again, after the apt-get dist-upgrade.

It is still fixed on Dapper for me. I look at the conf to see if Dapper made new settings to the log and it did. The below values are lower than they were when I had Breezy.

Section "Monitor"
 Identifier "Generic Monitor"
 Option "DPMS"
 HorizSync 28-51
 VertRefresh 43-60
EndSection

btw: I have a PCI card and this was a fresh installation of dapper flight 6

When i add options bustype pci, does not work.

When i comment out load dri works fine for me, except that some games can't run.

Help!!
I get the system-freeze even when I comment out the "load dri", and both with the "BusType" "PCI" option, and without it. It is very reproducable. All I need to do is launch Firefox and it immediatelly hangs.

BTW, I have a Thinkpad T30 with a 16MB RADEON 7500 ATI Mobility card (AGP x4),
and I am using Dapper Flight 6 with the latest updates.

Here is the xorg.conf driver section:

Section "Device"
        Identifier "ATIMERGEDFB"
        Driver "ati"
        BusID "PCI:01:00:0"
        Option "MergedFB" "true"
        Option "CRT2Position" "RightOf"
        Option "CRT2HSync" "30-130"
        Option "CRT2VRefresh" "48-170"
        Option "MetaModes" "1400x1050-1600x1200 1400x1050-1400x1050 1280x1024 1024x768 800x600"
        Option "MergedNonRectangular" "true"
        Option "MergedDPI" "100 100"
EndSection

Well, I'm out of clues... looks like there is a problem with the rv200 chips, at this point, I suppose only ATI can be of proper help... For those who have mobility chips, one thing you can try is to play with DynamicClocks (enable or disable them, try both). That's the last thing I have in mind

The latest xserver-xorg-driver-ati update (1:6.5.7.3) seems to have fixed the problem! Everything seems to work even with "load dri" !!!

It's still happening on my system. Ati Radeon 7000 with an smp kernel. Ubuntu dapper beta. As soon as I log in it crashes X.

Still with 6.5.8 which was just uploaded ? If yes, is this with DRI enabled or not ? (there have been some confusion in this bug report wether it was a problem with or without DRI). Finally, does it work if you boot an UP kernel on the same machine ?

I experienced a similar situation where X and Gnome just freeze upon login(no blank screen; the screen just froze). I couldn"t access a console, mouse or anything for that matter. Only a hard re-boot (pressing the power button) would release the system.I have been experiencing this problem since i tried to upgrade (sudo apt-get dist-upgrade) to Ubuntu 6.06 Dapper beta2. I have dont have any such problem on my Ubuntu 5.10 installation. I have a ATI (ATI Radeon 9600)graphics card. (Toshiba SA60 laptop). I have had to downgrade back to Ubuntu 5.10. Could this be the same problem? Or would this be a different issue?

I just had something similar on an iMac G5 where it appears to lockup at the login prompt of gdm ... using the "nv" driver. Not sure what's up at this point. Could be related to the kbd bug that was found in the server recently and can cause memory corruption of various X server globals. One of the consequences was that it would clobber the some file descriptor and cause log output to be written to the video card config space which is deadly

It definitely still happens with the latest patches on dapper. If running the ati driver with the 686-smp kernel, the system freezes right after the splashscreen disappears. Nothing works: no ctrl+alt+del, no mouse, etc. If using the "vesa" driver (no dri) everything works well. I tried using a non-smp driver, but no matter what, uname -a keeps saying "SMP" so I'm not sure my tests are valid.. at any rate, the system still freezes, just a little later. I can open a prompt, check glxinfo (dri is on), then I try to run synaptic and the system freezes again.

I'm actually experiencing the same problem on a Dell PowerEdge 2850 server. It has an ATI 7000ve card. My computer locks up as soon as I login, forcing me to hard reboot. I tried changing my driver from 'ati' to 'radeon' which worked for a while. then i tried to vnc from a remote machine and the problem happened again. So now I'm going to try changing the driver to Vesa, and then try commenting out the Load "dri" line.

I have an ati radeon 7000, using the "ati" driver (tried "radeon" with same results. Maybe "ati" and "radeon" refer to the same thing?), and I have DRI turned *off*. Still, my system freezes at random (i.e., no ctrl-alt-bckspace, no ctrl-alt-F?, and is unpingable from the outside).

Again, note that I do not use DRI and am still experiencing these intermittent freezes.

Some more info: I have xinerama set up, so I don't know whether this contributes to the problem. Previously, running Fedora Core 4, I had no problems with this card so I'm thinking that it has to do with some recent change to the xorg drivers.

Here are the relevant sections of my xorg.conf:

Section "Module"
# Load "GLcore"
        Load "bitmap"
        Load "ddc"
# Load "dri"
        Load "extmod"
        Load "freetype"
# Load "glx"
        Load "int10"
        Load "type1"
        Load "vbe"
EndSection
...
Section "Device"
        Identifier "ATI0"
        Driver "ati"
        BusID "PCI:1:0:0"
# Option "UseFBDev" "true"
        Option "MonitorLayout" "AUTO,AUTO"
        Option "DRI" "false"
# Option "MergedFB"
        Screen 0
EndSection

Section "Device"
        Identifier "ATI1"
        Driver "ati"
        BusID "PCI:1:0:0"
        Option "UseFBDev" "true"
        Option "MonitorLayout" "AUTO,AUTO"
        Option "DRI" "off"
# Option "MergedFB"
        Screen 1
EndSection
...
Section "ServerLayout"
        Identifier "DualHead Layout"
        Screen 0 "Default Screen" 0 0
        Screen 1 "Screen2" RightOf "Default Screen"

        Option "Xinerama" "on"
# Option "Clone" "on"

        InputDevice "Generic Keyboard"
        InputDevice "Configured Mouse"
        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"
EndSection

btw. i was able to reproduce it with the latest dapper version.

ill try to get a xorg log.

In addition to everything else, we seem to have a bug specific to the radeon 7000... I suspect it could be one of the dynamic clock bits. We avoid "touching" those bits on non-mobile but I remember that we used to have "workarounds" for buggy BIOSes in the past that whacked some of those bits unconditionally and that were removed...

We might need something back in that ara for r7000.

Can somebody create a bug report into freedesktop bugzilla and put an URL to the discussion here ? I'd like to move the discussion over. Also, it might help to ask ATI (though they might not respond)

https://bugs.freedesktop.org/show_bug.cgi?id=6429

I attach a xorg logfile of a freezed X.

I have also this problem on my laptop: Dell Latitude C610 with Radeon Mobility M6 LY [Radeon Mobility 9000].

X / Gnome freezes randomly almost every time it is used.
Host is not reachable from network either.
KDE (kubuntu) doesn't seem to have this problem, so is it using X / graphics card somehow differently?
Neither Breezy had this problem.

I'll try also disabling dri from xorg.conf.

ok, I think that we talk about different bugs.

My bug started to appear with a radeon 7000 and the release of Ubuntu 5.10 (Hoary).

Yours started with a radeon 9000 and the release of Ubuntu 6.06 so I would suggest to open a special bug report for your issue.

Did that: https://launchpad.net/distros/ubuntu/+bug/49395

And disablind dri did not help... :-(

If this was enough for that:
 diff xorg.conf xorg.conf.orig
33c33
< #Load "dri"
---
> Load "dri"

We found a bug when UseFBDev is used that may explain some of the issues (it does on some chips at least). There may be more of course, but for those of you who haven't tried, try without UseFBDev.

I have the same problem here.

The system is a fresh install of Kubuntu 6.06LTS, patched to the latest available package set. The hardware is a Supermicro P6DBU motherboard with 2xP3/750 and a Sapphire ATI Radeon 7000 video card in the AGP slot. When I use the -386 kernel, everything works fine, but as soon as I switch to -686 and SMP, X always locks up somewhere after KDM coming up.

It cannot be a hardware problem, the machine is rock stable. On another partition I have a Debian Sarge with kernel 2.4.32 (hand-compiled) and it runs well with DRI turned on, in SMP mode.

I also have this Problem (freeze 10 to 60 seconds after graphical logon) on my Pentium 4 Dual Core, using an SMP kernel in combination with a Radeon 7000, using the "ati" or "radeon" driver in my xorg.conf.

I recently uninstalled my debian (which I was using for 3 years until last week quite luckily), because I did an upgrade to testing (gaining newer applications) and the error occured after that. Because I thought the testing version was the problem, I switched to Ubuntu 6.06 and everything went fine with the 386 kernel, but having installed the 686 kernel, the freeze came again.

Then I installed an arch linux and the error occured once again using gnome, also using twm (instead of gnome with metacity).

So, now I conclude that the free radeon/ati driver is the problem. Using "vesa" drivers is not really an option, because I cannot use vertical refresh rates higher than 60 Hz, what is really an ugly flickering. After turning off the "dri" option, the radeon driver does well, but dri would be really nice when playing tuxracer or so.

Are you going to fix the bug or why did you assign the bug to youself? :-)

Please look at the upstream bug report, located here:

https://bugs.freedesktop.org/show_bug.cgi?id=6429

It says that the new ati driver from the Xorg CVS could fix this issue, sadly I am not able to compile it..

I have the same problem as Osmo Laitinen with the same platform.

Dell Latitude C610 laptop with Radeon Mobility M6 LY [Radeon Mobility 9000].

Ubuntu Dapper freezing randomly, and the only way to escape is to take out the battery and power off.

I never had these problems in Breezy, which I used all the time on this laptop. Windows also doesn't have this problem, so it can't be hardware.

There is no information in the /var/log files either.

It is really frustrating, and makes the whole experience unusable as I keep losing work. I'll try to turn off some of the ati features as suggested here or use the vesa driver.

I can confirm this bug with 686 kernel and a p4. With 386 kernel the system is stable.

On Wed, 2006-08-09 at 14:03 +0000, Edu wrote:
> I can confirm this bug with 686 kernel and a p4. With 386 kernel the
> system is stable.

A bug regarding clocks setting was fixed (including in the stable branch
I think) a few weeks ago that might fix part of the problem.

Ben.

i have the same problem i'm going to try 386 kernel

without DRI it's working.

Out of interest, do the binaries mentioned at:
http://64.71.152.24/ make any difference in 16bpp or 32bpp mode?

16bpp for me.
sorry but i prefer wait a free and viable solution without contraint or mercantile contribution.

again present without dri :-(

In edgy or dapper? Did the bug disappear for some time?

It's the same for me with a dapper with the last update(and before)...
With or without DRI activated it freezes randomly. I've got the feeling with DualHead even more. My record is 4 freezes per hour.
Know I work with the vesa Driver which don't freeze.
With Breezy this never happened to me.

I can confirm this bug is still open and is a major issue. Dapper 686 smp, with all latest updates, freezes a few seconds after logon when using a Radeon 7000.

My spec:

2 * PIII 733 mhz processors (Coppermine)
Intel OR840 Workstation m/b
768 ram
Asus ATI Radeon 7000

Ubuntu:

Dapper 6.06 01 686 smp kernel (fully updated)

- The 386 kernel works.

With the 686 smp kernel:

- Disabling FB, AGPFastwrites and DRI does not work
- The VESA driver works

i confirm this bug in Edgy and Dapper ....
DRI or without DRI under my Sony VAIO Z1RMP (ATI Mobility Radeon M6-C16)
kernel 2.6.15 or 2.6.17 686 .. :-(

please try a combination of those lines

Option "DynamicClocks" "true"
Option "AccelMethod" "EXA"
Option "DMAForXv" "off"
Option "BusType" "AGP"
Option "SubPixelOrder" "NONE"

worked for mine (Dell with ATI M6 running 1400x1050 @ 24bpp).
(don't know which line solved the freeze though :)

so far, it seems to me to be fixed in dapper..

could anybody confirm this, please?

I mean that it seems to be fixed in edgy of course..

sorry

no freeze since yesterday ;-) with new upgrade 1:6.6.2-0ubuntu2

no i can't confirm ... my computer crash again :'(
Edgy, ati package 1:6.6.2-0ubuntu2, generic kernel 2.6.17, DRI Enable... "ati" driver
i'm going to try Binh Trinh tips.

my last xorg.log.. see the warning from DRI .... is normal?

Can you try the patch at

http://people.freedesktop.org/~airlied/radeon_rn50_memmap.diff

And let me know ?

how may i try this?

I am going to create a .deb with the patch included but sadly there are currently some dependency problems in Edgy with the packages I need in order to recompile the driver.

Okay, a .deb which includes the patch from http://people.freedesktop.org/~airlied/radeon_rn50_memmap.diff is available from here:

http://gamesplace.info/opensource/ubuntu/ati/xserver-xorg-video-ati_6.6.2-0ubuntu3_i386.deb

Diffs and soucecode are available from here: http://gamesplace.info/opensource/ubuntu/ati/

The packages are for Edgy only.

Benjamin Herrenschmidt: The patched package froze my system when running "glxgears" ( I did not saw the gears, there was only a black screen in the window, then it froze )

Lol, sorry. I was confused.

For me, it does not freezy globally with and without your patch since I upgraded to Edgy. It would be interesting to hear from Sylvek if the patch solves the issue or not solves the issue.

But when I run glxgears it crashes using the patch and not using the patch. But I think that this is an other problem since my system does not freeze at my everyday work anymore.

ok thks for everything! .. i'm going to try your path now with basic xorg configuration.
Driver "ati" and BusID "PCI:1:0:0" only.

presently the glxgears works but i get this warning.
libGL warning: 3D driver claims to not support visual 0x4b

Ok, all of those 3d/glxgears problems are unrelated. If you have a specific problem, please open a separate report (and feel free to CC me). At this point, we are trying to chase down the long standing random system lockup issue that has been plaguing M6, M7 and radeon 7xxx users.

The patch seem indeed confirm the reported lockups with M6, M7 and radeon 7000 so far. David will probably do a new stable release of the radeon driver including it. I recommend that Ubuntu updates dapper and edgy drivers with that fix and close this bug.

since september, 18th my xorg don't crash ...

September 22, 2006. As of this day, my computer *still* crashes from this bug.

OS: Ubuntu Dapper
Video Card: Radeon Mobility M6 LY
xserver-xorg-driver-all: 7.0.0-0ubuntu45
xserver-xorg-driver-ati: 1:6.5.7.3-0ubuntu7
(newest as of today)

xorg.conf (truncated):
        Driver "ati"
        BusID "PCI:1:0:0"
        Option "DynamicClocks" "on"
...
        Identifier "Generic Monitor"
        Option "DPMS"
        HorizSync 28-49
        VertRefresh 43-72

Sylvek, what version of xorg are you using? What OS are you using? Any help would be appreciated.

The bug seems to be fixed in *Edgy*, not in Dapper. As a temporary solution you may want to disable dri.

Disabling DRI will not fix it. It will still occasionally lockup (depending on the machine and other ramdom circumstances). Ubuntu should definitely apply this patch on dapper. Dave is about to release a new stable version of the ATI driver which includes it too.

i attach my Xorg -version
i use Ubuntu Edgy under Sony VIAO Z1RMP

I just wanted to confirm that disabling DRI will NOT fix this bug. Hopefully someone can put the patched version of the ati drvers in the ubuntu repositories.

I confirm that disabling DRI do not fix this bug. ^ ^
but since i path my ati driver all works properly.

We might still be looking at different bugs here. For me (on a system with Radeon 7200), the lockups were happening quite often (most sessions within a few minutes), but disabling DRI did fix the problem entirely. No lockups at all after disabling DRI (for a few months).

>We might still be looking at different bugs here. For me (on a system with >Radeon 7200), the lockups were happening quite often (most sessions within a >few minutes), but disabling DRI did fix the problem entirely. No lockups at all >after disabling DRI (for a few months).

same here. additional, the ati driver in edgy fixed the problem without the patch.

seems that the patch solved my freezing problems in edgy

thanks martin for providing the binaries

any hope of seeing this fix in dapper?

due to a simple misunderstanding with upstream, the patch for this bug has been applied with yesterday upload of the ati driver in edgy.

Backport to Dapper of xserver-xorg-video-ati_6.6.2-0ubuntu3 fails due to dependency problem:

 -> Considering xserver-xorg-dev (>= 1:1.1.1)
      Tried versions: 1:1.0.2-0ubuntu10.4 1:1.0.2-0ubuntu10
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.

So my guess is that this fix will not make it into Dapper? I was hoping that I would not need to upgrade to a non-stable release.

The edgy package is based on X 7.1 and can't just be used 'as-is' on 7.0, but the fix itself is a simple patch that could easily be applied to dapper version of the driver

I find it hard to tell if bug #151219 is a duplicate.
151219 is linked to upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=2581

Someone more knowledgeable could confirm it is a duplicate?

> but the fix itself is a simple patch that could easily be applied to dapper version of the driver

The Xorg 7.1 code looks quite different from the 7.0 code to me. Anyhow, a stable version of the Xorg 7.0 ati driver which includes the memory map fixes has been published upstream (version 6.5.8.1). I would really appreciate it if that could be made available for Ubuntu Dapper. Seriously, I will be willing to make a charitable donation a developer's beer fund.

Can I also request that the importance of this bug be raised. This can lock up affected PCs (of which there are many in existence) frequently.

I am using Kubuntu Dapper as a platform for KDE development and something in the latest Qt release seems to trigger this lockup very frequently.

Switching to EXA accelerations helps - although EXA support seems to have many rough edges in the X.org 7.0, so much so that using it for day to day desktop work can be a little painful.

I have discussed the matter with David Airlie, who maintains the xorg ati driver. He told me that Ubuntu have added quite a number of patches to the ati driver, and it isn't a straightforward matter - for someone who is not familiar with the X code at least (ie. myself) - to find a patch in the x.org git tree and apply it to the Ubuntu version of the driver.

I did have a look at both codebases, and I really was way out of my depth.
The short story is that I upgraded to 'Edgy' where the issue has been fixed, much as I would have preferred a "safe and stable" release on my main machine.

This bug is very serious, and I strongly suggest upgrading its severity.

On Thu, 2006-11-16 at 16:29 +0000, Robert Knight wrote:
> I have discussed the matter with David Airlie, who maintains the xorg
> ati driver. He told me that Ubuntu have added quite a number of patches
> to the ati driver, and it isn't a straightforward matter - for someone
> who is not familiar with the X code at least (ie. myself) - to find a
> patch in the x.org git tree and apply it to the Ubuntu version of the
> driver.
>
> I did have a look at both codebases, and I really was way out of my depth.
> The short story is that I upgraded to 'Edgy' where the issue has been fixed, much as I would have preferred a "safe and stable" release on my main machine.
>
> This bug is very serious, and I strongly suggest upgrading its severity.

well, I've told ubuntu folks I know my feeling on the matter several
times. I beleive that they should use the latest stable driver release
in dapper too...

Ben.

I hate to sound redundant. As much as I love to use Ubuntu, I need to have Dapper functional on my Poweredge server (running ATI). Edgy doesn't provide me the LTS, so I simply can't upgrade. Sure, I can run in vesa, it's a server anyway. But at that point do I really need to run Ubuntu?

I hope the fix will applied to Dapper soon. Otherwise, what's the point of advertise that release as having "Long Term Support"?

I am afraid, as I did too before, misunderstand the meaning Ubuntu give to Long Term Support.
Please read:
https://wiki.ubuntu.com/StableReleaseUpdates

The bug persists in Dapper!

Vaio - PCG C1 MHP
Radeon Mobility M6 LY
Driver ati + dri (standard installation)
Will try non-dri and stuff soon.

Unfortunately I can't tell with which update this bug appeared, but it was in Sept. 2005.

By they way, buttons in gnome show some distortion sometimes, which seems to be related to this bug. Ever since I saw this distortion, my system is freezing every once in a while. The distortion is regular. Black or gray pixels every 10-20 pixels in both axis. I will be more specific later and try to provide a screenshot.

This really should be fixed. Especially for the server people. I have a Poweredge server as well and I can't connect to it any more after the last update. This was a Debian sarge to etch update = xf86 to xorg update, so this bug seems to be hitting not just Ubuntu.

Anyhow, I would like this to be fixed in Dapper also!
I understand long term support differently either!

PS.: It took me until now to figure out, that it was not my hardware's fault. I bought a new Laptop in the meantime because I believed otherwise and I rely on Linux.

Modified the patch from comment #83 to apply cleanly on Dapper.

> This really should be fixed. Especially for the server people.

This will most probably not be SRU'ed for Dapper, since it can be worked around using the "vesa" driver (or just disabling DRI in some cases) - which should work fine especially for server people.

For the Dapper desktop users with this problem, can you try this package? (It has the above patch)

Any Dapper users left, who can test the patched package in the previous comment?

I've had the same problem with hard lock-ups using the "ati" driver with a Radeon 9700pro on a clean install of dapper. It still froze up when I upgraded to edgy, no difference. The system completely locks up. Nothing ever appears in the logs, but the freezing is consistent. When I switched from the ati driver to the vesa driver every worked fine, video refresh sucked of course, but it worked. Switch back to the ati and I froze within 15min. Finally I just installed the fglrx driver from the xorg-driver-fglrx package which has been working fine.

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 ND [Radeon 9700 Pro]
01:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9700 Pro] (Secondary)

I applied the updated .deb two days ago, switched back to the "ati" driver from "vesa" and so far have not seen any harware lockups like when I first installed Dapper. This is my video hardware:

0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY

I had the same Problem as described above, on an updated edgy with a 7500 and the radeon driver.
But only when I've tried to start a application that uses opengl like glxgears/info when I added "load dri" to my xorg.conf.
I've found a way to circumvent crashes while anyhow using dri module.
I've found out that the module "GLcore" interferes with "dri".
"GLcoere" is not needed for opengl and direct rendering so I deactivated it and lo and behold it all works wthout crashes and 3d is working perfectly smooth.
I'am using an ati 7500 with radeon driver on a thinkpad t41.
AIGLX works stable with beryl.

> But only when I've tried to start a application that uses opengl like glxgears/info when I added "load dri" to my xorg.conf.

See bug 61137. The bug this bug report is about has been fixed in Edgy.

closing bogus component

removing dapper milestone

fixed ages ago.

dazanova, you only assign bugs to yourself if you are working on a fix for it.