Re: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works
From: Bjorn Helgaas
Date: Tue Dec 11 2018 - 17:21:46 EST
On Tue, Dec 11, 2018 at 06:51:14PM +0000, Grumbach, Emmanuel wrote:
> > 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?
> Ok, I start to understand. So no, no public spec. I am an Intel
> employee, I used to maintain the WiFi driver (iwlwifi). I don't know
> much about PCI though. I am definitely not asking you to reverse
> engineer our device :) I can try to ask internally what could be
> going on. The reason I haven't done so so far and reached out to
> you is because I am not aware about switches that we need to toggle
> to make the device magically show up. So I thought it'd be related
> to the PCI core, which take me to the next point...
> > 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.
> Ok, thanks. So I understand from you that you didn't see any weird
> log from the PCI core saying: "I can see this device, but I can't
> enumerate it because XYZ". I tried to look for such a thing but
Right; we should be doing a config read to the device, but apparently
we don't get a response so we think it's not there. It's still
conceivable there's some hotplug or power management wrinkle that we
aren't handling correctly, but those things are used on many systems,
so it would have to be a fairly esoteric issue.
> From this point, I guess I can't do much either. I'll try to get
> info internally.