Task hung when using GPU

[Lucas Clemente Vella]

When I try to run the game Team Fortress 2 (freely available from Steam) with linux-generic kernel and free Radeonsi Gallium driver from Mesa, latest version updated from a PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers), the game hungs at the loading screen, won't die with SIGKILL, and will print periodically this message in dmesg:

[ 910.474207] radeon 0000:01:00.0: bo ffff88006da3bc00 va 0x00000323bc conflict with (bo ffff8800647f0000 0x00000323bc 0x00000323bc)
[ 1080.007000] INFO: task hl2_linux:2675 blocked for more than 120 seconds.
[ 1080.007003] Tainted: G OE 3.19.0-25-generic #26-Ubuntu
[ 1080.007004] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1080.007004] hl2_linux D ffff8801987cfcb8 0 2675 2672 0x20020000
[ 1080.007007] ffff8801987cfcb8 ffff88019930ce80 0000000000014240 ffff8801987cffd8
[ 1080.007008] 0000000000014240 ffff8801a82993a0 ffff88019930ce80 0000000000200046
[ 1080.007009] ffff88006da3bdf0 ffff88006da3bdf4 ffff88019930ce80 00000000ffffffff
[ 1080.007011] Call Trace:
[ 1080.007017] [<ffffffff817c71b9>] schedule_preempt_disabled+0x29/0x70
[ 1080.007019] [<ffffffff817c9075>] __mutex_lock_slowpath+0x95/0x100
[ 1080.007020] [<ffffffff817c9103>] mutex_lock+0x23/0x40
[ 1080.007035] [<ffffffffc0b6f0b0>] radeon_gem_object_close+0x70/0x120 [radeon]
[ 1080.007042] [<ffffffffc06faa6c>] drm_gem_handle_delete+0xac/0x100 [drm]
[ 1080.007044] [<ffffffff811f72c5>] ? __sb_end_write+0x35/0x70
[ 1080.007048] [<ffffffffc06fb125>] drm_gem_close_ioctl+0x25/0x30 [drm]
[ 1080.007052] [<ffffffffc06fba6f>] drm_ioctl+0x1df/0x680 [drm]
[ 1080.007054] [<ffffffff81234dde>] ? fsnotify+0x37e/0x530
[ 1080.007062] [<ffffffffc0718775>] drm_compat_ioctl+0x35/0x40 [drm]
[ 1080.007071] [<ffffffffc0c342f5>] radeon_kms_compat_ioctl+0x25/0x30 [radeon]
[ 1080.007073] [<ffffffff81249b20>] compat_SyS_ioctl+0xc0/0x320
[ 1080.007075] [<ffffffff817cdf2a>] sysenter_dispatch+0x7/0x21

Installing linux-lowlatency solved the problem. My GPU is reported from mesa as being a AMD TAHITI.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-generic 3.19.0.26.25
ProcVersionSignature: Ubuntu 3.19.0-26.28-lowlatency 3.19.8-ckt4
Uname: Linux 3.19.0-26-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: lucas 3705 F.... pulseaudio
 /dev/snd/controlC2: lucas 3705 F.... pulseaudio
 /dev/snd/controlC1: lucas 3705 F.... pulseaudio
 /dev/snd/controlC0: lucas 3705 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sat Aug 22 17:22:25 2015
HibernationDevice: RESUME=UUID=d49e649c-f1dc-44c4-abd1-357220cf8a95
InstallationDate: Installed on 2015-07-05 (48 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
ProcFB:
 0 radeondrmfb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-lowlatency root=UUID=c0557b65-d473-42d2-96e3-5546f8923821 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-26-lowlatency N/A
 linux-backports-modules-3.19.0-26-lowlatency N/A
 linux-firmware 1.143.3
RfKill:

SourcePackage: linux
UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97M-D3H
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.:bvrF2:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z97M-D3H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alberto Salvia Novella (es20490446e)]

Team Fortress 2, as many Steam games do, do not use Ubuntu native libraries. Instead Steam provides its own ones, which usually are older and do not support the latest Radeon graphics.

If you are experiencing this bug with a game outside Steam, please set its status back to "confirmed". Thank you.

[Lucas Clemente Vella (lvella-gmail)]

I couldn't disagree more with the closing of this bug, for two reasons:

1) Steam and Steam's games sometimes do replace completely userspace libraries, like C++ standard library, SDL and/or FreeType, but never OpenGL or graphic drivers, they always relies on systems installed implementation for that, and for Steam first run, it asks for sudo password and installs OpenGL via apt-get automatically.

2) Most importantly, this is a bug were a process hungs in kernelspace (I can't even kill it with SIGKILL), so no matter what library or application or any userspace code I could be running, this should never happen. No custom library Steam could install as my non-privileged user is able to change code running in kernelspace. This is why this bug was filled against "linux" package.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.2 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-rc8-unstable/

[penalvch (penalvch)]

Lucas Clemente Vella, the next step is to fully reverse commit bisect from kernel 3.19 to 4.2-rc8 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]