[Bug 3862] New: Seg. fault with r128 driver

2005-07-24 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to
   
the URL shown below and enter yourcomments there. 
   
https://bugs.freedesktop.org/show_bug.cgi?id=3862  
 
   Summary: Seg. fault with r128 driver
   Product: DRI
   Version: XOrg 6.7.0
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: libGL
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]


Dell 4550, ATI-Rage card and r128 driver. Xorg installed from Debian unstable.
DRM-modules installed from fresh snapshots at
http://dri.freedesktop.org/snapshots/ : 
http://dri.freedesktop.org/snapshots/common-20050718-linux.i386.tar.bz2 
http://dri.freedesktop.org/snapshots/rage128-20050718-linux.i386.tar.bz2

Installation was ok. Further X-launch reported no problem:
(II) R128(0): [drm] created r128 driver at busid pci::01:00.0
(II) R128(0): [dri] Visual configs initialized

But 'glxinfo' yielded following:

libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x30
Violación de segmento

(so, segmentation fault)
My .drirc is simple driconf/driconf

The output of 'gdb /usr/X11R6/bin/glxinfo' after 'run' and 'bt' is:
#0  0xb7976180 in driSetTextureSwapCounterLocation (heap=0x0,
counter=0x8051f24) at ../common/texmem.c:652
#1  0xb7979cb6 in r128CreateContext (glVisual=0x804ed18,
driContextPriv=0x804fd20, sharedContextPrivate=0x0) at r128_context.c:175
#2  0xb79775b0 in driCreateNewContext (dpy=0x804d008, modes=0x804ed18,
render_type=0, sharedPrivate=0x0, pctx=0x8050eac)
at ../common/dri_util.c:1059
#3  0xb7f260de in DriverCreateContextWrapper () from /usr/lib/libGL.so.1
#4  0xb7f2650d in CreateContext () from /usr/lib/libGL.so.1
#5  0xb7f2670e in glXCreateContext () from /usr/lib/libGL.so.1
#6  0x0804901a in ?? ()
#7  0x0804d008 in ?? ()
#8  0x080507e8 in ?? ()
#9  0x in ?? ()
#10 0x0001 in ?? ()
#11 0x0064 in ?? ()
#12 0x0064 in ?? ()
#13 0x in ?? ()
#14 0x0018 in ?? ()
#15 0x0001 in ?? ()
#16 0x0804e2a8 in ?? ()
#17 0x280a in ?? ()
#18 0xbae0 in ?? ()

I can give any log-output that you consider relevant  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: X300SE PCI-E freezes

2005-07-24 Thread Alex Deucher
On 7/24/05, Torbjörn Söderstedt [EMAIL PROTECTED] wrote:
 Hello,
 
 I tried the driver on my X300SE PCI-E card, but when I start the X
 server all I get is a black screen. To make the driver recognise my card
 at all, I added it to the pciids as a rv350 card (although it really
 should be rv370).
 
 Kernel and Xorg logs are attached. Because I don't have much kernel
 hacking experience, I don't really know where to start. I'm prepared to
 devote some time for this, so please tell me what I can do to help.
 

PCIE is not currently working.  So for the moment, PCIE cards will not
work.  What you can try is setting up the card with the fglrx driver
and getting that working then use the radeon register dump scripts in
r300 cvs to dump the PCIE config and then compare that to how the regs
get set up in the open drm.

Alex

 
 :02:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
 device 5b60 (prog-if 00 [VGA])
 Subsystem: C.P. Technology Co. Ltd: Unknown device 2089
 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: 0x08 (32 bytes)
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at d000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at be00 [size=256]
 Region 2: Memory at df8f (32-bit, non-prefetchable) [size=64K]
 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] #10 [0001]
 Capabilities: [80] Message Signalled Interrupts: 64bit+
 Queue=0/0 Enable-
 Address:   Data: 
 
 :02:00.1 Display controller: ATI Technologies Inc: Unknown device 5b70
 Subsystem: C.P. Technology Co. Ltd: Unknown device 2088
 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-
 Region 0: Memory at df8e (32-bit, non-prefetchable)
 [disabled] [size=64K]
 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] #10 [0001]
 
 AMD64 Ubuntu Hoary
 Linux 2.6.10
 
 Regards,
 Torbjörn Söderstedt
 
 
 



---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 3862] Seg. fault with r128 driver

2005-07-24 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to
   
the URL shown below and enter yourcomments there. 
   
https://bugs.freedesktop.org/show_bug.cgi?id=3862  
 




--- Additional Comments From [EMAIL PROTECTED]  2005-07-25 07:40 ---
Please attach (as opposed to paste) the full X server log and configuration 
files.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-users] X hangs when starting glxgears on r350

2005-07-24 Thread Roland Scheidegger

