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: Mon, 21 Jan 2013 19:11:44 +0100 [thread overview]
Message-ID: <50FD84E0.2090901@ionic.de> (raw)
In-Reply-To: <CAKMK7uEX0CG4LaVr3jkcPeQYTYFseG-G5f0_2zKTuCcfVfhF2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
* On 20.01.2013 11:49 PM, Daniel Vetter wrote:
> Thanks for testing, I've just submitted the patch for review. It
> should included in a -fixes tree soon and the get backported to
> stable kernels.
Thanks. :)
> Please let me know when this works solidly for you, so that I can
> put it into a real patch and also submit it for inclusion.
No freeze for >24h, I guess we can conclude the quirk does indeed
fix the random freeze issue as well. :)
I'm all for inclusion.
I'm also currently testing a kernel without the Intel IOMMU feature. This seems
to work, too, but also disables Intel TXT and VT-d...
At least not seeing USB and PCI(e) issues. I'll leave the box running for some
more and will afterwards disable IOMMU as a whole to see if I hit USB and PCI(e)
issues again with that combination.
Best regards,
Mihai
[resending to include all previous CC's]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4506 bytes --]
next prev parent reply other threads:[~2013-01-21 18:11 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
2013-01-20 22:49 ` Daniel Vetter
2013-01-21 18:11 ` Mihai Moldovan [this message]
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=50FD84E0.2090901@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