From: Bjorn Helgaas <helgaas@kernel.org>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "bjorn@helgaas.com" <bjorn@helgaas.com>,
"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: Tue, 11 Dec 2018 07:51:21 -0600 [thread overview]
Message-ID: <20181211135121.GB99796@google.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB30133754C00@HASMSX112.ger.corp.intel.com>
On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel wrote:
> > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647
> > The Windows device manager info (requested above) would be interesting.
I *thought* I had requested it, but I can't find that. Mert, thanks
for the screenshot you attached. Would you mind also capturing the
other tabs from device manager? I'm really looking for a hex dump of
the config space, which should be at least 256 bytes. I *think*
that's available somewhere in device manager. If not, AIDA64
(https://www.aida64.com/downloads) should be able to get it.
> 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.
> PS: PCI folks don't use bugzilla's anymore? It's all over the mailing list?
Personally, I use bugzilla as a convenient place to archive artifacts
like logs, screenshots, etc. But it doesn't seem as convenient for
conversations as the mailing list, and it doesn't have the visibility
that the list does.
Bjorn
next prev parent reply other threads:[~2018-12-11 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201647-193951@https.bugzilla.kernel.org/>
2018-11-09 21:43 ` Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works Bjorn Helgaas
2018-11-28 21:19 ` Bjorn Helgaas
2018-12-02 6:57 ` Grumbach, Emmanuel
2018-12-10 22:24 ` Bjorn Helgaas
2018-12-11 6:35 ` Grumbach, Emmanuel
2018-12-11 13:51 ` Bjorn Helgaas [this message]
[not found] ` <0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com>
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=20181211135121.GB99796@google.com \
--to=helgaas@kernel.org \
--cc=Mertarg10@gmail.com \
--cc=bjorn@helgaas.com \
--cc=emmanuel.grumbach@intel.com \
--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).