Author Topic: Crash at main hall with intel drivers  (Read 8580 times)

0 Members and 1 Guest are viewing this topic.

Crash at main hall with intel drivers
Hi all,

Just built a new system, and tried to get FS2 running on it, but I'm getting a segfault at the main hall. This happens in my old (previously working) install folder, and in a clean FS2 install, with 3.7.0 and 3.6.14. The only info I get on the command line is:
"ATTENTION: default value of option force_s3tc_enable overridden by environment.
Segmentation fault"
I'm on openSUSE 13.1 RC1, using the HD 4600 integrated drivers on a 4670K (still waiting on a real graphics card). It looks like these might be the problem, as the gdb backtrace mentions /usr/lib/dri/i965_dri.so. (part of Mesa 9.2.2-61.6.1)
The gdb backtrace and fs2_open.log files are attached. Any help would be appreciated. Thanks!

NedLander

[attachment deleted by ninja]

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
Here's a couple of things you could try:

1) Do you have "force_s3tc_enable" set in your environment?  If so, try un-setting it before running FSO.

2) When using an Intel GPU you might need to add "-no_glsl" to your command line parameters.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Crash at main hall with intel drivers
Thanks for the reply! I tried both of those things, and am still getting the same problem. Program opens, plays the intro movie, and lets me select a pilot. Then it displays one frame of main hall and instantly crashes with segfault. (It also looks like I don't have 'force_s3tc_enable' set in my env vars if I check the output of 'env'.)

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
Well, you could maybe try the command line parameter "-nohtl", but that'll probably run very slowly (if at all).  Unfortunately I don't think there's much else that can help right now, FSO tends to have issues with Intel cards due to incomplete/buggy OpenGL support in the drivers.  You might need to wait for that new graphic card :(

BTW - what was the old system that you had where FSO was working?
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Crash at main hall with intel drivers
AMD Athlon X2 7850BE with an 8800gt or a GT430 under Nvidia drivers, running openSUSE 12.3. Worked great!  So probably once I get another Nvidia card, that will fix everything...

Another possibility is that my system is 64-bit, but I'm using the 32-bit FSO build. That worked on my previous system, but maybe I should try to compile FSO in 64-bit for this one, rather than using the 32-bit compatibility libraries.

 
Re: Crash at main hall with intel drivers
niffiwan, I just saw you have openSUSE rpms in your signature, so I just tried the x86_64 build. Same crash, unfortunately. But I think some Intel driver updates are coming soon with Broadwell.

Quote
Program received signal SIGSEGV, Segmentation fault.
0x00007fffeb6b082e in ?? () from /usr/lib64/dri/i965_dri.so
(gdb) bt
#0  0x00007fffeb6b082e in ?? () from /usr/lib64/dri/i965_dri.so
#1  0x00007fffeb19ab36 in _mesa_ReadnPixelsARB () from /usr/lib64/libdricore9.2.2.so.1
Cannot access memory at address 0x7fffffffcf58
« Last Edit: November 05, 2013, 10:29:22 pm by NedLander »

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
If you're feeling really adventurous, you could maybe install the debug packages for the intel driver that you're using and see if they add any more useful info to the backtrace?  But, that'd probably be of most interest to Intel driver developers.  I don't have an Intel card to run any tests with, the desktop has Nvidia, and AMD in my laptop.

Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Crash at main hall with intel drivers
Actually, just installed some debug packages, so here is a more detailed backtrace:

Quote
    (gdb) run -window -nograb
    Starting program: /data/programs/freespace2/fs2_open_3.7.0_DEBUG_x64 -window -nograb
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib64/libthread_db.so.1".
    Future debug output directed to: /home/nathand/.fs2_open/data/fs2_open.log
    [New Thread 0x7ffff0dfa700 (LWP 25279)]
    [Thread 0x7ffff0dfa700 (LWP 25279) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25280)]
    [New Thread 0x7ffff7f46700 (LWP 25281)]
    [Thread 0x7ffff7f46700 (LWP 25281) exited]
    [Thread 0x7ffff0dfa700 (LWP 25280) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25282)]
    [Thread 0x7ffff0dfa700 (LWP 25282) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25283)]
    [New Thread 0x7ffff7f46700 (LWP 25284)]
    [Thread 0x7ffff7f46700 (LWP 25284) exited]
    [Thread 0x7ffff0dfa700 (LWP 25283) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25285)]
    [Thread 0x7ffff0dfa700 (LWP 25285) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25286)]
    [Thread 0x7ffff0dfa700 (LWP 25286) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25287)]
    [Thread 0x7ffff0dfa700 (LWP 25287) exited]
    [New Thread 0x7ffff0dfa700 (LWP 25288)]
    [New Thread 0x7ffff7f46700 (LWP 25289)]
    [New Thread 0x7fffec574700 (LWP 25290)]
    ATTENTION: default value of option force_s3tc_enable overridden by environment.

    Program received signal SIGSEGV, Segmentation fault.
    0x00007fffeb6b082e in do_blit_readpixels (pixels=0x0, pack=0x25b3b28, type=33639, format=32993, height=1080,
        width=1920, y=0, x=0, ctx=0x25a4a30) at intel_pixel_read.c:94
    94      intel_pixel_read.c: No such file or directory.
    (gdb) bt
    #0  0x00007fffeb6b082e in do_blit_readpixels (pixels=0x0, pack=0x25b3b28, type=33639, format=32993,
        height=1080, width=1920, y=0, x=0, ctx=0x25a4a30) at intel_pixel_read.c:94
    #1  intelReadPixels (ctx=0x25a4a30, x=0, y=0, width=1920, height=1080, format=32993, type=33639,
        pack=0x25b3b28, pixels=0x0) at intel_pixel_read.c:174
    #2  0x00007fffeb19ab36 in _mesa_ReadnPixelsARB (x=0, y=0, width=1920, height=1080, format=32993, type=33639,
        bufSize=bufSize@entry=2147483647, pixels=pixels@entry=0x0) at ../../../src/mesa/main/readpix.c:1042
    #3  0x00007fffeb19ad2a in _mesa_ReadPixels (x=<optimized out>, y=<optimized out>, width=<optimized out>,
        height=<optimized out>, format=<optimized out>, type=<optimized out>, pixels=0x0)
        at ../../../src/mesa/main/readpix.c:1050
    #4  0x00000000004f01f2 in ?? ()
    #5  0x00000000007c0307 in ?? ()
    #6  0x00000000007c0d46 in ?? ()
    #7  0x00000000005dd139 in ?? ()
    #8  0x00000000005c7577 in ?? ()
    #9  0x00000000004da018 in ?? ()
    #10 0x000000000044475a in ?? ()
    #11 0x000000000040d445 in ?? ()
    #12 0x00007ffff5704be5 in __libc_start_main () from /lib64/libc.so.6
    #13 0x0000000000435a19 in ?? ()

 
