Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
As for the glxgears thing, I got some output from it when I ran it with gdb from an ssh session: glxgears: vblank.c:338: driWaitForVBlank: Assertion `interval != (unsigned)-1' failed. try updating from CVS both trees, I fixed this I just can't remember which tree it went into :-) I think it was the Mesa one, I'll take a look at the DMA failure case later on .. when I'm more with awake On a side note, what kind of stuff should I put in my host.def to build a nice static debuging server? I googled for this and found a few things, but they I change the XF86Drivers line to just ati, the DriDrivers line to just mach64, define GlxBuiltInMach64 to YES and comment out DoLoadableServer line and I think that works.. I've also used the gdb mentioned in the Wiki I think to debug the normal server ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
-X starts up fine now, window manager comes up, etc. -xvinfo reports xv working, playing mpeg with mplayer confirms this. -glxinfo reports correct info -glxgears locks up. Rest of X is locked, but mouse can be moved around. I can ssh in, but can't seem to kill the X server. A reboot is required to get the screen working again. wierd is their anything in dmesg? send me a copy of it .. I've just had a game of tuxracer and it works great for me .. I've also started two glxgears side by side ... and exited them.. does gears lock up after you try to exit it or straight away? if it is on exit, I'd re-build the tree and confirm yuou have the latest 2d driver as that is what was happening me before about 8 hours ago.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
Yeah, got a couple things here. First, the dmesg. the dma test is failing. It worked fine on the old branch. This of course happens when starting X. Here's a dmesg clip: -- agpgart: Putting AGP V2 device at :00:00.0 into 2x mode agpgart: Putting AGP V2 device at :01:00.0 into 2x mode [drm] descriptor ring: cpu addr 0xcc878000, bus addr: 0xe000 [drm] mach64_do_wait_for_idle failed! GUI_STAT=0x0081 [drm] [drm] ring contents: [drm] head_addr: 0x head: 0 tail: 0 [drm] 0xe000: 0x007ffe48 0x06134000 0xcff8 0x (head) (tail) [drm] 0xe010: 0x 0x 0x 0x [drm] 0xe020: 0x 0x 0x 0x [drm] 0xe030: 0x 0x 0x 0x [drm] ... [drm] 0xe0003fd0: 0x 0x 0x 0x [drm] 0xe0003fe0: 0x 0x 0x 0x [drm] 0xe0003ff0: 0x 0x 0x 0x [drm] [drm] [drm]BM_GUI_TABLE = 0xe000 [drm] [drm] BM_FRAME_BUF_OFFSET = 0x007ff980 [drm] BM_SYSTEM_MEM_ADDR = 0xe000 [drm] BM_COMMAND = 0x [drm] [drm] BM_STATUS = 0x834860ca [drm]BUS_CNTL = 0x7b33a111 [drm] FIFO_STAT = 0x [drm]GUI_STAT = 0x0081 [drm]SRC_CNTL = 0x0f00 [drm] mach64_do_wait_for_idle failed (result=-16) [drm] [drm]AGP_BASE = 0xe000 [drm]AGP_CNTL = 0x0002003e [drm] ALPHA_TST_CNTL = 0x0470 [drm] [drm] BM_COMMAND = 0x [drm] BM_FRAME_BUF_OFFSET = 0x007ff980 [drm]BM_GUI_TABLE = 0xe000 [drm] BM_STATUS = 0x834860ca [drm] BM_SYSTEM_MEM_ADDR = 0xe000 [drm] BM_SYSTEM_TABLE = 0x4cb8 [drm]BUS_CNTL = 0x7b33a111 [drm] [drm] CLR_CMP_CLR = 0x [drm]CLR_CMP_CNTL = 0x [drm] CONFIG_CHIP_ID = 0xdc004c42 [drm] CONFIG_CNTL = 0x3f46 [drm]CONFIG_STAT0 = 0x00a10095 [drm]CONFIG_STAT1 = 0x [drm]CONFIG_STAT2 = 0x0200 [drm] CRC_SIG = 0x [drm] CUSTOM_MACRO_CNTL = 0x003c0171 [drm] [drm] DP_BKGD_CLR = 0x [drm] DP_FRGD_CLR = 0x [drm] DP_MIX = 0x00070003 [drm]DP_PIX_WIDTH = 0x01000404 [drm] DP_SRC = 0x0100 [drm] DP_WRITE_MASK = 0x [drm] DSP_CONFIG = 0x00370a09 [drm] DSP_ON_OFF = 0x0158072e [drm]DST_CNTL = 0x0023 [drm] DST_OFF_PITCH = 0x1900 [drm] [drm]EXT_MEM_CNTL = 0x64000c01 [drm] [drm] FIFO_STAT = 0x [drm] [drm] GEN_TEST_CNTL = 0x0100 [drm]GUI_CMDFIFO_DATA = 0x017c020b [drm] GUI_CMDFIFO_DEBUG = 0x00248026 [drm]GUI_CNTL = 0x0001 [drm]GUI_STAT = 0x0081 [drm] GUI_TRAJ_CNTL = 0x0023 [drm] [drm] HOST_CNTL = 0x [drm]HW_DEBUG = 0x48803800 [drm] [drm] MEM_ADDR_CONFIG = 0x0101 [drm]MEM_BUF_CNTL = 0x00382848 [drm] [drm]PAT_REG0 = 0x [drm]PAT_REG1 = 0x [drm] [drm] SC_LEFT = 0x [drm]SC_RIGHT = 0x031f [drm] SC_TOP = 0x [drm] SC_BOTTOM = 0x0a3c [drm] [drm] SCALE_3D_CNTL = 0x [drm]SCRATCH_REG0 = 0x04100400 [drm]SCRATCH_REG1 = 0x [drm] SETUP_CNTL = 0x3100 [drm]SRC_CNTL = 0x0f00 [drm] [drm]TEX_CNTL = 0x [drm] TEX_SIZE_PITCH = 0x [drm]TIMER_CONFIG = 0x [drm] [drm] Z_CNTL = 0x0110 [drm] Z_OFF_PITCH = 0x19062a20 [drm] [drm] resetting engine ... [drm] freeing data buffer memory. [drm] DMA test failed (ret=-16), using pseudo-DMA mode --- As for the glxgears thing, I got some output from it when I ran it with gdb from an ssh session: glxgears: vblank.c:338: driWaitForVBlank: Assertion `interval != (unsigned)-1' failed. I got some patchy backtrace action too: (gdb) bt #0 0x4021e031 in kill () from /lib/libc.so.6 #1 0x4018b49e in pthread_kill () from /lib/libpthread.so.0 #2 0x0006 in ?? () #3 0xb668 in ?? () #4 0x4018b454 in pthread_kill () from /lib/libpthread.so.0 #5 0x40009a00 in _dl_runtime_resolve () from /lib/ld-linux.so.2 #6 0x080515d8 in ?? () #7 0xb688 in ?? () #8 0x4018b7a3 in raise () from /lib/libpthread.so.0 #9 0x4021de1c in raise () from /lib/libc.so.6 #10 0x4021f2a7 in abort () from /lib/libc.so.6 #11 0x4021777e in __assert_fail () from /lib/libc.so.6 #12 0x4044d34a in driWaitForVBlank (priv=0x8050cd8, vbl_seq=0x40192e40, flags=4294967295, missed_deadline=0xb86b ) at vblank.c:338 #13 0x40451d2a in mach64CopyBuffer (dPriv=0x8050cd8) at mach64_ioctl.c:309 #14 0x40453887 in mach64SwapBuffers (dPriv=0x8050cd8) at mach64_screen.c:285 #15 0x4034f4a3 in driSwapBuffers
[Dri-devel] mach64-0-0-7 branch illness and snapshots..
Okay I wasn't as complete as I thought, the Mesa and the DRM I was using were from the branch but I never updated my 2d driver, it was still the old branch... so then I noticed something else which might cause problems with the snapshots When I updated and using the XFree86 from the snapshot directory, I was missing an I2C symbol, the ati driver in DRI CVS seems to need a newer version of libi2c.a, mine was from Fedora Core 1... The 2d driver builds now but 3d seems to crap it out .. it'll be a day or two until I figure it out .. I might need to get a serial console together.. (or a network).. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
When I updated and using the XFree86 from the snapshot directory, I was missing an I2C symbol, the ati driver in DRI CVS seems to need a newer version of libi2c.a, mine was from Fedora Core 1... The 2d driver builds now but 3d seems to crap it out .. it'll be a day or two until I figure it out .. I might need to get a serial console together.. (or a network).. Okay the 2D driver is now in a lot better state and should work fine ... the libi2c.a issue is still there I think.. Dave. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
