[gm45] GPU lockup (ESR: 0x00000001 IPEHR: 0x7b001c04)

[Andreas Ehlert]

Binary package hint: xserver-xorg-video-intel

the application app-gpu-error-intel.py crashed

ACTHD: 0x03e7a53c
EIR: 0x00000000
EMR: 0xffffff05
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x7b001c04
IPEIR: 0x00000000
INSTDONE: 0xfdfffffe
INSTDONE1: 0xbfffeffc
    busy: Row 1, EU 2
    busy: CS
    busy: DM
    busy: VS0
    busy: VF

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.11.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-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.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1152x720 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAJ0Q54RVQAACoTAQOALx54LtxVo1lIniQRUFSla4BxAIEAgUCVD4GAlQCzAAEBITmQMGIaJ0BosDYA2igRAAAcAAAA/wBFQTkwMTk5NzAyNgogAAAA/QA3TB9TEQAKICAgICAgAAAA/ABCZW5RIEcyMjAwVwogAFw=
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAyDAEeAAAAAAARAQOAIRV4CrNAmVlTjSclUFQAAAABAQEBAQEBAQEBAQEBAQEB6hoAeFAgFDAYIEQAS88QAAAZAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBMR1BoaWxpcHNMQ0QKAAAA/gBMUDE1NFdYNS1UTEExAA==
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Tue Jul 6 21:01:05 2010
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: 1e86c0de
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100630.2)
InterpreterPath: /usr/bin/python2.6
MachineType: FUJITSU SIEMENS AMILO Pi 3525
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-6-generic root=UUID=fc377840-c2d4-46a2-97d4-fb470e3053f1 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 1e86c0de
UserGroups:

dmi.bios.date: 09/04/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.07C
dmi.board.name: F46
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 01
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.07C:bd09/04/2008:svnFUJITSUSIEMENS:pnAMILOPi3525:pvr10600934909:rvnFUJITSUSIEMENS:rnF46:rvr01:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: AMILO Pi 3525
dmi.product.version: 10600934909
dmi.sys.vendor: FUJITSU SIEMENS
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-6-generic

[Marc Deslauriers (mdeslaur)]

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.

[Geir Ove Myhr (gomyhr)]

Andreas, with the script /usr/share/apport/apport-gpu-error-intel.py we are (ab)using the crash report system to automatically collect information about a GPU error. So it is not really the application apport-gpu-error-intel.py that has crashed.

Often a GPU error will cause the computer to freeze or behave erratically in other ways. This makes it hard to collect any information manually and this is why this automatic information collection is useful. Sometimes the GPU error can happen during the shutdown of the computer and may therefore not be noticed. Apport will in both cases notice the crash report next time it boots and will offer to submit a bug report.

Did you notice any strange behaviour before apport offered to report this bug? Has this only happened once or does it happen regularly?

[Andreas Ehlert (logan-5)]

hey,

no. there is no strange behaviour before apport report this bug.
but this was happen regulary.

best regards
andreas

Am 09.07.2010 12:30, schrieb Geir Ove Myhr:
> Andreas, with the script /usr/share/apport/apport-gpu-error-intel.py we
> are (ab)using the crash report system to automatically collect
> information about a GPU error. So it is not really the application
> apport-gpu-error-intel.py that has crashed.
>
> Often a GPU error will cause the computer to freeze or behave
> erratically in other ways. This makes it hard to collect any information
> manually and this is why this automatic information collection is
> useful. Sometimes the GPU error can happen during the shutdown of the
> computer and may therefore not be noticed. Apport will in both cases
> notice the crash report next time it boots and will offer to submit a
> bug report.
>
> Did you notice any strange behaviour before apport offered to report
> this bug? Has this only happened once or does it happen regularly?
>
> ** Attachment added: "Gzipped result of intel_error_decode i915_error_state"
> http://launchpadlibrarian.net/51619510/intel_error_decode.txt.gz
>
>

[Geir Ove Myhr (gomyhr)]

Looking a little closer at the timing, I notice something strange. In the automatically collected information there is:
Date: Tue Jul 6 21:01:05 2010
which is when the GPU error happened and the logs should have been collected.
You reported the bug the next day (2010-07-07 - doesn't say what time of day), so this indicates that the information may have been collected in the evening when shutting down and you have been offered to submit the bug report when apport noticed the files in /var/crash/ the next day. However, XorgLog says:
[ 15.344] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 7 15:03:57 2010
So this file seems to be far newer than it should be. But it explains why there is no trace in it about what happened the evening before.
To add to the confusion, i915_error_state has the number of seconds since epoch in the first line, which should translate into
Tue, 06 Jul 2010 18:33:31 GMT
(according to http://www.epochconverter.com/).

It seems that our GPU error bug reporting mixes up some things.

[Chris Halse Rogers (raof)]

I don't quite see how that could happen - the gpu hook creates the whole apport report in one go, and I don't see where it would get munged between there and here.

My guess this could happen if the crash was during *suspend* and we caught the GPU errors before suspend and the Xorg log from after suspend? No, that doesn't quite work. Timezone?

[bugbot (bugbot)]

Hey Andreas,

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.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.