Radeon driver freezes GPU (reproducible)

[tuxator]

Hi,

System:
lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04

Package:
 apt-cache policy xserver-xorg-video-radeon
xserver-xorg-video-radeon:
  Installiert: 1:7.5.0-1ubuntu2
  Installationskandidat: 1:7.5.0-1ubuntu2
  Versionstabelle:
 *** 1:7.5.0-1ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

GPU: Radeon HD 5870

I upraded from Ubuntu 14.10 to 15.04 (x64) three days ago. After the upgrade I was not able to play a specific game (Star Conflict) with the open-source radeon drivers. (It does work with fglrx, very low FPS, but it does work)

The game did work on Ubuntu 14.10 hours before I upgraded, so a game bug or hardware bug can be excluded in my opinion.

Steps to reproduce:
 1. On a computer that uses the open-source radeon driver, start Star Conflict.
 2. log-in and start a custom game against bots
 3. start the match
 4. wait until the countdown is completed and you are launched

Expected result: I can fly around and shoot at those bots
Reality check: X freezes, I get a garbled up screen for a second and then the image I had before. I can still move my mouse, but nothing reacts. I can change to tty1 and kill the X server/gdm and restart it but it just shows me the exact same image I saw before.

Game logs are clean. dmesg/kern.log shows this
[quote]
[drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35).
[/quote]

I checked any log file I could find/think of, but kern.log is the only thing that shows anything. To get back to a working system I have to reboot.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-video-radeon 1:7.5.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Mar 30 18:17:50 2015
DistUpgraded: 2015-03-29 00:45:53,926 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.26, 3.16.0-34-generic, x86_64: installed
 virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cypress XT [Radeon HD 5870] [1002:6898] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:0346]
InstallationDate: Installed on 2014-01-11 (443 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=UUID=e00de04e-690f-4eae-a67a-badfe2d740c8 ro iommu=soft quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-ati
UpgradeStatus: Upgraded to vivid on 2015-03-28 (1 days ago)
dmi.bios.date: 02/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/05/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Mon Mar 30 18:10:55 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "ati" (module does not exist, 0)
 Failed to load module "ati" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: modeset

[tuxator (steffen-trekki)]

Forgot the entire kern.log file, sorry. Relevant stuff starts at 521.412751

[tuxator (steffen-trekki)]

I tried to get a backtrace via SSH, but no luck. I can start the gdb session and attach to the Xorg process, but the moment the bug occurs (screen freeze), I can't send any signals through my SSH session either. A few times I had to do a hard-reset because Magic SysReq was not recognized anymore (REISUB sequence).

There were two things that changed when attaching a gdb session, aside from REISUB not working:

1. I got a few frames from the game (meaning, my ship spawned and everything went fine for ~3 seconds)
2. the kern.log file had a bunch of this inside of it:
[ 745.250679] radeon 0000:02:00.0: GPU lockup (current fence id 0x000000000000f5a5 last fence id 0x000000000000f5b2 on ring 0)
[ 745.749923] radeon 0000:02:00.0: ring 0 stalled for more than 89868msec
[ 745.749932] radeon 0000:02:00.0: GPU lockup (current fence id 0x000000000000f5a5 last fence id 0x000000000000f5b2 on ring 0)
[ 746.249238] radeon 0000:02:00.0: ring 0 stalled for more than 90368msec
[ 746.249247] radeon 0000:02:00.0: GPU lockup (current fence id 0x000000000000f5a5 last fence id 0x000000000000f5b2 on ring 0)
[ 746.748547] radeon 0000:02:00.0: ring 0 stalled for more than 90868msec
[ 746.748556] radeon 0000:02:00.0: GPU lockup (current fence id 0x000000000000f5a5 last fence id 0x000000000000f5b2 on ring 0)

[tuxator (steffen-trekki)]

one of the recent updates changed the behaviour. I can now always see the ingame screen and sometimes even move around for a few seconds. Also some new stuff in dmesg.

After some research I was also able to enable sysrq again, so I did a sysrq L. I also found a Troubleshooting site on the ubuntu wiki that pointed to the usage of radeontool and the /sys/kernel/debug/dri/0 directory so I copied some files ( that seemed relevant judging by their name) from there, too.

And I'd appreachiate it if someone with a tiny bit more knowledge could give me a hand here. Either helping me in obtaining more informations or even fixing the problem. I mean, this is something like a dream-bug for a software developer with knowledge of the subsystems involved. It's 100% reproducible. What more do you need?

[tuxator (steffen-trekki)]

I tried getting some more logs. I did the following in a bash:
[code]
export LIBGL_DEBUG=verbose
export MESA_DEBUG=1
export MESA_LOG_FILE=/home/tuxator/mesa_errs.log
steam &>/home/tuxator/steam_errs.log
[/code]

steam_errs.log has nothing of interest, but mesa_errs has these two errors:
[code]
Mesa: User error: GL_INVALID_VALUE in glViewport(0, 0, -1, -1)
Mesa: User error: GL_INVALID_ENUM in glMatrixMode(mode)
[/code]
over and over again, until it's only the glMatrixMode error.

[madbiologist (me-again)]

The next step would be to report this information upstream at bugs.freedesktop.org and then link that bug report to this one by clicking on "Also affects project" at the top of this page. They might ask you to try a more recent kernel version - if they do, PPAs of recent kernels are available at http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how to install and uninstall them are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds

[penalvch (penalvch)]

tuxator, as per http://www.gigabyte.com/products/product-page.aspx?pid=4001#bios an update to your computer's buggy and outdated BIOS is available (FE). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status New. Otherwise, please mark this as Invalid.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]

[APolihron (apolitech)]

i can confirm this bug. this is not the only game with this problem team fortress 2 have the same problem.
The bug persist in 16.04.1 with amd r360 oc open source drivers

[penalvch (penalvch)]

APolihron (apolitech), it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]