[Bug 60391] [ilk regression] 3.7.x corrupt console image, hard hang starting X

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=60391

--- Comment #22 from Daniel Vetter <daniel at ffwll.ch> ---
(In reply to comment #21)
> I built stock 3.7.7 with IOMMU turned on, and patched, and 
> booted with and without the suggested option.  It booted to
> full X both times.  Without the patch, and built with IOMMU on,
> it fails reliably.  Without the patch, and without IOMMU, it
> boots and runs X with no apparent problems.
> 
> IOMMU turned on means:
> 
> # CONFIG_CALGARY_IOMMU is not set
> CONFIG_IOMMU_HELPER=y
> CONFIG_IOMMU_API=y
> CONFIG_IOMMU_SUPPORT=y
> # CONFIG_AMD_IOMMU is not set
> CONFIG_INTEL_IOMMU=y
> CONFIG_INTEL_IOMMU_DEFAULT_ON=y
> CONFIG_INTEL_IOMMU_FLOPPY_WA=y
> # CONFIG_IOMMU_STRESS is not set

Have you also tested what happens with an IOMMU-enable kernel, but adding
intel_iommu=igfx_off on the kernel cmdline? That is a slightly different mode
of "IOMMU disabled" which we need to test separately.

> This is not to say there are no problems.  The 3.6 and 3.7
> kernels are prone to freezing, with no mouse pointer motion,
> no response to keyboard input, and no response to ping, about
> once a week on this machine, but I don't know how to get any
> diagnostics out when it happens.

Should be fixed in latest stable updates, see bug #55984

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130217/dc14dc0f/attachment.html>