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: Sun, 20 Jan 2013 22:52:49 +0100 [thread overview]
Message-ID: <50FC6731.3020209@ionic.de> (raw)
In-Reply-To: <CAKMK7uExHc=PEBpn2vPrX+sQcv=U7VuvsJHRxc-SSOh=_G_1Dg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
Hi Daniel,
the patch does work, i.e., it turns off DMAR for the graphics card and
alleviates the freezes when loading i915/kms.
However, still seeing random machine freezes with it (being consistent with the
behavior I've experienced with intel_iommu=igfx_off).
The patch + forcing RWBF is working, too. Interestingly, this version didn't
randomly freeze yet, after more than 5 hours of uptime! I'll leave the box
running until tomorrow to make sure I did stick around long enough.
All those tested kernels were able to handle USB and PCI(e) devices.
I still have to test turning off IOMMU in general and Intel IOMMU specifically.
Will probably do this tomorrow.
Thank you so far! :)
Mihai
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4506 bytes --]
next prev parent reply other threads:[~2013-01-20 21:52 UTC|newest]
Thread overview: 12+ 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
2013-01-19 16:25 ` Daniel Vetter
2013-01-19 16:26 ` Mihai Moldovan
2013-01-19 16:30 ` Daniel Vetter
2013-01-20 21:52 ` Mihai Moldovan [this message]
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: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=50FC6731.3020209@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox