Page fault in drm while using Unity's software center overlay

[Bryce Harrington]

Was attempting to install Evolution to try to repro bug 874146. Opened Unity's software scope overlay, clicked on the More Software button, typed in Evolution and clicked the Evolution Mail and Calendar icon that appeared. Suddenly X crashed and the lightdm login screen appeared. I had dmesg open in another window during this time and saw this appear in the dmesg output at the moment X crashed:

[ 163.755960] [drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer

Next, I re-logged in. The password was accepted and the screen cleared, showing the standard purple background, except it was tiled 2x2. At that point it froze up. The following got printed to dmesg in my ssh session. I then filed the bug.

[ 184.677808] [<f89b1adf>] i915_gem_evict_something+0xef/0x370 [i915]
[ 184.677858] [<c103c8d8>] ? __kunmap_atomic+0x88/0x90
[ 184.679967] [<f89ad6b4>] i915_gem_object_bind_to_gtt+0x1b4/0x400 [i915]
[ 184.680005] [<f89b00ee>] i915_gem_fault+0x20e/0x240 [i915]
[ 184.680005] [<c11138fe>] __do_fault+0x6e/0x550
[ 184.680005] [<f89af79f>] ? i915_gem_set_domain_ioctl+0xaf/0xf0 [i915]
[ 184.680005] [<c1117265>] handle_pte_fault+0x95/0x2c0
[ 184.680005] [<c111767e>] handle_mm_fault+0x15e/0x2c0
[ 184.680005] [<c15a802b>] do_page_fault+0x15b/0x490
[ 184.680005] [<f8543bb0>] ? drm_copy_field+0x80/0x80 [drm]
[ 184.680005] [<c1154139>] ? do_vfs_ioctl+0x79/0x2d0
[ 184.680005] [<c11543db>] ? sys_ioctl+0x4b/0x80
[ 184.680005] [<c15a7ed0>] ? vmalloc_fault+0x190/0x190
[ 184.680005] [<c15a5317>] error_code+0x67/0x6c

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+7ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic-pae 3.2.0-rc5
Uname: Linux 3.2.0-4-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Dec 16 11:36:49 2011
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:1458]
   Subsystem: Fujitsu Limited. Device [10cf:1458]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111121)
MachineType: FUJITSU LifeBook T4410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic-pae root=UUID=74b73169-6ac4-4698-bb5e-1f9b21250507 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB206
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A40R8CE708EA1001
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd09/30/2009:svnFUJITSU:pnLifeBookT4410:pvr:rvnFUJITSU:rnFJNB206:rvr:cvnA40R8CE708EA1001:ct10:cvr:
dmi.product.name: LifeBook T4410
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
version.libdrm2: libdrm2 2.4.27-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Bryce Harrington (bryce)]

Probably not relevant but this is what was displayed on the screen at time of freeze.

[Bryce Harrington (bryce)]

After updating to latest kernel, the crash seems to have gone away; at least, I can't seem to reproduce it as easily now.