Display blanking/freezing using PCI/AGP ATI 9250

[Carey Underwood]

Binary package hint: xorg

Occasionally (estimating after 10-30 minutes) while logged in and actively working, my display will go black. Ctrl+alt+F1, etc, won't switch to a new display, ctrl+alt+backspace doesn't kill the xserver, and it will seem as though the machine is hung. I can still ssh into it from a different machine however: top shows xorg spiking the cpu, and Xorg.0.log shows a large number of messages repeating:
  (EE) RADEON(0): RADEONWaitForIdleCP: CP idle -1022
  (EE) RADEON(0): Idle timed out, resetting engine...
  (**) RADEON(0): EngineRestore (16/16)

This occurs with a Radeon 9250 128mb AGP card, as well as a Radeon 9250 128mb PCI card, freezing within 30 minutes or so. It works fine however with a (much) older Rage II PCI card, at the same resolution/bitdepth, although with no 3d acceleration working.

The machine has been working fine since dapper was in beta (including a month experiment running compiz + xgl/aiglx), failures started last week some time (sorry I can't be more specific, had other things on my mind).

It seems to be tied to interactive use somehow (it doesn't crash overnight), and I'm not running any 3d apps (although the open gl screensavers are installed; again, this occurs as I'm typing, so I don't think it's screensaver related).

[Carey Underwood (cwillu)]

Radeon 9250 PCI,
AMD Sempron 2400,
1 gig memory

Occurs with ubuntu's vanilla 386, 686 and K7 kernels, as well as a 2.6.17.ck patched kernel, all of which ran fine before, and fine now with the older video card.

Quite a few windows open in the session (Firefox's session recovery is a wonderful thing)

[Carey Underwood (cwillu)]

This one happened just lately, came back to a hung sesion after a few minutes, and the monitor was displaying a warning about refresh rate being out of range. Ctrl+alt+<-> gave me a viewable session again, and Ctrl+alt+<+> got me back to the original resolution, with no apparent ill effect.

[Carey Underwood (cwillu)]

https://bugs.freedesktop.org/show_bug.cgi?id=6111#c14

This one particular comment looks like the same bug (although the general bug on that page looks like a different issue judging from its xorg.log file).

Probably not an issue with the older kernel, as I've ran a later kernel.org version with the same problems. One commonality is the reference to the DRI Drivers from xgl.compiz.info, as I had been running xgl for a month about a month ago, and the latest batch of updates including updates to that (iirc). xgl and aiglx are still installed on my machine, but to the best of my knowledge, I'm running the normal xorg server (ps aux|grep 'x' shows xorg, not XGL or xorg-air).

[Carey Underwood (cwillu)]

Removed all XGL, AIGLX, and Compiz related packages, and forced all xorg and ati related packagesto previous versions; I haven't experienced any hangs in the last 12 hours. I'm going to give it another day, and if things are still stable, I'll let the latest xorg updates reapply and repost.

[Timo Jyrinki (timo-jyrinki)]

What's the current situation on this bug?

[AdeDidou (adelineenileda)]

Hello,

I need your help. I have used the driver fglrx but with the new version my graphic card isn't supported... so I have choice to use the driver radeon but I have still the same problem than before I installed the driver fglrx : After 2, 5 or 25 minutes (the time aren't the same each time) I have a black screen (with some time my screen say : "no signal") and I need to restart xorg (with alt+ctrl+<---).

[AdeDidou (adelineenileda)]

My configuration :
HP dx200MT with ATI Radeon 9250 PCI (Screen :Daewoo Sensy)

OS : Ubuntu Feisty

$ uname -a
Linux didou-pentium 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

$ dmesg | grep drm
[ 53.230050] [drm] Initialized drm 1.1.0 20060810
[ 53.255885] [drm] Initialized radeon 1.25.0 20060524 on minor 0
[ 58.215199] [drm] Setting GART location based on new memory map
[ 58.215867] [drm] Loading R200 Microcode
[ 58.215938] [drm] writeback test succeeded in 2 usecs
[ 761.673810] [drm] Setting GART location based on new memory map
[ 761.674712] [drm] Loading R200 Microcode
[ 761.674779] [drm] writeback test succeeded in 2 usecs
[ 806.227550] [drm] Setting GART location based on new memory map
[ 806.228481] [drm] Loading R200 Microcode
[ 806.228549] [drm] writeback test succeeded in 2 usecs
[ 1479.968053] [drm] Setting GART location based on new memory map
[ 1479.969205] [drm] Loading R200 Microcode
[ 1479.969275] [drm] writeback test succeeded in 1 usecs
[ 1613.605317] [drm] Setting GART location based on new memory map
[ 1613.606414] [drm] Loading R200 Microcode
[ 1613.606485] [drm] writeback test succeeded in 1 usecs

$ sudo scanpci
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x2570
 Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface
pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x2572
 Intel Corporation 82865G Integrated Graphics Controller
pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x24d2
 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1
pci bus 0x0000 cardnum 0x1d function 0x01: vendor 0x8086 device 0x24d4
 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2
pci bus 0x0000 cardnum 0x1d function 0x02: vendor 0x8086 device 0x24d7
 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3
pci bus 0x0000 cardnum 0x1d function 0x03: vendor 0x8086 device 0x24de
 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4
pci bus 0x0000 cardnum 0x1d function 0x07: vendor 0x8086 device 0x24dd
 Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller
pci bus 0x0000 cardnum 0x1e function 0x00: vendor 0x8086 device 0x244e
 Intel Corporation 82801 PCI Bridge
pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x24d0
 Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge
pci bus 0x0000 cardnum 0x1f function 0x01: vendor 0x8086 device 0x24db
 Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x24d3
 Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller
pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x5960
 ATI Technologies Inc RV280 [Radeon 9200 PRO]
pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x5940
 ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary)
pci bus 0x0001 cardnum 0x01 function 0x00: vendor 0x13f6 device 0x0111
 C-Media Electronics Inc CM8738
pci bus 0x0001 cardnum 0x02 function 0x00: vendor 0x14f1 device 0x2f01
 Conexant Device unknown
pci bus 0x0001 cardnum 0x08 function 0x00: vendor 0x8086 device 0x1050
 Intel Corporation 82562EZ 10/100 Ether...

[AdeDidou (adelineenileda)]

Created an attachment (id=9885)
xorg.conf

[AdeDidou (adelineenileda)]

Created an attachment (id=9886)
Xorg.0.log.old (with a crash)

[AdeDidou (adelineenileda)]

Thanks for your help...

Adeline

[Timo Jyrinki (timo-jyrinki-hut)]

Not sure if it helps in this particular problem, but you might try to edit your xorg.conf and comment out / remove the line that says 'Load "dri"'. Then you don't have accelerated 3D, but it'd be worth trying out if it helps in this.

This might be a duplicate of bug 6111, but there's a lot of noise (unrelated to the original reporter's problem) there. A hint from there, which is probably unrelated to you since you already have a PCI card, is to add Option "BusType" "PCI" to the Driver-section.

[Glisse (glisse)]

What driver do you want to use ? Your log say you use radeon open source driver,
your message say you want to use fglrx. We do not provide support for fglrx.
Because we can't and don't want to. If you want to try with the open source
driver please try to strip down your card configuration to the following:

Section "Device"
 Identifier "HIS (Ati) Radeon 9250 PCI"
 BusID "PCI:1:0:0"
 Driver "radeon"
 Option "GARTSize" "64"
 Option "EnablePageFlip" "1"
 Option "ColorTiling" "1"
EndSection

[Timo Jyrinki (timo-jyrinki-hut)]

(In reply to comment #6)
> What driver do you want to use ? Your log say you use radeon open source
> driver,

Like it was said, she was using fglrx before because the hang problems. Now that ATI dropped support for 8500-9250 series of cards, it's again being tried to use open source drivers, but the old hanging/blackscreen problem persists.

So, despite the fglrx mentions, this report is about the open source driver and wishes for instructions how to get it not to hang.

Anyway, indeed in addition to my hint, it might be worthwhile to "clean" the driver section to just include the Identifier, Driver and BusID, which are the only ones that should be really needed. Just in case some of the options cause any trouble.

Also, Driver can be just "ati" instead of "radeon", though it should not matter.

[AdeDidou (adelineenileda)]

(In reply to comment #5)
> add Option "BusType"
> "PCI" to the Driver-section.
>
I add it :
Section "Device"
 Identifier "HIS (Ati) Radeon 9250 PCI"
 BusID "PCI:1:0:0"
 Driver "radeon"
 Option "BusType" "PCI"
 Option "AccelMethod" "XAA" # Use XFree86 Acceleration Architecture
 Option "AccelDFS" "1" # mettez à 0 si vous avez une carte AGP
 Option "GARTSize" "64"
#Fait sauter mon ordinateur Option "RingSize" "8"
 Option "BufferSize" "2"
 Option "EnablePageFlip" "1" # Enable page flipping for 3D apps
 Option "ColorTiling" "1"
 Option "EnableDepthMoves" "yes"
 Option "UseFBDev" "false"
 Option "RenderAccel" "true" # Enable the hardware render acceleration
 Option "mtrr" "on"
 Option "SubPixelOrder" "none"
 Option "DPMS"
 Option "DynamicClocks" "on"
# Option "VideoOverlay" "on"
# Option "OpenGLOverlay" "off"
EndSection

For the moment it's good but I need to try more time

Thanks

And sorry for my bad English... Yes I want to use the oepn driver ;)

[Timo Jyrinki (timo-jyrinki)]

Setting as confirmed, there's an upstream bug with a similar problem with ATI 9250 PCI.

[Timo Jyrinki (timo-jyrinki)]

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

[AdeDidou (adelineenileda)]

> For the moment it's good but I need to try more time
>
>
No it's not the solution, I have the same problem even if I add Option "BusType" "PCI"...

Have you a other proposition ?

When I see the xorg.log.0, I see that the driver radeon support the 9250 (AGP) but I don't see that it support the 9250 (PCI) it's wright or not ?

Thanks

[Glisse (glisse)]

Did you try with device section as proposed in comment 6 ?
Please try this, you really have too much options; so it's
hard to understand from where the issue likely come.

Btw i am not sure i fully understand your issue, you have
a black screen after some times, is this after some times
of inactivity ? If so then this likely somethings related
to dpms and failing to wake up the card or the screen.

Anyway the fact that ctr-alt-backspace restart properly your
xserver likely mean that the isn't lockup at all.

[Timo Jyrinki (timo-jyrinki-hut)]

(In reply to comment #9)
> Have you a other proposition ?

1. Did you try to comment out the Option "dri" line from Section "Module"?

2. Also, if it would be a problem with some screen power saver, you could, depending on a bit on the environment you are using, disable display power management. In GNOME, it's System->Preferences->Power Manager. There set the "Put display to sleep when inactive for:" to "Never". Though as it seems it happens while you're working (?) this is probably not the reason.

3. Cleaning the amount of options, like stated.

But really, I'd guess only the option 1 has the real possibility to fix the problem at the moment, but all are worth trying anyway.

There's a somewhat similar case at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/58448 , though there ctrl-alt-backspace does not work.

[AdeDidou (adelineenileda)]

(In reply to comment #10)
> Did you try with device section as proposed in comment 6 ?

Oki, now I have :

Section "Device"
 Identifier "HIS (Ati) Radeon 9250 PCI"
 BusID "PCI:1:0:0"
 Driver "radeon"
 Option "BusType" "PCI"
 Option "GARTSize" "64"
 Option "EnablePageFlip" "1" # Enable page flipping for 3D apps
 Option "ColorTiling" "1"
#Fait sauter mon ordinateur Option "RingSize" "8"
# Option "AccelMethod" "XAA" # Use XFree86 Acceleration Architecture
# Option "AccelDFS" "1" # mettez à 0 si vous avez une carte AGP
# Option "BufferSize" "2"
# Option "EnablePageFlip" "1" # Enable page flipping for 3D apps
# Option "ColorTiling" "1"
# Option "EnableDepthMoves" "yes"
# Option "UseFBDev" "false"
# Option "RenderAccel" "true" # Enable the hardware render acceleration
# Option "mtrr" "on"
# Option "SubPixelOrder" "none"
# Option "DPMS"
# Option "DynamicClocks" "on"
# Option "VideoOverlay" "on"
# Option "OpenGLOverlay" "off"
EndSection

> Btw i am not sure i fully understand your issue, you have
> a black screen after some times, is this after some times
> of inactivity ?

This is after some times of activity OR inactivity...

[AdeDidou (adelineenileda)]

(In reply to comment #11)
> (In reply to comment #9)
> > Have you a other proposition ?
>
> 1. Did you try to comment out the Option "dri" line from Section "Module"?
>

When I comment this line I have not crash... but not 3D too.

> 2. Also, if it would be a problem with some screen power saver, you could,
> depending on a bit on the environment you are using, disable display power
> management. In GNOME, it's System->Preferences->Power Manager. There set the
> "Put display to sleep when inactive for:" to "Never". Though as it seems it
> happens while you're working (?) this is probably not the reason.
>

I have already this configuration.

> 3. Cleaning the amount of options, like stated.
>

I have clean the amount of options but if I load dri I have still crashes...

> There's a somewhat similar case at
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/58448 ,
> though there ctrl-alt-backspace does not work.
>

I don't understand all of this repport (I am french...)

[Timo Jyrinki (timo-jyrinki-hut)]

Changing summary to include the information that this is DRI related.

> When I comment this line I have not crash... but not 3D too.

Ok, then it is DRI related definitely.

> > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/58448 > > I don't understand all of this repport (I am french...)

No worries, there is really no new information there, except that someone claims that with some older drivers it works for him. It's rather uncertain if it's the same problem, though, as most people complaining about this are using AGP card.

I don't know further options other than to leave the 3D disabled or try the latest development versions in case you want to provide further information on whether the problem has been finally fixed or not. Basically the git repositories from git://anongit.freedesktop.org/git/mesa/drm , git://anongit.freedesktop.org/git/mesa/mesa and git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati contain the latest kernel DRM module, DRI modules and the video driver. For the first two, there are some compilation + installation instructions at http://dri.freedesktop.org/wiki/Building which I just updated a bit. I would guess that the third one (the normal DDX video driver) is not needed since this is DRI related.

[Michel-tungstengraphics (michel-tungstengraphics)]

(In reply to comment #14)
> I would guess that the third one (the normal DDX video driver) is not needed
> since this is DRI related.

DRI issues can be caused by the DDX driver.

Does the problem also happen without Option "GARTSize"?

[AdeDidou (adelineenileda)]

> Does the problem also happen without Option "GARTSize"?
>

I have try to uncomment Option "GARTSize" but I have a crash too....

[AdeDidou (adelineenileda)]

> I don't know further options other than to leave the 3D disabled or try the
> latest development versions in case you want to provide further information on
> whether the problem has been finally fixed or not. Basically the git
> repositories from git://anongit.freedesktop.org/git/mesa/drm ,
> git://anongit.freedesktop.org/git/mesa/mesa and
> git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati contain the latest
> kernel DRM module, DRI modules and the video driver. For the first two, there
> are some compilation + installation instructions at
> http://dri.freedesktop.org/wiki/Building which I just updated a bit.

I try to do this but T have a problem whith the compilation of 3D Mesa : see the attachement please....

[AdeDidou (adelineenileda)]

Created an attachment (id=9932)
Error Make Mesa 3D

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Adeline, since you're using Ubuntu, you might find some prebuilt packages on https://wiki.ubuntu.com/XorgOnTheEdge which you can try, before you try compiling everything yourself.

[agd5f (agd5f)]

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

[agd5f (agd5f)]

Does this problem persist with a more recent version of the radeon driver (ati 6.7.19x or git master) or radeon drm (git master)?

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

From the report on https://bugs.launchpad.net/bugs/114520, 6.7.196 is different and somewhat better.

[Tormod Volden (tormodvolden)]

cwillu, can you still reproduce this bug on Ubuntu 7.10 or Hardy?

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Mike from the above Ubuntu bug reports that 6.7.196 works fine after a cold start, but not after a reboot.

[Probablement (probablement)]

Hi there,
I have the exact same problem as Adeline under Debian etch with Xorg 7.1.1 (ati 6.6.3 as far as I can tell, using driver radeon). I will try to disable DRI.

(II) RADEON(0): [dri] Found DRI library version 1.2.0 and kernel module version 1.25.0

[Carey Underwood (cwillu)]

Seems to be working fine since feisty; I've picked up another xorg bug in gutsy, but I don't think it's related.

[Timo Aaltonen (tjaalton)]

Thanks, closing the bug!

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Mike reported that with the newest drm modules, it now works fine all the time.

[Benjamin-close (benjamin-close)]

Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Unless Adeline disagrees, I guess this bug can be closed now? It seems to be fixed in both the radeon driver and drm.

[agd5f (agd5f)]

closing, please re-open if there are still issues.

[Gareth Bult (gareth-encryptec)]

I have the exact same problem on Hardy with an integrated Radeon 200XP.
I'd supply more info, but the problem is 100% identical and it's a fresh install / upgrade from feisty.