Bellido Nicolas wrote:

Hi all,

I have a Radeon 9800Pro that I'm trying to get working with the R300 tree on 
my Gentoo box.


I'm running a 2.6.12-gentoo-r4 kernel with the X11 6.8.99.15 ebuild.
As I saw a post recently on the dri-devel list, I built DRI and Mesa from CVS.

When the radeon module is loaded, i get in the kernel logs:

Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT880 chipset
agpgart: AGP aperture is 128M @ 0xe000
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16
[drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc 
Radeon R350 [Radeon 9800 Pro]


This is just a shot in the dark, have you built the drm module too? The 
r300 driver needs a new version too. I don't know what would happen if 
you don't build it however, but it certainly wouldn't work.
CC to dri-devel as the r300 driver doesn't check correctly for the drm 
version as far as I can see. The version should have been bumped in the 
drm when support for r300 driver was added I guess (along with the date 
and version comments in radeon_drv.h).


Roland


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-users] X hangs when starting glxgears on r350

2005-07-24 Thread Bellido Nicolas
On Monday 25 July 2005 00:47, Roland Scheidegger wrote:
 Bellido Nicolas wrote:
  When the radeon module is loaded, i get in the kernel logs:
 
  Linux agpgart interface v0.101 (c) Dave Jones
  agpgart: Detected VIA KT880 chipset
  agpgart: AGP aperture is 128M @ 0xe000
  [drm] Initialized drm 1.0.0 20040925
  ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16
  [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc
  Radeon R350 [Radeon 9800 Pro]

 This is just a shot in the dark, have you built the drm module too? The
 r300 driver needs a new version too. I don't know what would happen if
 you don't build it however, but it certainly wouldn't work.

That's the version string I have in radeon_drv.c:

$ grep 20050311 linux-core/radeon_drv.h
#define DRIVER_DATE 20050311

Checked out yesterday from drm cvs on freedesktop.org.

In case it helps, i just insmoded the drm module with debug=1.
Here are the last lines ok kmsg.

[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 236
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=13 s=0 e=88 d=0
[drm:radeon_cp_dispatch_indirect] indirect: buf=13 s=0x0 e=0x58
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=13 s=88 e=104 d=1
[drm:radeon_cp_dispatch_indirect] indirect: buf=13 s=0x58 e=0x68
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 237
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=14 s=0 e=176 d=0
[drm:radeon_cp_dispatch_indirect] indirect: buf=14 s=0x0 e=0xb0
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=14 s=176 e=192 d=1
[drm:radeon_cp_dispatch_indirect] indirect: buf=14 s=0xb0 e=0xc0
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 238
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=15 s=0 e=124 d=0
[drm:radeon_cp_dispatch_indirect] indirect: buf=15 s=0x0 e=0x7c
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=15 s=128 e=144 d=1
[drm:radeon_cp_dispatch_indirect] indirect: buf=15 s=0x80 e=0x90
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 239
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=16 s=0 e=108 d=0
[drm:radeon_cp_dispatch_indirect] indirect: buf=16 s=0x0 e=0x6c
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=16 s=112 e=128 d=1
[drm:radeon_cp_dispatch_indirect] indirect: buf=16 s=0x70 e=0x80
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] pid=9733, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1
[drm:drm_lock] 3 (pid 9733) requests lock (0x0001), flags = 0x
[drm:drm_lock] 3 has lock
[drm:drm_ioctl] pid=9733, cmd=0x40106450, nr=0x50, dev 0xe200, auth=1
[drm:radeon_cp_cmdbuf] RADEON_CMD_SCALARS2
[drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at e08fa024
[drm:drm_ioctl] ret = ffea
[drm:drm_ioctl] pid=9684, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1
[drm:drm_lock] 1 (pid 9684) requests lock (0x0003), flags = 0x
[drm:drm_lock] 1 has lock
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] ret = fff0
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 240
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=17 s=0 e=544 d=0
[drm:radeon_cp_dispatch_indirect] indirect: buf=17 s=0x0 e=0x220
[drm:drm_ioctl] pid=9684, cmd=0xc010644d, nr=0x4d, dev 0xe200, auth=1
[drm:radeon_cp_indirect] indirect: idx=17 s=544 e=560 d=1
[drm:radeon_cp_dispatch_indirect] indirect: buf=17 s=0x220 e=0x230
[drm:drm_ioctl] pid=9684, cmd=0x6444, nr=0x44, dev 0xe200, auth=1
[drm:radeon_cp_idle] 
[drm:radeon_do_cp_idle] 
[drm:drm_ioctl] ret = fff0
[drm:drm_ioctl] pid=9684, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1
[drm:radeon_freelist_get] done_age = 240
[drm:drm_ioctl] pid=9684,