Bug 21468 - [GM45]: suspend/resume from ram cycle causes segfault
Summary: [GM45]: suspend/resume from ram cycle causes segfault
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other All
: medium critical
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 21384 21704 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-28 14:46 UTC by Arkadiusz Miskiewicz
Modified: 2009-05-12 15:40 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (16.85 KB, text/plain)
2009-04-28 14:47 UTC, Arkadiusz Miskiewicz
no flags Details

Description Arkadiusz Miskiewicz 2009-04-28 14:46:45 UTC
thinkpad t400, x86_64 linux, xserver 1.6.1, intel driver from master(a90cab43209bba52d35b953f3d686a19c154fc43), libdrm (a1e3ab9e55047c08a4006ec389c1a99b72bc672c)

suspend to ram causes segfault and X session is restarted

Program received signal SIGSEGV, Segmentation fault.
0x00007f092ff967b3 in drm_intel_bufmgr_check_aperture_space (bo_array=0x7fff3b2348c0, count=3) at intel_bufmgr.c:155
155             return bo_array[0]->bufmgr->check_aperture_space(bo_array, count);
(gdb) bt
#0  0x00007f092ff967b3 in drm_intel_bufmgr_check_aperture_space (bo_array=0x7fff3b2348c0, count=3) at intel_bufmgr.c:155
#1  0x00007f09301fecc7 in i830_get_aperture_space () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#2  0x00007f09301ff657 in i830_uxa_prepare_copy () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#3  0x00007f09302150e3 in uxa_copy_n_to_n () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#4  0x00007f092fd85d3a in fbCopyRegion (pSrcDrawable=0x4fe4910, pDstDrawable=0x4fe4910, pGC=0x0, pDstRegion=<value optimized out>, dx=-30, dy=807400660,
    copyProc=0x7f0930214f5c <uxa_copy_n_to_n>, bitPlane=0, closure=0x0) at fbcopy.c:396
#5  0x00007f09302162e0 in uxa_copy_window () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#6  0x000000000053078b in damageCopyWindow (pWindow=0x5451ed0, ptOldOrg=<value optimized out>, prgnSrc=0x573f140) at damage.c:1774
#7  0x00000000004da4af in miSpriteCopyWindow (pWindow=0x5451ed0, ptOldOrg={x = 1131, y = 873}, prgnSrc=0x573f140) at misprite.c:480
#8  0x00000000004fa13c in compCopyWindow (pWin=0x5451ed0, ptOldOrg=<value optimized out>, prgnSrc=0x573f140) at compwindow.c:577
#9  0x00000000004e1775 in miMoveWindow (pWin=0x5451ed0, x=30, y=0, pNextSib=0x0, kind=VTMove) at miwindow.c:317
#10 0x00000000004fa71e in compMoveWindow (pWin=0x5451ed0, x=1161, y=9, pSib=0x0, kind=VTMove) at compwindow.c:363
#11 0x00000000004336f6 in ConfigureWindow (pWin=0x5451ed0, mask=15, vlist=<value optimized out>, client=0x369) at window.c:2400
#12 0x0000000000446e4d in ProcConfigureWindow (client=0x4f36510) at dispatch.c:741
#13 0x00000000004477bc in Dispatch () at dispatch.c:437
#14 0x000000000042d63d in main (argc=7, argv=0x7fff3b234f78, envp=<value optimized out>) at main.c:397
(gdb) frame 0
#0  0x00007f092ff967b3 in drm_intel_bufmgr_check_aperture_space (bo_array=0x7fff3b2348c0, count=3) at intel_bufmgr.c:155
155             return bo_array[0]->bufmgr->check_aperture_space(bo_array, count);
(gdb) print bo_array
$1 = (drm_intel_bo **) 0x7fff3b2348c0
(gdb) print *bo_array
$2 = (drm_intel_bo *) 0x0
Comment 1 Arkadiusz Miskiewicz 2009-04-28 14:47:48 UTC
Created attachment 25241 [details]
Xorg.0.log
Comment 2 Gordon Jin 2009-04-28 18:51:13 UTC
Can this be also reproduced by just switching between X and text console?
Comment 3 Arkadiusz Miskiewicz 2009-04-28 22:10:04 UTC
Switching between X and text console works fine (just tried doing that like 20 times).
Comment 4 Jesse Barnes 2009-05-11 11:21:55 UTC
Adjusting severity: crashes & hangs should be marked critical.
Comment 5 Eric Anholt 2009-05-12 14:29:57 UTC
commit e54a23bff068416ccbdb75d538dc7dcd40a6c95c
Author: Keith Packard <keithp@keithp.com>
Date:   Thu May 7 16:35:19 2009 -0700

    Fallback when VT inactive
    
    While the VT is inactive, pI830->batch_bo will be NULL, so use that as a
    simple check for when to not use the accelerator. The alternative is to
    ignore VT switch and just keep drawing, which would also be fine.
Comment 6 Eric Anholt 2009-05-12 14:34:36 UTC
*** Bug 21704 has been marked as a duplicate of this bug. ***
Comment 7 Eric Anholt 2009-05-12 15:40:42 UTC
*** Bug 21384 has been marked as a duplicate of this bug. ***


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.