Re: Crash at main hall with intel drivers
I'm having exactly the same issue. Any news on this front? Seems to be the same as: http://www.hard-light.net/forums/index.php?topic=86145.0

 
Re: Crash at main hall with intel drivers
No updates on my end; I gave up and got an Nvidia card. Works beautifully now, but kind of disappointing, since the Intel graphics probably would have been sufficient had they worked.

 
Re: Crash at main hall with intel drivers
FS2 worked on my laptop a year or two ago, can't remember the version. Nothing changed with the laptop, and the GOG.com version works with wine, but I would like to replay some mods again. Oh well...

 

Offline The E

  • He's Ebeneezer Goode
  • Moderator
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: Crash at main hall with intel drivers
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

Always post your logs, even if your error looks similar to one reported by a different person.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

 
Re: Crash at main hall with intel drivers

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
See if adding -no_glsl on the command line helps you out.

If not, you could try one of the recent nightly builds (or build from latest source if you're comfortable with that)  There were a few issues fixed recently to do with graphics options not being disabled correctly when the video card didn't support the required feature.

Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Crash at main hall with intel drivers
no_glsl  does nothing. I'll try building from the latest source and report ;)

 
Re: Crash at main hall with intel drivers
SVN 10253 not working either
with -no_glsl
http://pastebin.com/MCz0rep1

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
:sigh:

Well, moving further into debugging territory, could you please try one of the following.

a) If you have a large amount of cloud based storage, and a good internet upload speed, could you try getting & providing a core dump?

Code: (using a terminal) [Select]
$ ulimit -c unlimited
$ ./fs2_open_DEBUG
$ ls -ltr core*   <-- this will be the core file, pick the most recent, it may be 500-700Mb in size though!

b) Could you provide a stack trace?  See here for details: http://www.hard-light.net/forums/index.php?topic=82688.msg1662031#msg1662031
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 
Re: Crash at main hall with intel drivers
(gdb) backtrace
Code: [Select]
#0  0x00007fffebb759ce in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#1  0x00007fffeb99fd86 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#2  0x00007fffeb99ff7a in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so
#3  0x00000000004d5167 in gr_opengl_save_screen () at graphics/gropengl.cpp:1028
#4  0x00000000007ae8ee in popup_do (pi=0x147e2a0 <Popup_info>, flags=67175424) at popup/popup.cpp:821
#5  0x00000000007aef88 in popup (flags=67175424, nchoices=3) at popup/popup.cpp:1013
#6  0x00000000005d1187 in player_tips_popup () at menuui/playermenu.cpp:1347
#7  0x00000000005b856a in main_hall_do (frametime=0.25) at menuui/mainhallmenu.cpp:840
#8  0x00000000004175fe in game_do_state (state=1) at freespace2/freespace.cpp:6466
#9  0x00000000004bbea5 in gameseq_process_events () at gamesequence/gamesequence.cpp:409
#10 0x000000000041841b in game_main (cmdline=0x223acc0 "") at freespace2/freespace.cpp:7062
#11 0x00000000004185ca in main (argc=1, argv=0x7fffffffe628) at freespace2/freespace.cpp:7196

I'll clean up my dropbox and see if I can fit a core dump there

 

Offline Hellzed

  • 28
Re: Crash at main hall with intel drivers
I'm experiencing the exact same bug (Ubuntu 13.10, xorg-edgers mesa 10.0, Intel HD4000)...
If you need some aditional debug info, I can use gdb and install apitrace.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Crash at main hall with intel drivers
sure, it's always good to get more info. A stacktrace would be good, a coredump would be great (although obviously a bit harder to pass around)
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...