Bug 30603 - X crash in NVAccelDownloadM2MF with KDE desktop effects enabled.
Summary: X crash in NVAccelDownloadM2MF with KDE desktop effects enabled.
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 13:26 UTC by Orion Poplawski
Modified: 2013-08-18 18:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (33.89 KB, text/plain)
2010-10-04 13:26 UTC, Orion Poplawski
no flags Details

Description Orion Poplawski 2010-10-04 13:26:41 UTC
Created attachment 39158 [details]
Xorg.0.log

Logging into KDE with desktop effects enabled results in an X crash:

#0  0x000000377b634065 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x000000377b635a16 in abort () at abort.c:92
#2  0x000000000046346e in OsAbort () at utils.c:1274
#3  0x000000000046ee07 in ddxGiveUp () at xf86Init.c:951
#4  0x000000000045f96d in AbortServer () at log.c:424
#5  0x000000000045fb7e in FatalError (f=0x578d10 "Caught signal %d (%s). Server aborting\n")
    at log.c:552
#6  0x0000000000460bde in OsSigHandler (signo=11, sip=<value optimized out>, 
    unused=<value optimized out>) at osinit.c:156
#7  <signal handler called>
#8  0x00007fe0566c6961 in NVAccelDownloadM2MF (pspix=0xe15980, x=0, y=0, w=1920, h=1080, 
    dst=0x0, dst_pitch=7680) at /usr/include/bits/string3.h:52
#9  nouveau_exa_download_from_screen (pspix=0xe15980, x=0, y=0, w=1920, h=1080, dst=0x0, 
    dst_pitch=7680) at nouveau_exa.c:415
#10 0x00007fe055a58013 in exaGetImage (pDrawable=0xe15980, x=0, y=0, w=1920, h=1080, format=2, 
    planeMask=18446744073709551615, d=0x0) at exa_accel.c:1294
#11 0x0000000000555ac8 in miSpriteGetImage (pDrawable=0xe15980, sx=0, sy=0, w=1920, h=1080, 
    format=2, planemask=18446744073709551615, pdstLine=0x0) at misprite.c:423
#12 0x00007fe056f40e4a in swrastGetImage (draw=<value optimized out>, x=<value optimized out>, 
    y=<value optimized out>, w=<value optimized out>, h=<value optimized out>, 
    data=<value optimized out>, loaderPrivate=0x1336880) at glxdriswrast.c:391
#13 0x00007fe054bd564a in ?? () from /usr/lib64/dri/swrast_dri.so
#14 0x00007fe056f40de8 in __glXDRIbindTexImage (baseContext=<value optimized out>, 
    buffer=<value optimized out>, glxPixmap=<value optimized out>) at glxdriswrast.c:205
#15 0x00007fe056f3d9ce in __glXDisp_BindTexImageEXT (cl=<value optimized out>, 
    pc=<value optimized out>) at glxcmds.c:1603
#16 0x00007fe056f3e812 in __glXDisp_VendorPrivate (cl=0x1084bc8, pc=<value optimized out>)
    at glxcmds.c:2314
#17 0x00007fe056f40483 in __glXDispatch (client=0x1084ab0) at glxext.c:601
#18 0x000000000042d431 in Dispatch () at dispatch.c:432
#19 0x000000000042148e in main (argc=5, argv=<value optimized out>, envp=<value optimized out>)
    at main.c:291
Comment 1 Orion Poplawski 2010-10-04 13:28:28 UTC
Can log in fine if I install nouveau_dri.so from mesa-dri-drivers-experimental-7.9-0.8.fc14.x86_64
Comment 2 Ilia Mirkin 2013-08-18 18:09:51 UTC
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.