[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a6aa431-fdde-a329-4168-44490c37f197@lwfinger.net>
Date: Thu, 21 Sep 2017 09:21:25 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: Zwindl <zwindl@...tonmail.com>
Cc: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"chaoming_li@...lsil.com.cn" <chaoming_li@...lsil.com.cn>,
"kvalo@...eaurora.org" <kvalo@...eaurora.org>,
"pkshih@...ltek.com" <pkshih@...ltek.com>,
"johannes.berg@...el.com" <johannes.berg@...el.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RTL8192EE PCIe Wireless Network Adapter crashed with linux-4.13
On 09/21/2017 06:37 AM, Zwindl wrote:
> Hi, I've reported to archlinux's bugzilla, and finally found out the flag which
> caused that issue, it's the `CONFIG_INTEL_IOMMU_DEFAULT_ON=y` flag, I think may
> this is a kernel bug, more details at https://bugs.archlinux.org/task/55665
My standard kernel has the following:
CONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_SVM is not set
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
I will do some further testing to see if turning CONFIG_INTEL_IOMMU_DEFAULT_ON
also breaks my system.
Larry
Powered by blists - more mailing lists