Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp980583imu; Tue, 11 Dec 2018 10:34:34 -0800 (PST) X-Google-Smtp-Source: AFSGD/UJkBNP4X75zREoQd8TH0bfWNK39lSXL/NpMGw8/iWpztkPOv0p58iybD6mOXpm/y4X5GHG X-Received: by 2002:a63:ff16:: with SMTP id k22mr15783924pgi.244.1544553274822; Tue, 11 Dec 2018 10:34:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544553274; cv=none; d=google.com; s=arc-20160816; b=U4lipk5W029t+eso9eO024BggxO3BU0pQPKp+Uu1kAXNq/NYn56ByM3j1gxB4YRNF8 dOJsL6cEMzN0TT6OPe0vuiHCwwWJCJqkInqgXjKGZRiyC5l3Rn/o0fOaKcHoFm75Y/uL WrhKLIieTEyxe3e+aBA1xGf1QjfTpqi0rme01uQ7EkkGY4ZMBL3hKV3sV9N2j8l1OnZ3 PogabN93g4kNrlolutCTwiPGuLAjQ/dFqIXeCQnipxj4pbHHrYz1nv6ycegSuMTEC28E 28qw+RCe1Xgo/8Mz5J03cO0dVP/loFxTdrA+0205wIsABwqXjR3B7xbpEiDUA03wIpvV Ww5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :dlp-reaction:dlp-version:dlp-product:content-language :accept-language:in-reply-to:references:message-id:date:thread-index :thread-topic:subject:cc:to:from; bh=1dD/XcOk0qJQv5BQ2J7gAyJaSWcY2lud6Sz6fI94JGE=; b=LxJXextRW7wLtXSZ+o7pq7NBOfSnTomxn7Lqc6/qD3edzydLtbxYIoxTiM5PMAVjWN T/rxmuuuhOAmLQRT6Ilm+fdrTahuL0gfOkSQ2U8aum64KXSn/oSqJdcUPH4NP071+eHp brY39IJM4+XDfAzWPLoahOl27pbkMe/Z8HPk8Fs4/2IYht8kvPj3pWcO3dZ6v7lQUYK9 wwTJBG/u+rYugK5xAbaYH99iCIJQBBbC0Nc7P0Vk7AB/VZfE1dPg1vqGS8X8mOLTKJ31 U+m674ChJYP03q3KdY2Iwd5rKDFAEvC8SshN89DljQoZE7IitAN2HuXyNoCVsXmgZBvd lelQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h3si12928787pgl.468.2018.12.11.10.34.20; Tue, 11 Dec 2018 10:34:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727119AbeLKSbw convert rfc822-to-8bit (ORCPT + 99 others); Tue, 11 Dec 2018 13:31:52 -0500 Received: from mga02.intel.com ([134.134.136.20]:6774 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726700AbeLKSbw (ORCPT ); Tue, 11 Dec 2018 13:31:52 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2018 10:31:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,343,1539673200"; d="scan'208";a="301301276" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga006.fm.intel.com with ESMTP; 11 Dec 2018 10:31:51 -0800 Received: from fmsmsx153.amr.corp.intel.com (10.18.125.6) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 11 Dec 2018 10:31:51 -0800 Received: from hasmsx111.ger.corp.intel.com (10.184.198.39) by FMSMSX153.amr.corp.intel.com (10.18.125.6) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 11 Dec 2018 10:31:50 -0800 Received: from hasmsx112.ger.corp.intel.com ([169.254.11.88]) by HASMSX111.ger.corp.intel.com ([169.254.5.58]) with mapi id 14.03.0415.000; Tue, 11 Dec 2018 20:31:48 +0200 From: "Grumbach, Emmanuel" To: Bjorn Helgaas CC: "bjorn@helgaas.com" , "linux-pci@vger.kernel.org" , "Mertarg10@gmail.com" , "linux-kernel@vger.kernel.org" , Fran RR Subject: RE: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works Thread-Topic: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works Thread-Index: AQHUh2ApCc7lmNGfg0mZ5cTxRsuvBaVrCVdwgA10uACAAKnQcIAAWQuAgABN2ZD///8HAIAAIouA Date: Tue, 11 Dec 2018 18:31:47 +0000 Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com> References: <20181128211959.GB178809@google.com> <0BA3FCBA62E2DC44AF3030971E174FB3013373E4A3@HASMSX112.ger.corp.intel.com> <20181210222452.GC85090@google.com> <0BA3FCBA62E2DC44AF3030971E174FB30133754C00@HASMSX112.ger.corp.intel.com> <20181211135121.GB99796@google.com> <0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com> <20181211182630.GF99796@google.com> In-Reply-To: <20181211182630.GF99796@google.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2ZlMDg5NzYtNDQzMS00OGI2LTkwYmEtYTdhYTViOTVmMGQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTkk0ZjN4T2hQZzlYaEhOc1JXN2NRb2d2S2RWbTBIOE16Q1hhWnRBU1cyMW5GYXYzY0dcL2dUZHEwMWRUYmFkK1QifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.251.82.25] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > On Tue, Dec 11, 2018 at 04:32:25PM +0000, Grumbach, Emmanuel wrote: > > > On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel wrote: > > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647 > > > > > > > FWIW: I saw another problem like this with a 9650 device. > > > > > > Do you have a pointer to any info about this 9650 issue? Maybe that > > > would have a clue. > > > > I added him here so that you can ask whatever you like :) The story is > > the same. I am attaching a picture I got from the reporter. > > I can confirm that this device ID / subdevice ID is supported by the linux > driver. > > Was there a resolution, i.e., if somebody figured out how to make the > 9650 wifi work, maybe a similar solution would work for the 3165? Unfortunately not, I am stuck there at the exact same point. No Wifi device shows up in lspci...