All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: LKML <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: i915-related and general system freezes with specific kernel config // IOMMU
Date: Sat, 19 Jan 2013 17:13:14 +0100	[thread overview]
Message-ID: <50FAC61A.9060503@ionic.de> (raw)
In-Reply-To: <CAKMK7uExHc=PEBpn2vPrX+sQcv=U7VuvsJHRxc-SSOh=_G_1Dg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

* On 19.01.2013 02:27 PM, Daniel Vetter wrote:
> You have a gen4.5 chipset which is known to be utterly broken for
> IOMMU+intel gpu.

Nice description for what I'm seeing. ;)

After some more hours of uptime I'm inclined to say, that "intel_iommu=off
iommu=off" fixes my random freezes as well.
Alas, the USB and PCI(e) problems are still around, but I could test recompiling
3.7.2 with Intel IOMMU turned off completely in the kernel config.
Interestingly, my 3.0.2 kernel which worked fine for so long doesn't even *have*
support for VT-d/Intel IOMMU. This could explain why I wasn't bit by those
problems on all previous versions.


> [...] and we've never added the proper
> quirks. See https://bugzilla.kernel.org/show_bug.cgi?id=51921 for a
> proposed patch to fix this (i.e. automatically set
> intel_iommu=igfx_off for affected platfroms). Testing highly welcome.

From a quick glance, I don't think this patch will work as-is, my PCI ID 2e12 is
missing.
I'll add it to the relevant section.

But even if it worked, I'd still have the "box freezes randomly" issue (mostly
within 5 to 60 minutes of uptime). :(
The only way to get rid of this is disabling Intel IOMMU as a whole via kernel
parameters intel_iommu=off iommu=off.

Anyway, I'll give it a try.

Best regards,



Mihai


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4506 bytes --]

  reply	other threads:[~2013-01-19 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 23:48 i915-related and general system freezes with specific kernel config // IOMMU Mihai Moldovan
2013-01-18 23:59 ` Mihai Moldovan
2013-01-19 13:27 ` Daniel Vetter
2013-01-19 16:13   ` Mihai Moldovan [this message]
2013-01-19 16:25     ` Daniel Vetter
2013-01-19 16:26     ` Mihai Moldovan
2013-01-19 16:30       ` Daniel Vetter
2013-01-19 16:30         ` Daniel Vetter
2013-01-20 21:52   ` Mihai Moldovan
2013-01-20 22:49     ` Daniel Vetter
2013-01-21 18:11       ` Mihai Moldovan
2013-01-22 18:15         ` Mihai Moldovan
2013-01-22 18:15           ` Mihai Moldovan
2013-01-22 18:52           ` Daniel Vetter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50FAC61A.9060503@ionic.de \
    --to=ionic@ionic.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwmw2@infradead.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.