Ubuntu
module-init-tools package

[MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001)

Bug #612816 reported by jazz41408 on 2010-08-03

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	module-init-tools (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

My computer was on the screen saver and it said failed then an error. I thought it shut down so I turned it back on and saw a crash on the top of my screen.

---
PCI ID: 0x2a42
EIR: 0x00000010
  PGTBL_ER: 0x00000001
  INSTPM: 0x00000000
  IPEIR: 0x00000000
  IPEHR: 0x00000000
  INSTDONE: 0xfffffffe
  ACTHD: 0x04000000
  INSTPS: 0x00000000
  INSTDONE1: 0xffffffff
---

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Chipset: gm45
DRM.card0.DisplayPort.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.DisplayPort.2:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.HDMI_Type_A.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1366x768
edid-base64: AP///////wAGrywSAAAAAAESAQOAHRB4CvnVlVVUkychUFQAAAABAQEBAQEBAQEBAQEBAQEBJhtWZFAAFjAwIDYAJaQQAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTMzWFcwMSBWMiAKADU=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Mon Aug 2 21:55:45 2010
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: 493062ea (EIR: 0x00000010)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
MachineType: Acer Aspire 3810TZ
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=0065d499-e523-4140-8de6-3fd980f71ef1 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup 493062ea (EIR: 0x00000010)
UserGroups:

dmi.bios.date: 05/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.03
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 3810TZ
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: dmi:bvnAcer:bvrV1.03:bd05/22/2009:svnAcer:pnAspire3810TZ:pvrV1.03:rvnAcer:rnAspire3810TZ:rvrPSMBOU-1234567:cvnAcer:ct1:cvrNone:
dmi.product.name: Aspire 3810TZ
dmi.product.version: V1.03
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-14-generic
xkbcomp:
Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
Exiting

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0229]

See original description

Tags:

Revision history for this message

jazz41408 (newviolinist) wrote on 2010-08-03:

BootDmesg.txt Edit (50.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (17.8 KiB, text/plain; charset="utf-8")
DRM.card0.SVIDEO.1.txt Edit (108 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.2 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (5.5 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (19.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (18.8 KiB, text/plain; charset="utf-8")
IntelGpuDump.txt Edit (1.2 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (23.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (828 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (667 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (5.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (729 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (232 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (109.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (250.6 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (11.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (28.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.1 KiB, text/plain; charset="utf-8")
i915_error_state.txt Edit (672.3 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (9.7 KiB, text/plain; charset="utf-8")

Bryce Harrington (bryce) on 2010-08-03

tags:	added: crash
Changed in xserver-xorg-video-intel (Ubuntu):
status:	New → Confirmed

Robert Hooker (sarvatt) on 2010-10-06

description:	updated
summary:	- [gm45] GPU lockup 493062ea (EIR: 0x00000010) + [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001)

Robert Hooker (sarvatt) on 2010-10-06

summary:	- [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001) + [MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: + 0x00000001)
Changed in xserver-xorg-video-intel (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-02-08:

[ 7159.618248] video LNXVIDEO:00: Restoring backlight state
[ 7159.620023] render error detected, EIR: 0x00000010
[ 7159.620023] IPEIR: 0x00000000
[ 7159.620023] IPEHR: 0x00000000
[ 7159.620023] INSTDONE: 0xfffffffe
[ 7159.620023] INSTPS: 0x00000000
[ 7159.620023] INSTDONE1: 0xffffffff
[ 7159.620023] ACTHD: 0x04000000
[ 7159.620023] page table error
[ 7159.620023] PGTBL_ER: 0x00000001
[ 7159.620023] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

Bug #672853 looks similar

Revision history for this message

bugbot (bugbot) wrote on 2011-02-19:

Hey jazz41408,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

Changed in xserver-xorg-video-intel (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

jazz41408 (newviolinist) wrote on 2011-02-19: Re: [Bug 612816] Re: [MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001)

The backlight still doesn't work in Maverick, but I am currently testing
Natty and the backlight works.

On Feb 18, 2011 11:01 PM, "bugbot" <email address hidden> wrote:

Hey jazz41408,

Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick
development period. But I see there's not been more comments on the bug
since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may
have been solved by kernel or X or other updates that occurred late in
the release; if so, would you mind please closing the bug for us? Go to
the URL mentioned in this bug report, click the yellow icon(s) in the
status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or
otherwise feel the bug no longer needs tracked in Launchpad, you can set
the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply
to this email saying so. (Or set the bug status to Confirmed.) If you
are able to re-test this against 11.04 Natty Narwhal (our current
development focus) and find the issue still affects Natty, please also
run 'apport-collect <bug-number>' while running natty, which will add
fresh logs and debug data, and flag it for the Ubuntu-X development team
to look at.

** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Incomplete

-- You received this bug notification because you are a direct subscriber of
the bug. https://bugs...
Incomplete

Bug description: Binary package hint: xserver-xorg-video-intel My computer
was on the screen s...

Revision history for this message

tetsuo55 (akira146) wrote on 2011-02-20:

Afaik this bug is still valid.

I have stopped using hibernation because of it, i will test it as soon as i get a chance to confirm its still there.

Revision history for this message

tetsuo55 (akira146) wrote on 2011-02-23:

I cannot test this, there is a regression that is making it impossible to hibernate right now

Revision history for this message

tetsuo55 (akira146) wrote on 2011-02-23:

i managed to hibernate from the terminal

I did not get this crash this time, i used to get it 100% of the time, so this might in fact be fixed

Revision history for this message

tetsuo55 (akira146) wrote on 2011-04-01:

Some bad news, the crash happened again, but this time its different because the system recovers and manages to boot up succesfully. Apport doesnt catch it though so no crash dump.

Is there any addtional information required?

tetsuo55 (akira146) on 2011-04-02

Changed in xserver-xorg-video-intel (Ubuntu):
status:	Incomplete → Opinion
status:	Opinion → Confirmed

bugbot (bugbot) on 2011-04-27

description:

updated

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-04-28:

Generally I've found that these EIR: 0x00000010 occur due to a conflict between the intel kernel driver and another video driver (such as vesafb for instance). There have been a few fixes in natty to better deal with this situation. Can you test natty and see if the issue still exists there?

affects:	xserver-xorg-video-intel (Ubuntu) → module-init-tools (Ubuntu)
Changed in module-init-tools (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-06-27:

#10

[Expired for module-init-tools (Ubuntu) because there has been no activity for 60 days.]

Changed in module-init-tools (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

tetsuo55 (akira146) wrote on 2011-06-27:

#11

I have not seen this crash for 60 days, and i have been using both hibernation and suspend.

So it might look like this is fixed, i have been using git nightly drivers for the past few 2 weeks which seem more compatible.

Changed in module-init-tools (Ubuntu):
status:	Expired → Confirmed
status:	Confirmed → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntumodule-init-tools package

[MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001)

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
module-init-tools package