[clarkdale] GPU crash while playing doom 3

Bug #618076 reported by Fred Odendaal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

At a certain point in the doom 3 video game the screen freezes for about 5 seconds and then alternately flashes between black and some text which can't be read because the flashing cycles so quickly.

I am using the native Linux version of Doom 3. This crash happens almost half way through the game and is consistent. I have a checkpoint just before where the crash happens so I can recreate it easily.

The last time it crashed I was running apport and was able to get into a terminal with CTRL-ALT-1. I saved the output from dmesg, Xorg.0.log and i915_error_state. I'll attach these files to this error report.

If there is any other information required please let me know as I can readily reproduce this bug.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
CheckboxSubmission: 5a6950b34d04ad8c3d59efea84488501
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Sat Aug 14 23:48:45 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: Gigabyte Technology Co., Ltd. H55M-USB3
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=UUID=bff8a402-5573-4ab0-bd41-2322d103d063 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 02/05/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: H55M-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd02/05/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55M-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-24-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12)
     Subsystem: Giga-byte Technology Device [1458:d000]

Revision history for this message
Fred Odendaal (fred-odendaal) wrote :
Revision history for this message
Fred Odendaal (fred-odendaal) wrote :
Revision history for this message
Fred Odendaal (fred-odendaal) wrote :
Bryce Harrington (bryce)
tags: added: crash
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Fred Odendaal (fred-odendaal) wrote :

No graphics card. GPU is onboard Intel I3 530 Core processor.

Crash can be avoided by turning off 3D acceleration in the xorg.conf file by putting the following line in the Device section:
Option "DRI" "False"

However, this makes the game so slow it's almost unplayable.

Revision history for this message
Fred Odendaal (fred-odendaal) wrote :

Upgraded OS to Ubuntu 10.10 - Kernel 2.6.35-24-generic (64 bit). Crash no longer occurs!

However it no longer picks up the 32bit libraries by default. I had to add this line to the beginning of the doom3 script to get it to work:

export LD_LIBRARY_PATH=/usr/lib32:$LD_LIBRARY_PATH:.

I think this bug can be closed.

bugbot (bugbot)
description: updated
bugbot (bugbot)
summary: - GPU crash while playing doom 3
+ [clarkdale] GPU crash while playing doom 3
Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for following up on this bug Fred, I'll close it as per your suggestion. Sounds to me like it was a fault in mesa fixed in a newer version.

affects: xserver-xorg-video-intel (Ubuntu) → mesa (Ubuntu)
Changed in mesa (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.