Yura, you can ignore the automatic notification from Bryce. you already tested drm-intel-next which has all the bug fixes he mentions.
Thanks a lot for testing. It seems that the automatic and manual logs are fairly consistent, but not 100%. dmesg output is consistent. I think the important part is [ 21.609431] render error detected, EIR: 0x00000010 [ 21.609496] page table error [ 21.609548] PGTBL_ER: 0x00000102 [ 21.609605] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking so there are two different error registers that are being triggered, EIR and PGTBL_ER. The only thing I find a bit confusing is that in IntelGpuDump.txt in bug 532295 it says PGTBL_ER: 0x00000112 whereas i915_error_state, dmesg, and the other IntelGpuDump.txt says that this has value 0x00000102. If you find this interesting, the registers are described in http://intellinuxgraphics.org/VOL_1_graphics_core.pdf . You say that "display freeze after login with linux 2.6.33-997". What happens then? Do you have to use the power button? Does Ctrl-Alt-F1 work? Does the mouse cursor move? Does the apport-generated bug report appear the next time you boot after the freeze? I'm just trying to get a picture of how these bugs manifest themselves with the new kernels. I can't draw any conclusions yet, but your help definitely helps us understand what is going on. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Triaged -- [i945gm] GPU lockup 585b0b66f331dfb836dfc05f1eb2e8a8 https://bugs.launchpad.net/bugs/532100 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
