Summary: | Anomaly 2 (Steam) exits with divide by 0 in r600g | ||
---|---|---|---|
Product: | Mesa | Reporter: | romulasry |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | mathias.anselmann |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
full steam logfile
Full GDB backtrace for Anomaly 2 Full GDB backtrace for git mesa Anomaly 2 Full GDB backtrace for git mesa Anomaly 2 Full GDB backtrace for Anomaly 2 (2013-10-02) |
Description
romulasry
2013-05-15 20:44:09 UTC
> GLX_EXT_swap_control not supported, unable to set vertical sync.
Are you sure the problem is directly related to this message? If it is, it's not a driver specific problem, as GLX_EXT_swap_control is not implemented at all yet in Mesa AFAICT.
First of all though, why do you say it 'crashes'? Is there any evidence of a crash that you didn't include?
It then closes. It won't run without that extention, switched to GLX instead of a driver specific component. The swap control extension is not required by the game to function. The exit must be caused by something else. What exactly happens? Does it look like graceful exit or a segfault? What kind of GPU are you using? 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4870] Created attachment 79488 [details]
full steam logfile
(In reply to comment #4) >Does it look like agraceful exit or a segfault? No segfault so a graceful exit. Hm, doesn't really look graceful to me, I see:
> traps: Renderer[14746] trap divide error ip:f5eea6aa sp:f03fedd0 error:0 in r600_dri.so[f5b82000+585000]
in dmesg output (nothing else) and "Floating point exception" on the console where Steam is running.
Additional information:
Game crashes after intro, which I can watch.
Warning: my Mesa/DRM stack is not up-to-date and I can't update it immediately, but since others are seeing this crash too, maybe this helps to find the reason. I'll try to get a recent Mesa/libdrm stack up here soon.
(In reply to comment #8) > Hm, doesn't really look graceful to me, I see: > > traps: Renderer[14746] trap divide error ip:f5eea6aa sp:f03fedd0 error:0 in r600_dri.so[f5b82000+585000] > in dmesg output (nothing else) and "Floating point exception" on the console > where Steam is running. Can you get a proper backtrace with gdb? Created attachment 79573 [details] Full GDB backtrace for Anomaly 2 Yes, took two attempts, but attaching GDB while the intro is playing works (GAME_DEBUGGER=gdb doesn't seem to work, though I think it should?). The interesting part seems to be (on first glance): >copy_height=<error reading variable: Could not find type for DW_OP_GNU_const_type> Again, just to make sure you don't search for a bug that is maybe no longer in r600g: I don't have the latest master for Mesa/libdrm, and it'll take me at least a few days, before I can get around to build a new version. Hency you might want to confirm the backtrace with somebody who runs master. (In reply to comment #2) > It then closes. It won't run without that extention, switched to GLX instead > of a driver specific component. The game runs for me with i965 on gen7. Same problem here, game crashes after intro, which I can watch. Dmesg output here is: traps: Renderer[1375] trap divide error ip:f4fedce4 sp:f09fee30 error:0 in r600_dri.so[f4b61000+1512000] I'm using mesa 9.1.2 and kernel 3.9.3 (up to date arch system). (In reply to comment #12) > Same problem here, game crashes after intro, which I can watch. > Dmesg output here is: > > traps: Renderer[1375] trap divide error ip:f4fedce4 sp:f09fee30 error:0 in > r600_dri.so[f4b61000+1512000] > > I'm using mesa 9.1.2 and kernel 3.9.3 (up to date arch system). Same issue in git: traps: Renderer[7610] trap divide error ip:f5eb56ba sp:f07fedd0 error:0 in r600_dri.so[f5b3e000+5f5000 (In reply to comment #11) > (In reply to comment #2) > > It then closes. It won't run without that extention, switched to GLX instead > > of a driver specific component. > > The game runs for me with i965 on gen7. Very likely (see attachment 79573 [details]). The title is wrong, GLX_EXT_swap_control is only requested by the Steam overlay and non-critical. I can see the GLX_EXT_swap_control with any game I launch through Steam (e.g. Oil Rush) and the others work well. It's just Anomaly that is hitting a bug in r600g (or a bug in Anomaly which isn't handled gracefully by r600g?). Anyway, the title should be changed to something more accurate. > Again, just to make sure you don't search for a bug that is maybe no longer
> in r600g: I don't have the latest master for Mesa/libdrm, and it'll take me
> at least a few days, before I can get around to build a new version. Hency
> you might want to confirm the backtrace with somebody who runs master.
I will the backtrace, could you give me the exact command you used?
(In reply to comment #15) > > Again, just to make sure you don't search for a bug that is maybe no longer > > in r600g: I don't have the latest master for Mesa/libdrm, and it'll take me > > at least a few days, before I can get around to build a new version. Hency > > you might want to confirm the backtrace with somebody who runs master. > > I will the backtrace, could you give me the exact command you used? The command is gdb "~/.local/share/Steam/SteamApps/common/Anomaly 2/Anomaly2Linux" [ProcID] but that alone isn't enough. First you need to install the debugging symbols for Mesa and libc (the 32 bit versions!). Then you need to start Steam and Anomaly 2 through Steam. While the intro is playing you need to tab to a console, determine the process ID (with ps) and then replace [ProcID] in the command above. After gdb has attached itself to Anomaly 2, you will see the gdb prompt where you need to type c (or continue). After that, you can tab back to the game and wait until you hit the crash. Then you should be back to your desktop (and console windows). There you have to type in bt full and info registers You can exit gdb (and the attached Anomaly 2) by typing in q (or quit). If you want to redirect the output of the above commands to a file, use set logging file /path/to/log-file set logging on before you type c (or continue). If you have trouble getting through all commands before the intro ends, you might want to prepare them beforehand. I hope this helps. Created attachment 79726 [details]
Full GDB backtrace for git mesa Anomaly 2
Created attachment 79727 [details]
Full GDB backtrace for git mesa Anomaly 2
Created attachment 86915 [details] Full GDB backtrace for Anomaly 2 (2013-10-02) Still an issue with current Git HEAD on an X.org 1.14.2 (ie. with OpenGL 3.1 available). The stack is: Kernel: 3.11.2 libdrm: 2.4.46 Mesa: master/aac75f877da1d106f6fd7bbd238d1d1d35a0c8e8 X.Org: 1.14.2 Current dmesg output is: > traps: Renderer[12757] trap divide error ip:f53c1896 sp:f0bfede0 error:0 in r600_dri.so[f4f06000+11a0000] -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/438. |
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.