[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <871sn09kdt.fsf@kamboji.qca.qualcomm.com>
Date: Thu, 21 Sep 2017 17:49:50 +0300
From: Kalle Valo <kvalo@...eaurora.org>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: Zwindl <zwindl@...tonmail.com>,
"linux-wireless\@vger.kernel.org" <linux-wireless@...r.kernel.org>,
"chaoming_li\@realsil.com.cn" <chaoming_li@...lsil.com.cn>,
"pkshih\@realtek.com" <pkshih@...ltek.com>,
"johannes.berg\@intel.com" <johannes.berg@...el.com>,
"gregkh\@linuxfoundation.org" <gregkh@...uxfoundation.org>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RTL8192EE PCIe Wireless Network Adapter crashed with linux-4.13
Larry Finger <Larry.Finger@...inger.net> writes:
> 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.
But not all systems have iommu so check from dmesg that iommu is really
enabled.
--
Kalle Valo
Powered by blists - more mailing lists