Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp986017imu; Tue, 11 Dec 2018 10:40:50 -0800 (PST) X-Google-Smtp-Source: AFSGD/UhBYTZrm3waaVm7W754Fy9JAYUpNNxe5cWU+/9aLg9YBG+yVV4TGiWper0joI+cTzEE+WS X-Received: by 2002:a17:902:a9c4:: with SMTP id b4mr17048951plr.298.1544553650328; Tue, 11 Dec 2018 10:40:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544553650; cv=none; d=google.com; s=arc-20160816; b=qdOaCO+IVO3gpzd13ES0CsRYr6cyRzsAyPNnbVXs5flq0zmkt5iFXxEsp4cGZwMDzJ nNUekehoUgi4VBG9e7a9oKIlyQ5pXCjsecotIedBQfXfNQgGWi6X3gxN+Y1DFomKS2dM hqFW8G5sLHkLTYHIBjuhZhEcmVE2z/YiK23uyXFgFN/MlYtZLz7Bn2z61A3pd14pQtQM zFC5MvjHOA1EPSOpSBvwKhFIK0Lrox86EfxecfuyXirffD8nKtbztqyLdyrVSSnX7cNg lkiKtWNILWyRVwzdQbr/hbm9vHkfKFepunReE3fZrcjgjsh4xheMWFT8s2sj3Sg29dkW Mrcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=9SsS/eaPOlGlYKDf4j/X94RUTyIuPyXF76rBOAsiGOU=; b=iSh9L7AofR9mojGSOVaBiKKDYPYuOHviH4TIYJG36NsuuXbFNWv2eZEs24vxwGEW+I rsWdy3buPitY7TqgS05zOC0Je8qEzHxoCt0QqxscFTBWWwqDOpgOWTXkS2aqmCCw/AZc eaoMPkngxZVFr8YLP0GbSGqk82yzCxl6HxgDOpQqamyZGLUGl3l/FHyMpRRq5JDASw9i fgg5IAHzl/frglJuTnl6se7Y/zA07DFYMvYtVUxzIolnuW+v4uRoy/BcOy5Sa7NBCsvc 1oRcduLAgnIi+iEq1iCtnpZF1klKoP7Rtw01PZ5on4jJdWduawBCR5OaVrFHCLmyG3Cm ylFw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wH1kFZgZ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l4si12724602pgr.346.2018.12.11.10.40.35; Tue, 11 Dec 2018 10:40:50 -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; dkim=pass header.i=@kernel.org header.s=default header.b=wH1kFZgZ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726556AbeLKSiH (ORCPT + 99 others); Tue, 11 Dec 2018 13:38:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:34576 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726254AbeLKSiH (ORCPT ); Tue, 11 Dec 2018 13:38:07 -0500 Received: from localhost (unknown [64.22.249.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4C7AC20855; Tue, 11 Dec 2018 18:38:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544553486; bh=yCgCdyK1fBGSGXfuw9k6xiuVD+sR2FU2KbOb7mxa/RM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wH1kFZgZ7Qo8GZnz6QpgciHdnj48jmV5VN600zDocOjWu5jo4l/YmuO3LXQKsXJ32 sBCL+SgwGku9yUu2hueU30H3xPhgi7zELB2halDgKlGNk7wCpLwYQ013lM19cKBT0A Fb/9T9MNxI2ZqppLJwI4B/3xgCMGXbGgNLs0bBWU= Date: Tue, 11 Dec 2018 12:38:05 -0600 From: Bjorn Helgaas To: "Grumbach, Emmanuel" 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 Message-ID: <20181211183805.GG99796@google.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> <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) 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 06:31:47PM +0000, Grumbach, Emmanuel wrote: > > 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... Is there a public spec? My patience for reverse engineering things that are documented somewhere that I'm not allowed to see is pretty limited. Presumably *you* should be able to see the spec, since this is an Intel device and you have an @intel.com address? From what we can tell so far, I don't *think* this is a PCI issue. If the device doesn't respond to a PCI config access, the PCI core can't really be expected to do anything about it. Bjorn