8086:2a42 [gm45] GPU lockup resume from hibernate (EIR: 0x00000010 ESR: 0x00000011 PGTBL_ER: 0x00000003 )

I'm duping 683314 here even though the error codes differ, because it's the same reporter and same symptoms (lockup on resume from hibernate).

In natty, the desktop team is deprecating hibernate (the kernel team wants to disable it completely, but we'll see). For this reason I'm setting the priority to Low, and recommending that the feature not be used if it exhibits this bug. Sorry, I know that's probably not the answer you hope to hear, but apparently hibernate has been extremely buggy in general, and is often found to be far too slow anyway.

[193189.288729] render error detected, EIR: 0x00000010
[193189.288733] IPEIR: 0x00000000
[193189.288736] IPEHR: 0x00000000
[193189.288738] INSTDONE: 0xfffffffe
[193189.288740] INSTPS: 0x00000000
[193189.288742] INSTDONE1: 0xffffffff
[193189.288745] ACTHD: 0x02000000
[193189.288747] page table error
[193189.288749] PGTBL_ER: 0x00000003
[193189.288753] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

This looks a lot like bug #702090

Actually, looking at the previous line:

[193189.282139] video LNXVIDEO:01: Restoring backlight state
[193189.288729] render error detected, EIR: 0x00000010
[193189.288733] IPEIR: 0x00000000
...

Hi,

Thanks for reporting this X gpu lockup bug in Ubuntu maverick.

In my opinion GPU lockups are one of the most frustrating kinds of bugs, both as a user and a developer. I want take a few moments of your time to explain the situation with these types of bugs.

For some reason, -intel has been plagued with these freeze bugs for a long time. In the past -intel has had options to switch to legacy memory or rendering technologies as workarounds, but Intel tends to drop obsolete code pretty aggressively and unfortunately in maverick these workarounds are not available.

As a policy, Intel engineers look only at bugs that are seen in the most recent release of their drivers. With older versions of their drivers, such as the version in maverick, we're on our own.

On the plus side, they provide good tools for gathering debug data about the bugs, such as the intel_gpu_dump too. Unfortunately, the version of Apport in maverick doesn't capture the dmesg or X logs correctly (it collects the files at the time of freeze, but then overwrites them with clean, unhelpful versions when it goes to file the report for you.)

The version of these diagnostic tools in natty has been fixed up, and is allowing us to analyze GPU lockups a lot easier. This has helped us solve several of the bugs, and given us a handle on some of the more challenging ones.

Backporting these fixes may not be feasible though; by their nature the fixes for these type of bugs tend to be very low level, esoteric, and risky of causing something else to regress. Because the freezes are often hard to reproduce, it's not always possible to verify fixes anyway. It may be that our best bet is to focus on natty.

But for now, since these freezes typically require kernel patches to solve, I'm moving your bug report to the kernel package. They may be able to point you to a newer kernel likely to help with this issue.

crf, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]