I had no problem playing the game (aside from low FPS) with i965 on the same machine, stock drivers from Ubuntu 14.10. Now, with a new GFX r9 280X, the game runs OK, but may randomly crash the entire system and I must hard reset the computer. I could not find anything relevant on the dmesg log from the last crashed session, the last message was from boot procedure. Last time it crashed I was on the Mission Center screen, from Carrer Mode. I also remember it crashed when I switched workspace with the game running (XFce, no composition, I pressed ctrl + alt + leftarrow, it swiched, displayed Chrome window running there, and crashed). The driver is no longer Ubuntu stock, and I am using from this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers with the following env var: R600_DEBUG=sb It crashed with Ubuntu 14.10, and crashed yesterday again, after updating to Ubuntu 15.04. The relevant part from glxinfo: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-7f5a8ac 2015-04-25 utopic-oibaf-ppa) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile It fares better than fglrx, that crashes the game just past main menu.
Can you run the game with the environment variable R600_DEBUG=ps,vs,gs and post the output?
I am starting to believe the problem is hardware overheat: had a relatively long session with the PC case open and no incident. Can it be considered a bug? Is overheat prevention a tractable issue in software? Anyway, I tried to run with R600_DEBUG=ps,vs,gs, but I am not sure how to retrieve the information you need. I have the game from Steam, I ran it by typing in the terminal: $ export R600_DEBUG=ps,vs,gs $ steam -applaunch 220200 And it output to the terminal the usual, nothing specific to Mesa.
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.