Forwarding this bug from Ubuntu reporter Travis Watkins:
In Ubuntu we're seeing a spattering of GPU lockups during boot that recover. The user doesn't notice anything wrong (or just a black screen or other minor symptom), but the gpu hang is detected by apport and collected as a bug report.
Analysis indicates that if vesafb is disabled, the phantom(?) gpu lockups don't occur, thus suggesting something related to that.
This bug report was filed against the 2.6.37 kernel but verified against current X bits; I'm forwarding it because it was the first instance of this issue reported within the current development period, and because it has verified the workaround of disabling vesafb. Other reporters have reported very similar bugs with the 2.6.38 kernel (same gpu dump error codes, same symptoms, same gpu).
I'm assuming this is because my suspend failed but I also had a black screen on boot until X started so perhaps it was something plymouth related.
From GPU dump:
busy: Projection and LOD
busy: Bypass FIFO
busy: Color calculator
[ 12.615203] [drm] initialized overlay support
[ 12.838827] render error detected, EIR: 0x00000010
[ 12.838830] page table error
[ 12.838831] PGTBL_ER: 0x00000100
[ 12.838834] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=3fa2b187-0edf-45a7-add7-17bf24470864 ro vt.handoff=7 quiet splash
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=3fa2b187-0edf-45a7-add7-17bf24470864 ro vt.handoff=7 quiet splash
dmi.bios.vendor: Apple Inc.
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.vendor: Apple Inc.
dmi.sys.vendor: Apple Inc.
version.libdrm2: libdrm2 2.4.22-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 7.9+repack-1ubuntu3
version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu7
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.13.901-2ubuntu2
Created attachment 43078 [details]
Created attachment 43079 [details]
Created attachment 43080 [details]
Created attachment 43081 [details]
The user ruled out the aforementioned suspicion of a suspend issue by reproducing the lockup after a fresh boot.
Here is the GPU dump: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/702090/+attachment/1792167/+files/IntelGpuDump.txt
Note that the gpu dump and error state files were collected from an older X stack than the dmesg and Xorg.0.log.
The user still sees the bug with the .38 kernel, 2.14.0 -intel, and current X stack.
Following will be a set of files from the same user, same hardware, same issue but with this more current set of software versions.
Created attachment 43082 [details]
Created attachment 43083 [details]
Created attachment 43084 [details]
Created attachment 43085 [details]
Newest GPU dump at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/714805/+attachment/1836996/+files/IntelGpuDump.txt
Here are some other bugs reported to Ubuntu which I suspect to be dupes of this:
(and half a dozen others linked to #711275)
Don't use two conflicting drivers for the same hardware.
The underlying problem of conflicts with vesafb may or may not still be worth further investigation but the surface problem of gpu lockups, which seems specific to ubuntu, has been resolved in ubuntu.