Unfortunately, I haven't been able to reproduce the crash with this variable enabled, despite playing for more than 5 hours (not consecutively.) The GALLIUM_DDEBUG mode is certainly working as performance is quite severely impacted. As I understand it, it creates fences around each GPU operation to detect when and if they complete, dumping the contents of the draw call if it doesn't finish in a timely way. I found out about this option via a Google search. Just to keep you up to date, I switched tack and have been using the "GALLIUM_DDEBUG" environment variable to try and capture data about the crash. My current stack (Debian testing as a base): Let me know, if you need something else, to debug this. According to the syslog (see the attached file for more details), the crash happens in: drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0x86/0x9d with the stack detailed below. Memory at fbc80000 (64-bit, non-prefetchable) Įxpansion ROM at fbcc0000 Ĭapabilities: Vendor Specific Information: Len=08 Ĭapabilities: Power Management version 3Ĭapabilities: Express Legacy Endpoint, MSI 00Ĭapabilities: MSI: Enable+ Count=1/1 Maskable- 64bit+Ĭapabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010 Ĭapabilities: Advanced Error Reporting Memory at d0000000 (64-bit, prefetchable) Error 41 This error only occurs if you have a virus scanner running in the background. Subsystem: Diamond Multimedia Systems Device 7770įlags: bus master, fast devsel, latency 0, IRQ 40 I also included a my dmesg:Ġ5:00.0 VGA compatible controller: Advanced Micro Devices, Inc. It happens much less frequently but it still does. * line 79, change the line: eval "$GAMESCRIPT" apitrace trace "$GAMESCRIPT" then save and launch the game, now the trace is properly generated * do a backup of xcom.sh file then edit the file home/ryan/.local/share/Steam/SteamApps/common/XCom-Enemy-Unknown/binaries/linux/xcom.sh: line 39: 9211 Segmentation fault (core dumped) $" Game removed: AppID 200510 "XCOM: Enemy Unknown", ProcID 6576 Thanks, but the game simply segfaults when I do this:ĭumped crashlog to /home/ryan/.local/share/feral-interactive/XCOM/crashes//50524115-5e25-7dad-395afa0f-6f10b83e.dmp > output to the console, so start steam in a terminal if you need to see the > you can run the game with gdb, strace, etc using this option. > On steam, you can select the game, right click on it, select proprieties , Gdb backtrace from xorg when system locks up during glretrace replayĪpitrace patch for honoring range in DrawRangeElementsX commands System journal containing gpu hang during apitrace replay Output of GALLIUM_DDEBUG="800 noflush" and R600_DEBUG="ps,vs,gs,vm" Has anyone come across this? Game - license, computer configuration (if needed) - OS - Windows 7 Ultimate 64-bit SP 1, processor - AMD Phenom II X4 955 Processor, 4.Syslog excerpt showing the GPU stall and kernel backtrace I thought it was an incorrect display, I sold something on the black market, but nothing changed - my balance was still negative, but it increased by 60 credits. When I logged out and logged in this way, my balance was -8798 credits instead of 200 credits. The Esc menu works, but nothing happens when you press save. Then, the context menu disappeared (where there is a laboratory, workshop, barracks, etc.), and when I entered the control center simply by clicking on the room, I saw that there was not a single item there either. They appeared after about 30 minutes of the game. The next day, freezes began, against which only the task manager helps. I downloaded it, went into the game, played for a couple of hours - everything is fine. In general, on New Year's discounts I bought myself XCOM: EW (EU won on some site back in the fall). A couple of problems with XCOM: EW (XCOM: Enemy Unknown)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |