[sandybridge-m-gt2] GPU lockup IPEHR: 0x01800100 IPEHR: 0x01000000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
These traces are probably identical...
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Chipset: sandybridge-m-gt2
Date: Tue Jan 22 17:56:45 2013
DistroCodename: raring
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x01800100 IPEHR: 0x01000000 Ubuntu 13.04
ExecutablePath: /usr/share/
GpuHangFrequency: This is the first time
InstallationDate: Installed on 2012-03-16 (311 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
InterpreterPath: /usr/bin/python3.3
MachineType: ASUSTeK Computer Inc. UX31E
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu4
libdrm2 2.4.41-0ubuntu1
xserver-
SourcePackage: xserver-
Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x01800100 IPEHR: 0x01000000
UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
UpgradeStatus: Upgraded to raring on 2013-01-10 (12 days ago)
UserGroups:
XorgConf:
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "AccelMethod" "sna"
EndSection
dmi.bios.date: 06/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.213
dmi.board.
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: UX31E
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1103059, 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.