Bug 598029

Summary: [abrt] crash in xorg-x11-server-Xorg-1.8.0-12.fc13: raise: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: airlied, bskeggs, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:21f7b349bc7317059ea9fdd92bcea7b8f21a3243, btparsed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 17:09:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Xorg.0.log
none
recent dmesg
none
messages from the date of the crash none

Description Dan Horák 2010-05-31 09:41:42 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-gZHS5b/database -nolisten tcp vt1
component: xorg-x11-server
crash_function: raise
executable: /usr/bin/Xorg
global_uuid: 21f7b349bc7317059ea9fdd92bcea7b8f21a3243
kernel: 2.6.33.4-95.fc13.i686.PAE
package: xorg-x11-server-Xorg-1.8.0-12.fc13
rating: 4
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Dan Horák 2010-05-31 09:41:44 UTC
Created attachment 418227 [details]
File: backtrace

Comment 2 Dan Horák 2010-05-31 09:46:08 UTC
Created attachment 418230 [details]
Xorg.0.log

Comment 3 Matěj Cepl 2010-05-31 09:54:39 UTC
#9  <signal handler called>
No symbol table info available.
#10 0x00679e3a in NVAccelUploadM2MF (pdpix=0x972d618, x=392, y=362, w=468, 
    h=60, src=0x0, src_pitch=1872) at /usr/include/bits/string3.h:52
        line_count = <value optimized out>
        i = <value optimized out>
        dst = <value optimized out>
        pNv = 0x96f6f40
        m2mf = 0x96e9f40
        cpp = 4
        dst_pitch = 5120
        chan = 0x96fb020
        dst_offset = 1855008
        linear = 1
        bo = 0x96fe398
        line_len = 1872
#11 nouveau_exa_upload_to_screen (pdpix=0x972d618, x=392, y=362, w=468, h=60, 
    src=0x0, src_pitch=1872) at nouveau_exa.c:464
        pScrn = <value optimized out>
        pNv = <value optimized out>
        bo = 0x96fb020
        dst_pitch = 5120
        cpp = 4
        dst = <value optimized out>
        ret = 0
#12 0x00190748 in exaHWCopyNtoN (pSrcDrawable=0x9f05e80, 
    pDstDrawable=0x9c06860, pGC=0x0, pbox=<value optimized out>, nbox=0, 
    dx=-392, dy=-362, reverse=0, upsidedown=0) at exa_accel.c:535
        bpp = 32
        src_stride = 1872
        src = <value optimized out>
        pExaScr = 0x96fee50
        pSrcPixmap = 0x9f05e80
        pDstPixmap = 0x972d618
        pSrcExaPixmap = 0x9e87750
        pDstExaPixmap = 0x972d6d8
        src_off_x = <value optimized out>
        src_off_y = <value optimized out>
        dst_off_x = 0
        dst_off_y = 0
        srcregion = 0xa8a8970
        dstregion = 0x9b7d418
        rects = <value optimized out>
        ret = 1
#13 0x00196102 in exaComposite (op=1 '\001', pSrc=0xa8a8918, pMask=0x0, 
    pDst=0x9f06b18, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=392, yDst=362, 
    width=468, height=60) at exa_render.c:956
        ret = <value optimized out>
        pExaScr = 0x0
        ret = -1
        saveSrcRepeat = 23724288
        saveMaskRepeat = 0
        region = {extents = {x1 = 392, y1 = 362, x2 = 860, y2 = 422}, 
          data = 0x0}
#14 0x0811ba47 in damageComposite (op=1 '\001', pSrc=0xa8a8918, pMask=0x0, 
    pDst=0x9f06b18, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=392, yDst=189, 
    width=468, height=60) at damage.c:643
        ps = 0x96fec08
        pScrPriv = 0x96ff0f0
#15 0x0810ea70 in CompositePicture (op=<value optimized out>, pSrc=0xa8a8918, 
    pMask=0x0, pDst=0x9f06b18, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=392, 
    yDst=189, width=468, height=60) at picture.c:1714
        ps = 0x96fec08
#16 0x08114c95 in ProcRenderComposite (client=0x99373d8) at render.c:723

Comment 4 Dan Horák 2010-05-31 10:08:17 UTC
Created attachment 418236 [details]
recent dmesg

Comment 5 Dan Horák 2010-05-31 10:09:26 UTC
Created attachment 418238 [details]
messages from the date of the crash

Comment 6 Bug Zapper 2011-06-02 12:39:47 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2011-06-27 17:09:40 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.