driver problem without lock held

2003-11-11 Thread Jason
Here is the error:

drm0: ATI Radeon QL R200 8500 LE port 0xa000-0xa0ff mem 
0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
error: [drm:radeon_unlock] *ERROR* Process 512 using kernel context 0

Now are there any suggestions on what is causing this or how to fix 
this?  I have a nforce2 epox 8rda, freebsd 5.1, and cvsuped and did a 
buildworld today.
Thanks,
Jason

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: driver problem without lock held

2003-11-11 Thread Eric Anholt
On Mon, 2003-11-10 at 21:10, Jason wrote:
 Here is the error:
 
 drm0: ATI Radeon QL R200 8500 LE port 0xa000-0xa0ff mem 
 0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
 info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
 error: [drm:radeon_unlock] *ERROR* Process 512 using kernel context 0
 
 Now are there any suggestions on what is causing this or how to fix 
 this?  I have a nforce2 epox 8rda, freebsd 5.1, and cvsuped and did a 
 buildworld today.
 Thanks,
 Jason

This error has been reported by both FreeBSD and Linux users for several
months.  Does it prevent the DRI from initializing?   Looks like it
should.  Under what circumstances do you get this error?

-- 
Eric Anholt[EMAIL PROTECTED]  
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: driver problem without lock held

2003-11-11 Thread John Baldwin

On 11-Nov-2003 Jason wrote:
 Here is the error:
 
 drm0: ATI Radeon QL R200 8500 LE port 0xa000-0xa0ff mem 
 0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
 info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
 error: [drm:radeon_unlock] *ERROR* Process 512 using kernel context 0
 
 Now are there any suggestions on what is causing this or how to fix 
 this?  I have a nforce2 epox 8rda, freebsd 5.1, and cvsuped and did a 
 buildworld today.

That is an issue in the radeon DRM driver.  You can try asking on the
DRI lists.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: driver problem without lock held

2003-11-11 Thread Jason
Eric Anholt wrote:

On Mon, 2003-11-10 at 21:10, Jason wrote:
 

Here is the error:

drm0: ATI Radeon QL R200 8500 LE port 0xa000-0xa0ff mem 
0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
error: [drm:radeon_unlock] *ERROR* Process 512 using kernel context 0

Now are there any suggestions on what is causing this or how to fix 
this?  I have a nforce2 epox 8rda, freebsd 5.1, and cvsuped and did a 
buildworld today.
Thanks,
Jason
   

This error has been reported by both FreeBSD and Linux users for several
months.  Does it prevent the DRI from initializing?   Looks like it
should.  Under what circumstances do you get this error?
 

It does prevent it, but I believe it is caused by not preloading agp or 
not having the agp module in the kernel.  No matter what I did before 
the last update on drm, the error was always produced as far as I can 
remember.  I did some work on the config files, and now I have some 
hardware 3d acceleration and the error is gone.  I have to use option 
ForcePCIMode, but it is better than nothing.  So tell all those other 
people in need of help to try this as well as preload the radeon.ko 
module.  Here are some important snips of various stuff:

dmesg:
agp0: NVIDIA nForce2 AGP Controller mem 0xe800-0xebff at 
device 0.0 on pci0
pci0: memory, RAM at device 0.1 (no driver attached)
pci0: memory, RAM at device 0.2 (no driver attached)
pci0: memory, RAM at device 0.3 (no driver attached)
pci0: memory, RAM at device 0.4 (no driver attached)
pci0: memory, RAM at device 0.5 (no driver attached)

I noticed the linux agp driver from nvidia uses mem controllers 1 and 
2.  The bsd driver also mentions it, but as you can see something is not 
playing nice.  I believe this is related to me not having agpgart, only 
pcigart.  Please let me know what you think.  Matthew N. Dodd(mdodd) 
[EMAIL PROTECTED] was kind enough to port the linux agp driver, but 
last time I checked he has no nforce boards so he can do no more to help 
me out on this issue.  If only he had one.  Maybe you could check in 
with him to see if he knows the mem controllers are causing some agp 
problems?

info: [drm] AGP at 0xe800 64MB
info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
What are the buffers that normally equal 8MB for?  The ring, 
vertex/inderect, and agptextures are not in any documention I found, but 
I may not have been looking in the right places.  I can guess at 
agptextures, but its default was only 5MB.  Will setting AGPSize or 
other options larger than default help performance?
Thanks,
Jason

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: FreeBSD 5.1 i386 [ELF] 
Build Date: 20 October 2003
Before reporting problems, check http://www.XFree86.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/XFree86.0.log, Time: Tue Nov 11 22:09:26 2003
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout XFree86 Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to 
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
(**) RgbPath set to /usr/X11R6/lib/X11/rgb
(**) ModulePath set to /usr/X11R6/lib/modules
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on freebsd
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,01e0 card , rev a2 class 06,00,00 hdr 80
(II) PCI: 00:00:1: chip 10de,01eb card 1695,1000