Bug 69961 - Regression: Xserver fails to start
Summary: Regression: Xserver fails to start
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: Other All
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-30 12:25 UTC by samit vats
Modified: 2013-10-09 09:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.log (32.47 KB, text/plain)
2013-09-30 12:25 UTC, samit vats
Details
xorg.log.ok (55.29 KB, text/plain)
2013-09-30 12:26 UTC, samit vats
Details

Description samit vats 2013-09-30 12:25:35 UTC
Created attachment 86844 [details]
xorg.log

Driver Stack Details:
=====================

1)    Kernel-3.10.5-031005-generic
2)    drm-2.4.46
3)    Mesa-9.2   
4)    Xorg-server-1.11.4
5)    xf86-video-ati- master
6)    glamor-0.5.1/0.5.0
7)    LLVM-3.3

System Configuration:
=====================

Asic         : CapeVerde XT (ID-683D)
O.S.         : Ubuntu-13.04 (64 bit)


Details:
========

1) The Xserver start fine with driver build before 28th september commit.

2) X server crashes with Backtrace with git master :

(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
/usr/bin/X: symbol lookup error: /home/atitest/install/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: glamor_xv_init
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Comment 1 samit vats 2013-09-30 12:26:41 UTC
Created attachment 86845 [details]
xorg.log.ok
Comment 3 Alex Deucher 2013-09-30 14:19:41 UTC
Sorry, issue is there there.  You need to enable Xv when you build glamor.  E.g., pass --enable-xv when you configure glamor.
Comment 4 samit vats 2013-10-01 11:36:29 UTC
I am getting segmentation fault on startx after building glamor with --enable-xv 

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x55f4f8]
1: /usr/bin/X (0x400000+0x1631b9) [0x5631b9]
2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fac50a82000+0xfbd0) [0x7fac50a91bd0]
3: /home/atitest/install/lib/dri/radeonsi_dri.so (radeon_llvm_compile+0xa5) [0x7fac4a7011d5]
4: /home/atitest/install/lib/dri/radeonsi_dri.so (si_compile_llvm+0x70) [0x7fac4a6f31a0]
5: /home/atitest/install/lib/dri/radeonsi_dri.so (si_pipe_shader_create+0x50c) [0x7fac4a6f394c]
6: /home/atitest/install/lib/dri/radeonsi_dri.so (si_shader_select+0x2d2) [0x7fac4a6fc472]
7: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x54e7c8) [0x7fac4a6fc7c8]
8: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x391f5e) [0x7fac4a53ff5e]
9: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x392a6e) [0x7fac4a540a6e]
10: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x3607b7) [0x7fac4a50e7b7]
11: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x35d637) [0x7fac4a50b637]
12: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x370ebd) [0x7fac4a51eebd]
13: /home/atitest/install/lib/dri/radeonsi_dri.so (0x7fac4a1ae000+0x349fd4) [0x7fac4a4f7fd4]
14: /home/atitest/install/lib/libglamor.so.0 (0x7fac4e174000+0x7ccf) [0x7fac4e17bccf]
15: /home/atitest/install/lib/libglamor.so.0 (0x7fac4e174000+0x8215) [0x7fac4e17c215]
16: /home/atitest/install/lib/libglamor.so.0 (0x7fac4e174000+0x87b3) [0x7fac4e17c7b3]
17: /home/atitest/install/lib/libglamor.so.0 (glamor_glyphs_init+0x26e) [0x7fac4e1804be]
18: /home/atitest/install/lib/xorg/modules/drivers/radeon_drv.so (0x7fac4ba55000+0x4bc65) [0x7fac4baa0c65]
19: /home/atitest/install/lib/xorg/modules/drivers/radeon_drv.so (0x7fac4ba55000+0x44ec6) [0x7fac4ba99ec6]
20: /usr/bin/X (0x400000+0x9d867) [0x49d867]
21: /usr/bin/X (0x400000+0x22fbc) [0x422fbc]
22: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fac4faf8ea5]
23: /usr/bin/X (0x400000+0x233dd) [0x4233dd]
Segmentation fault at address (nil)
Comment 5 Michel Dänzer 2013-10-01 16:43:34 UTC
(In reply to comment #4)
> I am getting segmentation fault on startx after building glamor with

That looks like https://bugs.freedesktop.org/show_bug.cgi?id=69463#c7 though, not related to the glamor_xv_init issue.
Comment 6 samit vats 2013-10-08 09:23:28 UTC
Adding gdb backtrace :

#0  0x00007ffb51141037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffb51144698 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x000000000056528e in OsAbort () at utils.c:1230
#3  0x000000000046e91c in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:936
#4  0x000000000046e9d9 in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:982
#5  0x0000000000569e72 in AbortServer () at log.c:416
#6  0x000000000056a075 in FatalError (f=f@entry=0x58df90 "Caught signal %d (%s). Server aborting\n") at log.c:547
#7  0x000000000056320e in OsSigHandler (sip=<optimized out>, signo=11, unused=<optimized out>) at osinit.c:146
#8  OsSigHandler (signo=11, sip=<optimized out>, unused=<optimized out>) at osinit.c:108
#9  <signal handler called>
#10 0x00007ffb4bd34715 in get_r600_target () at radeon_llvm_emit.c:71
#11 radeon_llvm_compile (M=M@entry=0x252b8e0, binary=binary@entry=0x7fff3bc7ff70, gpu_family=0x7ffb4c6e48bc "verde", dump=dump@entry=0) at radeon_llvm_emit.c:108
#12 0x00007ffb4bd2553c in si_compile_llvm (rctx=rctx@entry=0x1c68ac0, shader=shader@entry=0x252a140, mod=0x252b8e0) at radeonsi_shader.c:1765
#13 0x00007ffb4bd25cfc in si_pipe_shader_create (ctx=ctx@entry=0x1c68ac0, shader=shader@entry=0x252a140) at radeonsi_shader.c:1907
#14 0x00007ffb4bd2d262 in si_shader_select (ctx=ctx@entry=0x1c68ac0, sel=sel@entry=0x252a000, dirty=dirty@entry=0x0) at si_state.c:2169
#15 0x00007ffb4bd2d5b8 in si_create_shader_state (ctx=0x1c68ac0, state=0x2538f90, pipe_shader_type=1) at si_state.c:2211
#16 0x00007ffb4bb7112e in st_translate_fragment_program (st=st@entry=0x1cd2610, stfp=stfp@entry=0x1e655a0, key=key@entry=0x7fff3bc89590) at ../../src/mesa/state_tracker/st_program.c:768
#17 0x00007ffb4bb71c3e in st_get_fp_variant (st=0x1cd2610, stfp=0x1e655a0, key=0x7fff3bc89590) at ../../src/mesa/state_tracker/st_program.c:805
#18 0x00007ffb4bb3f7e7 in update_fp (st=0x1cd2610) at ../../src/mesa/state_tracker/st_atom_shader.c:92
#19 0x00007ffb4bb3c667 in st_validate_state (st=0x1cd2610) at ../../src/mesa/state_tracker/st_atom.c:221
#20 0x00007ffb4bb4ff1d in st_draw_vbo (ctx=0x1cf7680, prims=0x7fff3bc896c0, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0, max_index=3, tfb_vertcount=0x0)
    at ../../src/mesa/state_tracker/st_draw.c:210
#21 0x00007ffb4bb29004 in vbo_draw_arrays (ctx=0x1cf7680, mode=6, start=0, count=4, numInstances=1, baseInstance=<optimized out>) at ../../src/mesa/vbo/vbo_exec_array.c:660
#22 0x00007ffb4f7aeccf in _glamor_solid_boxes (pixmap=pixmap@entry=0x2515e80, box=box@entry=0x7fff3bc898d0, nbox=<optimized out>, color=color@entry=0x7fff3bc89850) at glamor_fill.c:245
#23 0x00007ffb4f7af215 in glamor_solid_boxes (pixmap=pixmap@entry=0x2515e80, box=box@entry=0x7fff3bc898d0, nbox=nbox@entry=1, fg_pixel=fg_pixel@entry=0) at glamor_fill.c:306
#24 0x00007ffb4f7af7b3 in glamor_solid (pixmap=pixmap@entry=0x2515e80, x=x@entry=0, y=y@entry=1024, width=width@entry=1024, height=height@entry=32, alu=alu@entry=3 '\003', 
    planemask=planemask@entry=4294967295, fg_pixel=fg_pixel@entry=0) at glamor_fill.c:348
#25 0x00007ffb4f7b34be in clear_mask_cache (maskcache=0x25394f0) at glamor_glyphs.c:169
#26 glamor_realize_glyph_caches (pScreen=0x1d625f0) at glamor_glyphs.c:356
#27 glamor_glyphs_init (pScreen=0x1d625f0) at glamor_glyphs.c:377
#28 0x00007ffb4d0d3c65 in radeon_glamor_create_screen_resources (screen=screen@entry=0x1d625f0) at radeon_glamor.c:64
#29 0x00007ffb4d0ccec6 in RADEONCreateScreenResources_KMS (pScreen=0x1d625f0) at radeon_kms.c:248
#30 0x000000000049d867 in xf86CrtcCreateScreenResources (screen=0x1d625f0) at xf86Crtc.c:725
#31 0x0000000000422fbc in main (argc=9, argv=0x7fff3bc89b68, envp=<optimized out>) at main.c:216
Comment 7 Michel Dänzer 2013-10-09 09:38:13 UTC
The glamor_xv_init issue is fixed. Let's track the other crash in your other bug report.


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.