Bug 48517

Summary:	[gm45] GPU hang in Ryzom (wine)
Product:	Mesa	Reporter:	Bryce Harrington <bryce>
Component:	Drivers/DRI/i965	Assignee:	Ian Romanick <idr>
Status:	RESOLVED INVALID	QA Contact:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity:	major
Priority:	medium	CC:	christopher.m.penalver
Version:	8.0
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	BootDmesg.txt CurrentDmesg.txt i915_error_state.txt XorgLog.txt

Description Bryce Harrington 2012-04-10 12:15:52 UTC

Forwarding this bug from Ubuntu reporter Forest Lake:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/978115

[Problem]
playing a game called Ryzom when this crash happened.... sorry, that is all i can tell you

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Chipset: gm45
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Tue Apr 10 23:54:41 2012
DistUpgraded: 2012-04-07 07:23:46,369 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
DuplicateSignature: [gm45] GPU lockup  render.IPEHR: 0x60020100 Ubuntu 12.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: No
GpuHangFrequency: Once a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Extensa 5630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=7A60735B60731D57 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup  render.IPEHR: 0x60020100
UpgradeStatus: Upgraded to precise on 2012-04-06 (3 days ago)
UserGroups:
 
dmi.bios.date: 08/05/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.19
dmi.board.name: Homa
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5630
dmi.product.version: 0100
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.6-0ubuntu1~ppa1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

Comment 1 Bryce Harrington 2012-04-10 12:16:12 UTC

Created attachment 59742 [details]
BootDmesg.txt

Comment 2 Bryce Harrington 2012-04-10 12:16:21 UTC

Created attachment 59743 [details]
CurrentDmesg.txt

Comment 3 Bryce Harrington 2012-04-10 12:16:39 UTC

Created attachment 59744 [details]
i915_error_state.txt

Comment 4 Bryce Harrington 2012-04-10 12:16:52 UTC

Created attachment 59745 [details]
XorgLog.txt

Comment 5 Eric Anholt 2012-08-08 19:41:33 UTC

Between it being under wine and no reliable way to reproduce, we can't treat this as a p1 bug.

Comment 6 Christopher M. Penalver 2016-02-26 00:49:41 UTC

Invalid downstream.

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.