i915 device or resource busy in some 3D apps

[Ruslan]

How to reproduce:
1. Install wine
2. Install GTAVC in wine
3. Try starting GTAVC in 1280x1024 resolution, press <Enter> twice to skip non-working intro videos, and when the menu appears, try moving mouse cursor to select "New Game"
4. See GTAVC crash with "Deivce or resource busy" in the terminal.
Dmesg suggests that it's i915 driver bug.
This has worked correctly in e.g. Ubuntu Lucid.

Mainline kernel bisect revealed:
3.4.56 good
3.4.55 bad

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-51-generic-pae 3.2.0-51.77
ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48
Uname: Linux 3.2.0-51-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ruslan 1473 F.... kded4
                      ruslan 1669 F.... kmix
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf20c0000 irq 40'
   Mixer name : 'Realtek ALC880'
   Components : 'HDA:10ec0880,08800000,00090500'
   Controls : 39
   Simple ctrls : 22
Date: Sat Aug 3 12:54:19 2013
HibernationDevice: RESUME=UUID=ad008e92-9144-4dca-b2cc-b9af0b200051
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic-pae root=UUID=67cea86f-7ed6-4be5-b574-afde6eb9e831 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-51-generic-pae N/A
 linux-backports-modules-3.2.0-51-generic-pae N/A
 linux-firmware 1.79.6
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: 8I915GMF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/27/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn8I915GMF:rvrx.x:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Ruslan, as per http://www.gigabyte.com/products/product-page.aspx?pid=1796#bios an update is available for your BIOS (F8). If you update to this, does it change anything?

If not, 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

Thank you for your understanding.

[Ruslan (b7-10110111)]

Hi Christopher,

In fact I've already upgraded it years ago. It seems just a bug that F4 version is returned by DMI (it was factory default). See this POST screen photo [1].
Here's output of the command you asked:

F4
09/27/2005

As you can see, date coincides with F8 version release listed in your link.

[1]: http://i0.simplest-image-hosting.net/picture/03082013567.jpg

[penalvch (penalvch)]

Ruslan, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Ruslan (b7-10110111)]

> If not, could you please both specify what happened
Basically I try to move mouse cursor in the GTAVC game menu, and get crash, where wine desktop window closes and I get this message:
intel_do_flush_locked failed: Device or resource busy

Sometimes I can get into second menu, and only after several more mouse moves the crash occurs (maybe more related to timing than to mouse movement).

Also, forgot to mention that this only happens if I use fullscreen GTAVC, i.e. 1280x1024. If I select smaller resolution (by deleting game settings file) (which makes wine desktop window smaller), no crash occurs.
Command line to start the game is like this:
cd ~/opt/Games/GTA-VC/ && wine explorer /desktop=g,1280x1024 gta-vc.exe

This all was when kwin compositor is disabled. If I enable compositing, the same symptoms occur, plus trying to open Yakuake window by pressing F12 after crash makes screen flicker with several previously showed images like blue background of wine desktop, yakuake window, plasma desktop etc. Disabling compositing after this makes the system usable, but reenabling still leads to similar artifacts.

[penalvch (penalvch)]

Ruslan, so what kernel did you test specifically?

[Ruslan (b7-10110111)]

Tested on kernel v3.11-rc3-saucy, the bug appears fixed there.

[Ruslan (b7-10110111)]

> Ruslan, so what kernel did you test specifically?
This one: h ttp://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/linux-image-3.11.0-031100rc3-generic_3.11.0-031100rc3.201307290035_i386.deb
Although I use Precise, this one is for Saucy, but still does its job.

[penalvch (penalvch)]

Ruslan, the next step is to find the earliest mainline kernel that fixed this issue. Could you please do this via https://wiki.ubuntu.com/Kernel/MainlineBuilds ?

[Ruslan (b7-10110111)]

3.4.56 good
3.4.55 bad

[penalvch (penalvch)]

Ruslan, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Ruslan (b7-10110111)]

Erm... well I'll check, but why would it remain if according to [1] Ubuntu Saucy uses linux >= 3.8, and the bug is fixed in 3.4.56 as I said in comment #11 and remains fixed until 3.11?

[1]: https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes#Updated_Packages

[Ruslan (b7-10110111)]

OK, I've checked Saucy with latest upgrades and the bug (not surprisingly) doesn't reproduce there. (Kernel 3.10.0-6-generic is used there)

[penalvch (penalvch)]

Ruslan, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

[Ruslan (b7-10110111)]

Of course I need a backport to at least Precise — it's an LTS release, and the bug is an application crash because of device driver, so it has to be fixed.

[penalvch (penalvch)]

Ruslan, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Ruslan (b7-10110111)]

Christopher, I'm not sure what you mean by steps 1 and 2:
1. Check that the bug is fixed in the current development release, and that its bug task is "Fix Released"
This is already done and you've marked it as "Fix Released"
2. Ensure that the bug report for this issue is public.
I'm pretty sure it is.

Did you mean some other steps 1 & 2?