Re: Attempting to start X with intel driver hangs system
clone 683167 -1
reassign 683167 libdrm-intel1 2.4.33-3
forcemerge 683167 684650
tags 683167 + upstream patch
notforwarded -1
reassign -1 src:linux 3.2.23-1
found -1 linux-2.6/2.6.32-45
retitle -1 kernel: missing support for Ivy Bridge GT2 Server
# cc22a938fc1d (drm/i915: add Ivy Bridge GT2 Server entries)
tags -1 = upstream patch moreinfo
quit
Hi,
Maik Zumstrull wrote:
> This is on an Ivy Bridge Xeon E3 with GPU. I thought it was the X
> driver, because i915 KMS works fine for the console, it only crashes
> when trying to bring up X. But I pulled in the 2.20.2 driver today and
> it still happens. So I now think the problem is in the kernel.
[...]
> 3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come
> up, but you can switch to a console and reboot. 3.4 needs the reset
> button.
Jonathan Nieder wrote:
> Support for this GPU seems to have been added by
>
> cc22a938fc1d drm/i915: add Ivy Bridge GT2 Server entries
>
> which was merged in 3.4-rc2.
Chris Wilson wrote:
> Aha! Indeed libdrm is out-of-date, you need libdrm 2.4.34 (or a backport of the
> PCI ID patch, or a backport of the assertion removal).
>
> commit e057a56448e2e785f74bc13dbd6ead8572ebed91
> Author: Eugeni Dodonov <eugeni@dodonov.net>
> Date: Thu Mar 29 21:03:29 2012 -0300
>
> intel: add Ivy Bridge GT2 server variant
[...]
> commit 9a2b57d229fe3e6a1c9799e8cd5397969202d223
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Wed Jul 25 16:28:59 2012 +0100
>
> intel: Bail gracefully if we encounter an unknown Intel device
>
> Otherwise we end up with X hitting a fail-loop as the embedded libGL
> stacks asserts whilst initialising.
Reassigning.
Thanks,
Jonathan
Reply to: