I believe this is fixed in the latest linux upload (the relevant change
was to make vesafb modular again):
linux (2.6.38-7.36) natty; urgency=low
[ Andy Whitcroft ]
* Revert "SAUCE: KLUDGE: work around failed 'shrink-wrap' compiler
optimisation"
* purge last vestiges of maverick
* [Config] switch CONFIG_FB_VESA back to module
[ Chris Wilson ]
* SAUCE: drm/i915: Fix pipelined fencing
- LP: #717114
[ Loïc Minier ]
* Include nls_cp437 module in virtual for fat
- LP: #732046
* Support arch= cross-compilation for any arch
* Fix couple of typos in 0-common-vars.mk
* Enforce DEFAULT_MMAP_MIN_ADDR on armhf
* Add armhf to Debian -> Linux arch map
* Add initial armhf.mk
* Enable common packages for armhf
[ Upstream Kernel Changes ]
* Yama: fix default relationship to check thread group
- LP: #737676
-- Andy Whitcroft <a...@canonical.com> Fri, 18 Mar 2011 18:18:02 +0000
** Changed in: linux (Ubuntu Natty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/702090
Title:
i965gm GPU lockup if vesafb is left loaded (EIR: 0x00000010 PGTBL_ER:
0x00000100) - *ERROR* EIR stuck: 0x00000010, masking
_______________________________________________
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
