Re: [Dri-devel] Crazy radeon problem

2003-02-13 Thread Keith Whitwell


So, in summary, I have no idea what is going on. X internals are a bit
over my head at this point. This seems to have been triggered by a
DRI-related hardware lock, but please also note that the above (current
state of things) happens with 'radeon' even when DRI is not being
loaded!


Does powering the machine down  restarting fix this?  (as opposed to a 
reboot?)  I've seen radeons get into a state where unplugging the power cable 
was the only way to restore them, but only when I was first bringing up the 
driver - but worth a try.

Keith




---
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] Crazy radeon problem

2003-02-11 Thread Dan Burcaw
Hi all,

I've just recently subscribed and never posted, so I'll give a quick
introduction of myself. I work for Terra Soft Solutions and am the
lead developer of Yellow Dog Linux.  This is a rpm-based Linux distro
for PowerPC microprocessors.  We tend to track Red Hat fairly closely
and our main hardware platform is Apple machines.

I apologize in advanced for the long-winded nature of this message.
For the last several months we've been tracking XFree86 4.3 development
and I've been using a Apple Power Mac with Radeon 7500 as
my primary workstation.

Recently, I got DRI working on this machine based upon Mike Harris'
4.2.99.4 packages in Red Hat's Rawhide.  I got very good performance but
did find some problems.  Of note, every time I changed to a virtual
console and then switched back to X, the video hardware locked up,
forcing a reboot (or power down).  This is DRI related.. as I can change
consoles just fine using 'fbdev'.

I was able to reproduce this several times and reported it to Michel
Dänzer.  However, on the last time it happened, after rebooting
when I started X, I obtained the following strange artifacts:

http://stage.terraplex.com/~dburcaw/radeon.jpg

Note that the X server does not crash, but the system becomes unusable
at the console.  Even switching back to the virtual consoles yields
a very similar display.

Now, after a while of using console and 'fbdev', I decided to try
again... instead of the artifacts above (which happened consistently 
even after reboots), the X server crashes with:


(II) Loading sub module radeon
(II) LoadModule: radeon
(II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) resource ranges after probing:
[0] -1  0   0x - 0x (0x1) MX[B]
[1] -1  0   0x - 0x (0x1) MX[B]
[2] -1  0   0xf520 - 0xf53f (0x20) MX[B]
[3] -1  0   0x80081000 - 0x80081fff (0x1000) MX[B]
[4] -1  0   0x80082000 - 0x80082fff (0x1000) MX[B]
[5] -1  0   0x8000 - 0x8007 (0x8) MX[B]
[6] -1  0   0x9002 - 0x9003 (0x2) MX[B](B)
[7] -1  0   0x9000 - 0x9000 (0x1) MX[B](B)
[8] -1  0   0x9800 - 0x9fff (0x800) MX[B](B)
[9] -1  0   0x8008 - 0x8008007f (0x80) MX[B]
[10] 0  0   0x000a - 0x000a (0x1) MS[B]
[11] 0  0   0x000b - 0x000b7fff (0x8000) MS[B]
[12] 0  0   0x000b8000 - 0x000b (0x8000) MS[B]
[13] -1 0   0x - 0x (0x1) IX[B]
[14] -1 0   0x - 0x (0x1) IX[B]
[15] -1 0   0x0400 - 0x04ff (0x100) IX[B](B)
[16] -1 0   0x0400 - 0x047f (0x80) IX[B]
[17] 0  0   0x03b0 - 0x03bb (0xc) IS[B]
[18] 0  0   0x03c0 - 0x03df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module vgahw
(II) LoadModule: vgahw
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor=The XFree86 Project
compiled for 4.2.99.901, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.6
(II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03b0, hwp-PIOOffset is
0x
(II) RADEON(0): PCI bus 0 card 16 func 0
(II) RADEON(0): here 0
(II) UnloadModule: ati
(II) UnloadModule: vgahw
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(II) UnloadModule: radeon
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found


You will note that I am now running 4.2.99.901, and 'radeon' still
doesn't work.  After the artifacts went away, the above logging also
occurred with 4.2.99.4.

I have managed to debug things a bit and found that radeon_drv.o is 
failing due to this condition being met in radeon_driver.c:

if (xf86RegisterResources(info-pEnt-index, 0, ResExclusive))
goto fail;

(in function Bool RADEONPreInit())

Compiling with DEBUG=1, yields some interesting (but foreign to me)
messages from xf86RegisterResources():

(II) Failed Resources after driver initialization for Entity: 0
[0] 0   0   0x0400 - 0x04ff (0x100) I


So, in summary, I have no idea what is going on. X internals are a bit
over my head at this point. This seems to have been triggered by a
DRI-related hardware lock, but please also note that the above (current
state of things) happens with 'radeon' even when DRI is not being
loaded!

I would appreciate any ideas that you all  might have as to what the
problem may be or where to go next in debugging this.

Regards,
Dan Burcaw
[EMAIL PROTECTED]





---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel