I recompiled a static Xserver so that could get a backtrace inside the
driver. This is the result:
Program received signal SIGSEGV, Segmentation fault.
0x080532e3 in SavageHelpSolidROP (pScrn=0x8624270, fg=0xbffff724, pm=-1,
rop=0xbffff728) at savage_accel.c:758
758 pm &= infoRec->FullPlanemask;
(gdb) bt
#0 0x080532e3 in SavageHelpSolidROP (pScrn=0x8624270, fg=0xbffff724, pm=-1,
rop=0xbffff728) at savage_accel.c:758
#1 0x080636e1 in SAVAGEDRISetupForSolidFill (pScrn=0x8624270, color=0, rop=0,
planemask=4294967295) at savage_dri.c:1956
#2 0x08062e87 in SAVAGEDRIInitBuffers (pWin=0x87dd650, prgn=0x87e1350,
index=0) at savage_dri.c:1676
#3 0x0849ee66 in DRIWindowExposures (pWin=0x87dd650, prgn=0x87e1350,
bsreg=0x0) at dri.c:1569
#4 0x081c90f2 in miHandleValidateExposures (pWin=0x87dd948) at miwindow.c:468
#5 0x0814f8c1 in MapWindow (pWin=0x87dd650, client=0x87588b8) at window.c:2841
#6 0x08126641 in ProcMapWindow (client=0x87588b8) at dispatch.c:688
#7 0x08125e9c in Dispatch () at dispatch.c:450
#8 0x0813d3d4 in main (argc=11, argv=0xbffffd84, envp=0xbffffdb4)
at main.c:435
Apperently the DRI code in the savage driver uses accel functions even
if acceleration is disabled. Maybe you can try disabling individual XAA
acceleration functions. See the XF86Config-4 manual page for details.
There are lots of options like XaaNoCPUToScreenColorExpandFill.
Felix
On Sat, 20 Dec 2003 17:25:55 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 02:58 PM 20/12/2003, Felix Kühling wrote:
>
> >We had a similar problem with the 2D driver on the savage-1_0_0-branch.
> >Accelerated stuff worked just fine for me but direct frame buffer access
> >was broken. It turned out to be quite simple to fix. However, this fix
> >didn't work for Maximo, so I suspect that on Savage4 either 2D
> >acceleration is broken with tiling or tiling works differently and
> >direct frame buffer was still broken.
> >
> >Maximo, you can find out which of the above is true by disabling 2D
> >acceleration and see if direct fb access works. Maybe disabling 2D accel
> >would be a workaround until we fix the real problem.
>
> I tried to use the "NoAccel" option, with this option the 2D is not
> corrupted but when i try to run glxgears the X server go back to the shell
> prompt and it doesn't show any error.
>
> bye.
>
>
> Rafael Máximo
------------ __\|/__ ___ ___ -------------------------
Felix ___\_e -_/___/ __\___/ __\_____ You can do anything,
Kühling (_____\Ä/____/ /_____/ /________) just not everything
[EMAIL PROTECTED] \___/ \___/ U at the same time.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
