Ok, so I've applied Stephane's fixes and sample_server comes up and 
miniglxtest no longer segfaults.  However, after setting the mode, 
sample_server seems to die and wedge my display.  miniglxtest just fails 
right away with this message:

[EMAIL PROTECTED] miniglx]$ ./miniglxtest
[miniglx] probed chipset 0x4e4b
CreateNotify
Authorize - magic 1
Unknown device ID 4E4B, please report. Assuming plain R300.
Using 8 maximum texture units..
sizeof(drm_r300_cmd_header_t)=4
sizeof(drm_radeon_cmd_buffer_t)=32
Allocating 284420 bytes command buffer (max state is 11140 bytes)
*********************************WARN_ONCE*********************************
File r300_state.c function r300Enable line 516
Don't know how to enable polygon offset point/line. Help me !
***************************************************************************
MapRequest
Hang on... drawing 6 frames
Redraw event
drmRadeonCmdBuffer: -22 (exiting)
DestroyNotify

My system long indicates that radeon_do_cleanup_cp is failing when it calls 
drm_ati_pcigart_cleanup, then the card hangs.  I have to hard reboot to get 
my machine back since sample_server isn't killable.

Call Trace:
 [<a00000010000fc00>] show_stack+0x80/0xa0
                                sp=e00000b07232fbf0 bsp=e00000b0723290f8
 [<a00000010000fc50>] dump_stack+0x30/0x60
                                sp=e00000b07232fdc0 bsp=e00000b0723290e0
 [<a0000002052a9cb0>] drm_ati_pcigart_cleanup+0x1b0/0x200 [drm]
                                sp=e00000b07232fdc0 bsp=e00000b0723290a0
 [<a000000205193530>] radeon_do_cleanup_cp+0xb0/0x240 [radeon]
                                sp=e00000b07232fdc0 bsp=e00000b072329078
 [<a000000205195d50>] radeon_do_release+0x1d0/0x2e0 [radeon]
                                sp=e00000b07232fdc0 bsp=e00000b072329040
 [<a0000002051ae8b0>] radeon_driver_pretakedown+0x30/0x60 [radeon]
                                sp=e00000b07232fdc0 bsp=e00000b072329020
 [<a00000020529bd00>] drm_takedown+0x380/0xa00 [drm]
                                sp=e00000b07232fdc0 bsp=e00000b072328fc0
 [<a00000020529ecb0>] drm_release+0x910/0x1160 [drm]
                                sp=e00000b07232fdc0 bsp=e00000b072328f38
 [<a000000100140290>] __fput+0x310/0x320
                                sp=e00000b07232fe20 bsp=e00000b072328ee8
 [<a0000001001402e0>] fput+0x40/0x60
                                sp=e00000b07232fe30 bsp=e00000b072328ec8
 [<a00000010013cf00>] filp_close+0xc0/0x1a0
                                sp=e00000b07232fe30 bsp=e00000b072328e98
 [<a00000010013d130>] sys_close+0x150/0x1a0
                                sp=e00000b07232fe30 bsp=e00000b072328e20
 [<a00000010000aa60>] ia64_ret_from_syscall+0x0/0x20
                                sp=e00000b07232fe30 bsp=e00000b072328e20
 [<a000000000010640>] __kernel_syscall_via_break+0x0/0x20
                                sp=e00000b072330000 bsp=e00000b072328e20
[drm:drm_ati_pcigart_cleanup] *ERROR* no scatter/gather memory!
[drm:radeon_do_cleanup_cp] *ERROR* failed to cleanup PCI GART!
radeonfb: FIFO Timeout !
radeonfb: Idle Timeout !
radeonfb: FIFO Timeout !
radeonfb: Idle Timeout !

The above stack trace is due to a dump_stack I put in the error path right 
before "no scatter/gather memory" is printed in drm_ati_pcigart_cleanup().

Anything I should try before digging into the source a little further?

Thanks,
Jesse


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to