[i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011)

Bug #747801 reported by mkoca
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

emesene login crash + opera web browser crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
Chipset: i915gm
Date: Fri Apr 1 23:55:12 2011
DistroCodename: natty
DistroVariant: ubuntu
DuplicateSignature: (ESR: 0x00000001 IPEHR: 0x02000011)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: FUJITSU SIEMENS Amilo M1450 Series
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=5d2f3b25-0f21-40be-957e-f4925d877440 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.6+4ubuntu1
 libdrm2 2.4.23-1ubuntu5
 xserver-xorg-video-intel 2:2.14.0-4ubuntu5
SourcePackage: xserver-xorg-video-intel
Title: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011)
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)
UserGroups:

dmi.bios.date: 11/17/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02C
dmi.board.name: M50EI0
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02C:bd11/17/2005:svnFUJITSUSIEMENS:pnAmiloM1450Series:pvr:rvn:rnM50EI0:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: Amilo M1450 Series
dmi.sys.vendor: FUJITSU SIEMENS
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

Revision history for this message
mkoca (mkoca) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #752125, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
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.