Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751968AbdIUOVc (ORCPT ); Thu, 21 Sep 2017 10:21:32 -0400 Received: from mail-io0-f178.google.com ([209.85.223.178]:43945 "EHLO mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751669AbdIUOV2 (ORCPT ); Thu, 21 Sep 2017 10:21:28 -0400 X-Google-Smtp-Source: AOwi7QAnTytRPHvvrhfiJ13Psk+NUcd1QmBDXcqKGdtyiTo4UmpQinQ6MIMiFBkUpfmjc0NRk1njLg== Subject: Re: RTL8192EE PCIe Wireless Network Adapter crashed with linux-4.13 To: Zwindl Cc: "linux-wireless@vger.kernel.org" , "chaoming_li@realsil.com.cn" , "kvalo@codeaurora.org" , "pkshih@realtek.com" , "johannes.berg@intel.com" , "gregkh@linuxfoundation.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: <2WhCEttl4IJtrTB2AkJYmhbsu-kiR_5fU0A_Z7eWW05rbVE5tB86A_ZS8ek_FQFdgaZw1bfx0wFbxOa0Ydjv1T6BzBkIHtaWTbSptcpB_kg=@protonmail.com> <1eb67d2e-dfbc-a2d0-8949-d4336191c07b@lwfinger.net> <35856452-c05c-d116-f91b-0964947ec8ae@lwfinger.net> <2_UKRQjXR9_CXy_99R7fqRbs4VDG0hfFCMvvf4ll2BQV5C_zNiPTnHHNtoYstAGy_UF9X85pl4siU7fnXefmqbhlErxR6FqZQfIf0tADKNg=@protonmail.com> <5e2a695a-ea26-e0a3-d5eb-cf8135c1349e@lwfinger.net> From: Larry Finger Message-ID: <5a6aa431-fdde-a329-4168-44490c37f197@lwfinger.net> Date: Thu, 21 Sep 2017 09:21:25 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 533 Lines: 15 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