Bug 39239 - Ryzom does not work!
Summary: Ryzom does not work!
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-07-14 14:10 UTC by Jorge Araya Navarro
Modified: 2011-09-15 10:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jorge Araya Navarro 2011-07-14 14:10:47 UTC
Ryzom does not work with the driver i915, i can't get the right version of my driver, anyway, here some of output:

jorge@Abril:/usr/local/games$ gdb ryzom_client
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying" 
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/games/ryzom_client...done.
(gdb) run
Starting program: /usr/local/games/ryzom_client 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffefc23700 (LWP 6194)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000100000000 in ?? ()
(gdb) bt
#0  0x0000000100000000 in ?? ()
#1  0x00007ffff2b284a1 in XML_Parse () from /usr/lib/libxmlparse.so.0
#2  0x00007fffec5de9ec in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#3  0x00007fffec5ebd9d in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#4  0x00007fffec5dc0af in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#5  0x00007fffee9479c7 in ?? () from /usr/lib/libGL.so.1
#6  0x00007fffee924a29 in ?? () from /usr/lib/libGL.so.1
#7  0x00007fffee921948 in ?? () from /usr/lib/libGL.so.1
#8  0x00007fffee921aed in glXChooseVisual () from /usr/lib/libGL.so.1
#9  0x00007fffeebbe051 in NL3D::CDriverGL::setDisplay (this=0x1f99e60, wnd=0, 
    mode=..., show=false, resizeable=<value optimized out>)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver/opengl/driver_opengl_window.cpp:1063
#10 0x00007ffff6bb2a1e in NL3D::CDriverUser::setDisplay (this=0x1cc4a60, 
    wnd=0, mode=<value optimized out>, show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:237
#11 0x00007ffff6bb0f90 in NL3D::CDriverUser::setDisplay (this=0x1cc4a60, 
    mode=..., show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:228
#12 0x00000000007d9a64 in prelogInit ()
    at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/init.cpp:886
#13 0x000000000067e051 in main (argc=<value optimized out>, 
    argv=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
    at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/client.cpp:555

jorge@Abril:/usr/local/games$
Comment 1 Ian Romanick 2011-07-14 15:34:44 UTC
Since the crash is inside libxmlparse, I'm assuming that it's processing your (or the systems) driconf.  What happens if you remove (or move) ~/.drirc or /etc/drirc?  Note that one of those files may not exist.

Also, what is the output of:

    glxinfo | egrep 'OpenGL (renderer|version)'
Comment 2 Jorge Araya Navarro 2011-07-14 22:39:37 UTC
(In reply to comment #1)
> Since the crash is inside libxmlparse, I'm assuming that it's processing your
> (or the systems) driconf.  What happens if you remove (or move) ~/.drirc or
> /etc/drirc?  Note that one of those files may not exist.
> 
> Also, what is the output of:
> 
>     glxinfo | egrep 'OpenGL (renderer|version)'

i dont have the file ~/.drirc or /etc/drirc :-|

the output of glxinfo is:

OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile  
OpenGL version string: 2.1 Mesa 7.10.3
Comment 3 Jorge Araya Navarro 2011-07-16 12:28:05 UTC
(In reply to comment #1)
> Since the crash is inside libxmlparse, I'm assuming that it's processing your
> (or the systems) driconf.  What happens if you remove (or move) ~/.drirc or
> /etc/drirc?  Note that one of those files may not exist.
> 
> Also, what is the output of:
> 
>     glxinfo | egrep 'OpenGL (renderer|version)'

hello!

I create a Debug Symbols for libxmlparse, so, i have a little more data about this bug. please, if you can indicate me a wiki or a document what I can use to create the Debug Symbols for «intel-dri 7.10.3-1» and  «libgl 7.10.3-1» in Parabola (Arch Linux) Gnu/Linux I'll appreciate it!:

Starting program: /usr/local/games/ryzom_client --verbose

Program exited with code 0177.
Hangup detected on fd 0
Error detected on fd 0
error detected on stdin
Starting program: /usr/local/games/ryzom_client 

Program exited with code 0177.
Starting program: /usr/local/games/ryzom_client 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffefc3c700 (LWP 1538)]
[Thread 0x7fffefc3c700 (LWP 1538) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000000100000000 in ?? ()
#0  0x0000000100000000 in ?? ()
#1  0x00007ffff2b3504e in XML_Parse (parser=0x1fb29a0, 
    s=0x7fffec81da60 "<driinfo>\n<section>\n<description lang=\"en\" text=\"Performance\"/>\n<description lang=\"de\" text=\"Leistung\"/>\n<description lang=\"es\" text=\"Rendimiento\"/>\n<description lang=\"nl\" text=\"Prestatie\"/>\n<descript"..., len=8928, isFinal=1)
    at xmlparse.c:860
#2  0x00007fffec5f89ec in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#3  0x00007fffec605d9d in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#4  0x00007fffec5f60af in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#5  0x00007fffee9619c7 in ?? () from /usr/lib/libGL.so.1
#6  0x00007fffee93ea29 in ?? () from /usr/lib/libGL.so.1
#7  0x00007fffee93b948 in ?? () from /usr/lib/libGL.so.1
#8  0x00007fffee93baed in glXChooseVisual () from /usr/lib/libGL.so.1
#9  0x00007fffeebd8051 in NL3D::CDriverGL::setDisplay (this=0x1f99d30, wnd=0, mode=..., show=false, resizeable=<value optimized out>)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver/opengl/driver_opengl_window.cpp:1063
#10 0x00007ffff6bb3a1e in NL3D::CDriverUser::setDisplay (this=0x1cc47f0, wnd=0, mode=<value optimized out>, show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:237
#11 0x00007ffff6bb1f90 in NL3D::CDriverUser::setDisplay (this=0x1cc47f0, mode=..., show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:228
#12 0x00000000007d9a64 in prelogInit () at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/init.cpp:886
#13 0x000000000067e051 in main (argc=<value optimized out>, argv=<value optimized out>)
    at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/client.cpp:555
Comment 4 Jorge Araya Navarro 2011-07-16 13:44:44 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Since the crash is inside libxmlparse, I'm assuming that it's processing your
> > (or the systems) driconf.  What happens if you remove (or move) ~/.drirc or
> > /etc/drirc?  Note that one of those files may not exist.
> > 
> > Also, what is the output of:
> > 
> >     glxinfo | egrep 'OpenGL (renderer|version)'
> 
> i dont have the file ~/.drirc or /etc/drirc :-|
> 
> the output of glxinfo is:
> 
> OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile  
> OpenGL version string: 2.1 Mesa 7.10.3

ok, i have more output, all what i can get, i hope this can be usefull:

Starting program: /usr/local/games/ryzom_client 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffefc3c700 (LWP 13126)]
[Thread 0x7fffefc3c700 (LWP 13126) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000000100000000 in ?? ()
#0  0x0000000100000000 in ?? ()
#1  0x00007ffff2b3504e in XML_Parse (parser=0x1fb2ca0, 
    s=0x7fffec826240 "<driinfo>\n<section>\n<description lang=\"en\" text=\"Performance\"/>\n<description lang=\"de\" text=\"Leistung\"/>\n<description lang=\"es\" text=\"Rendimiento\"/>\n<description lang=\"nl\" text=\"Prestatie\"/>\n<descript"..., len=8928, isFinal=1)
    at xmlparse.c:860
