From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
"bjorn@helgaas.com" <bjorn@helgaas.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Mertarg10@gmail.com" <Mertarg10@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works
Date: Sun, 2 Dec 2018 06:57:35 +0000 [thread overview]
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB3013373E4A3@HASMSX112.ger.corp.intel.com> (raw)
In-Reply-To: <20181128211959.GB178809@google.com>
>
> [+cc Emmanuel, LKML]
>
> On Fri, Nov 09, 2018 at 03:43:06PM -0600, Bjorn Helgaas wrote:
> > ---------- Forwarded message ---------
> > From: <bugzilla-daemon@bugzilla.kernel.org>
> > Date: Fri, Nov 9, 2018 at 4:10 AM
> > Subject: [Bug 201647] New: Intel Wireless card 3165 does not get
> > detected but bluetooth works
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=201647
> >
> > Bug ID: 201647
> > Summary: Intel Wireless card 3165 does not get detected but
> > bluetooth works
> > Product: Drivers
> > Version: 2.5
> > Kernel Version: 4.19.1
> > Hardware: Intel
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: high
> > Priority: P1
> > Component: PCI
> > Assignee: drivers_pci@kernel-bugs.osdl.org
> > Reporter: Mertarg10@gmail.com
> > Regression: No
> >
> > This bug affects most of the devices with a Celeron N4000 and an Intel
> > wifi 3165 Ac adapter.
> >
> > When using Linux wifi is not working however, Bluetooth is working
> > fine. Also, Bluetooth part of this chip is connected via btusb and
> > the wifi part of this chip is connected via PCIe.
>
> Can you attach a screenshot of the Windows 10 device manager info for the
> wifi adapter to the bugzilla? If you can get a raw hex dump of its config
> space, that would be awesome.
>
> Also attach a copy of your kernel .config file (typically in /boot/).
>
> My only guess is that maybe the system keeps wifi completely powered
> down and uses hotplug to add it when needed. [1] mentions wifi being on
> pcibus 1 under Windows. Your lspci does show bridge 00:13.0 leading to bus
> 01, but Linux doesn't find any devices on bus 01.
>
> Hotplug could be done via either acpiphp (ACPI mediated hotplug) or pciehp
> (native PCIe hotplug). Your dmesg shows you do have acpiphp.
>
> I can't tell about pciehp (your .config will show that), but I think pciehp will
> only claim bridges where SltCap contains HotPlug+, and yours shows HotPlug-
> , so I don't think pciehp will do anything on your system.
>
> Even if the system does use hotplug, I don't know what mechanism the OS
> would use to wake up the device, since we don't know it even exists. I guess
> there could be some magic switch accessible via USB.
> But if that were the case, I'm sure Emmanuel would know about it.
>
Hm... Don't be so sure... :)
I don't think we have anything as fancy as this.
I guess you can try to dig into the BIOS settings?
I have heard of such a switch that would make the device disappear.
next prev parent reply other threads:[~2018-12-02 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201647-193951@https.bugzilla.kernel.org/>
[not found] ` <CABhMZUXc4FS-f52ZDsErEhbkm_jjEz+kn75YO5Tuvp42Qm+1xw@mail.gmail.com>
2018-11-28 21:19 ` Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works Bjorn Helgaas
2018-12-02 6:57 ` Grumbach, Emmanuel [this message]
2018-12-10 22:24 ` Bjorn Helgaas
2018-12-11 6:35 ` Grumbach, Emmanuel
2018-12-11 13:51 ` Bjorn Helgaas
2018-12-11 16:32 ` Grumbach, Emmanuel
2018-12-11 18:26 ` Bjorn Helgaas
2018-12-11 18:31 ` Grumbach, Emmanuel
2018-12-11 18:38 ` Bjorn Helgaas
2018-12-11 18:51 ` Grumbach, Emmanuel
2018-12-11 22:21 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0BA3FCBA62E2DC44AF3030971E174FB3013373E4A3@HASMSX112.ger.corp.intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=Mertarg10@gmail.com \
--cc=bjorn@helgaas.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).