Le 24/02/2013 17:30, Ben Hutchings a écrit :
On Sun, 2013-02-24 at 17:13 +0100, Pierre AUSSAGUEL wrote:
Le 24/02/2013 08:08, Ben Hutchings a écrit :
[...]
If we can't come up with a workaround, this should be mentioned in the
release notes to prevent a regression on upgrade. Please feel free to
remind me in that case so I can come up with some wording (though I
also wouldn't mind if someone else does).
"Graphics rendering may be very slow on Intel 'Ironlake M' GPUs (PCI ID
8086:0046) when an IOMMU (VT-d) is enabled. The IOMMU functionality can
be disabled for the GPU by adding the kernel parameter
'intel_iommu=igfx_off'."
Do you want that I test with intel_iommu=igfx_off in 3.7, or even in 3.2 ?
Do you want that I test too intel_iommu=off in 3.2 ?
For now, the system works well with 3.7 but that would be better to use
a stable kernel for sure !
Please test intel_iommu=igfx_off in both 3.7 and the 3.2+drm kernel
linked from <http://bugs.debian.org/687442#131>.
(The next upload to unstable will include those drm changes.)
Ben.
I have made a few tests :
3.7 + intel_iommu=igfx_off -> problem still here (no messages at all)
3.2 + intel_iommu=igfx_off -> problem still here (not sure about missing
IRQ messages)
3.2 + intel_iommu=off -> problem still here (with missing IRQ messages)
3.2+drm + intel_iommu=off -> problem still here (with missing IRQ messages)
The only stable solution (using gnome shell of course) is 3.7 +
intel_iommu=off
--
Pierre AUSSAGUEL
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512ca5eb.7060...@yahoo.fr