#2  0x00007fffec6213db in driParseOptionInfo (info=0x1fb0e28, configOptions=<value optimized out>, nConfigOptions=11)
    at ../common/xmlconfig.c:686
#3  0x00007fffec630dff in intelInitScreen2 (psp=0x1fb0c70) at intel_screen.c:515
#4  0x00007fffec61eb20 in dri2CreateNewScreen (scrn=0, fd=10, extensions=0x1fa9750, driver_configs=0x7fffffffd318, data=0x1faa8d0)
    at ../common/dri_util.c:878
#5  0x00007fffee9623c5 in dri2CreateScreen (screen=0, priv=0x1fa8480) at dri2_glx.c:840
#6  0x00007fffee94236c in AllocAndFetchScreenConfigs (dpy=0x1f9b670) at glxext.c:765
#7  __glXInitialize (dpy=0x1f9b670) at glxext.c:865
#8  0x00007fffee93edb4 in GetGLXPrivScreenConfig (dpy=0x1f9b670, scrn=0, ppriv=0x7fffffffd4f8, ppsc=0x7fffffffd4f0) at glxcmds.c:130
#9  0x00007fffee93fd47 in glXChooseVisual (dpy=0x1f9b670, screen=0, attribList=0x7fffeee0ad40) at glxcmds.c:1160
#10 0x00007fffeebd8051 in NL3D::CDriverGL::setDisplay (this=0x1f9a030, wnd=0, mode=..., show=false, resizeable=<value optimized out>)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver/opengl/driver_opengl_window.cpp:1063
#11 0x00007ffff6bb3a1e in NL3D::CDriverUser::setDisplay (this=0x1cc4bb0, wnd=0, mode=<value optimized out>, show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:237
#12 0x00007ffff6bb1f90 in NL3D::CDriverUser::setDisplay (this=0x1cc4bb0, mode=..., show=false, resizeable=true)
    at /home/jorge/.ryzom_sc/ryzom/code/nel/src/3d/driver_user.cpp:228
#13 0x00000000007d9a64 in prelogInit () at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/init.cpp:886
#14 0x000000000067e051 in main (argc=<value optimized out>, argv=<value optimized out>)
    at /home/jorge/.ryzom_sc/ryzom/code/ryzom/client/src/client.cpp:555
Comment 5 Jorge Araya Navarro 2011-09-15 10:24:17 UTC
this was a bug in libwww of the game Ryzom, they have to replace it with libcurl or similar. for more information check http://dev.ryzom.com/issues/1329

thanks! ;)


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.