[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#180107: xserver-xfree86: ATI Radeon 7500: SEGV at random times, esp in xlock



On Mon, Mar 03, 2003 at 06:30:15PM -0800, Jeffrey Baker wrote:
> As requested, the stack trace:
> 
> #0  0x40077a51 in kill () from /lib/libc.so.6
> #1  0x40077872 in raise () from /lib/libc.so.6
> #2  0x40078986 in abort () from /lib/libc.so.6
> #3  0x0825137d in ddxGiveUp () at xf86Init.c:1094
> #4  0x082b86e0 in AbortServer () at utils.c:436
> #5  0x082b9985 in FatalError (f=0x85ab9e0 "Caught signal %d.  Server aborting\n")
>     at utils.c:1399
> #6  0x082628a8 in xf86SigHandler (signo=11) at xf86Events.c:1085
> #7  0x400779d8 in sigaction () from /lib/libc.so.6
> #8  0x081cefc0 in XAAPolySegment (pDrawable=0x6, pGC=0x89e45d0, nseg=0, pSeg=0x8932644)
>     at xaaSeg.c:238
> #9  0x0837c93e in miSpritePolySegment (pDrawable=0x882d880, pGC=0x89e45d0, nseg=1,
>     pSegs=0x893263c) at misprite.c:1406
> #10 0x08295fec in ProcPolySegment (client=0x87c6d70) at dispatch.c:1882
> #11 0x08293967 in Dispatch () at dispatch.c:462
> #12 0x082a34d4 in main (argc=9, argv=0xbffffdc4, envp=0xbffffdec) at main.c:454
> 
> pDrawable=0x6 in XAAPolySegment looks like a problem.  One level up
> from that, pDrawable is a 1600x1200, depth 24, bpp 32, type 0, class
> 1 drawable.

Thank you very much.  It looks like the only drivers that provide
implementations of XAAPolySegment() are glint and s3virge:

% grep -r XAAPolySegment *
glint/glint_driver.c:    "XAAPolySegment",
glint/pm2_accel.c:    XAAPolySegment(pDraw, pGC, nseg, pSeg);
glint/pm_accel.c:    XAAPolySegment(pDraw, pGC, nseg, pSeg);
glint/sx_accel.c:    XAAPolySegment(pDraw, pGC, nseg, pSeg);
glint/tx_accel.c:    XAAPolySegment(pDraw, pGC, nseg, pSeg);
s3virge/s3v_accel.c:    XAAPolySegment(pDraw, pGC, nseg, pSeg);

Therefore my guess is that problem is in XAA's internal version of this
function:

% grep -r '^XAAPolySegment(' *
xaa/xaaLine.c:XAAPolySegment(
xaa/xaalocal.h:XAAPolySegment(

And checking the CVS logs for xaaLine.c, I suspect this problem may be
fixed in XFree86 4.3.0:

 328. Add LINE_LIMIT_COORDS option to XAA to work around limited coordinate
      space for lines on Radeons (Kevin Martin)

-- 
G. Branden Robinson                |     Life is what happens to you while
Debian GNU/Linux                   |     you're busy making other plans.
branden@debian.org                 |     -- John Lennon
http://people.debian.org/~branden/ |

Attachment: pgp7Zew7LF9vp.pgp
Description: PGP signature


Reply to: