From: Kai Krakow <hurikhan77@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: system freeze with kernel 3.2-rc7
Date: Mon, 26 Dec 2011 03:43:22 +0100 [thread overview]
Message-ID: <3j3ls8-i64.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 86sjk8gmu7.fsf@sumi.keithp.com
Keith Packard <keithp@keithp.com> schrieb:
> On Mon, 26 Dec 2011 01:43:37 +0100, Kai Krakow <hurikhan77@gmail.com>
> wrote:
>
>> I didn't have such issues with early 3.2 rcs (afair), and not with 3.1
>> kernels. After some digging through google I've found you enabled RC6 in
>> 3.2. I disabled it now, and my system runs wonderfully.
>
> Argh. Can you try building a kernel with VT-d support? I assume you
> can't turn VT-d off in the BIOS as it's UEFI?
kakra@jupiter ~ $ zgrep -i iommu /proc/config.gz
CONFIG_GART_IOMMU=y
# 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_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
So kernel vt-d support is on. Not sure what to look for in dmesg thou... I
didn't look into the BIOS settings yet, but usually if there is such an
option I turn it on because I use virtual machines.
Regards,
Kai
next prev parent reply other threads:[~2011-12-26 2:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 0:43 system freeze with kernel 3.2-rc7 Kai Krakow
2011-12-26 1:09 ` Keith Packard
2011-12-26 2:43 ` Kai Krakow [this message]
2011-12-26 3:25 ` Keith Packard
2011-12-26 10:59 ` Kai Krakow
2011-12-27 0:54 ` Keith Packard
2011-12-27 3:18 ` Kai Krakow
2011-12-27 6:03 ` Keith Packard
2011-12-27 10:30 ` tino.keitel+xorg
2011-12-27 16:27 ` Tino Keitel
2011-12-28 21:36 ` Kevin
2011-12-30 1:13 ` Kevin
2012-01-02 13:18 ` Eugeni Dodonov
2012-01-12 18:33 ` Ben Widawsky
2012-01-12 22:57 ` Kai Krakow
2012-01-13 4:04 ` Ben Widawsky
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=3j3ls8-i64.ln1@hurikhan.ath.cx \
--to=hurikhan77@gmail.com \
--cc=intel-gfx@lists.freedesktop.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.