linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@gmail.com>
To: linux-pci@vger.kernel.org
Cc: Mertarg10@gmail.com
Subject: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works
Date: Fri, 9 Nov 2018 15:43:06 -0600	[thread overview]
Message-ID: <CABhMZUXc4FS-f52ZDsErEhbkm_jjEz+kn75YO5Tuvp42Qm+1xw@mail.gmail.com> (raw)
In-Reply-To: <bug-201647-193951@https.bugzilla.kernel.org/>

[Resend because I forgot to send as plain text and linux-pci rejected it.]

The report below shows only one PCI-PCI bridge (00:13.0) but no
devices below it.  I wonder if that's related to whatever's wrong with
this host bridge window:

  acpi PNP0A08:00: host bridge window [mem 0x1000000010000 window]
(ignored, not CPU addressable)
  pci 0000:00:13.0: PCI bridge to [bus 01]

Mertarg10, would you mind attaching the "sudo lspci -vv" output, too?

---------- 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
To: <bugzilla.pci@gmail.com>


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

Created attachment 279385
  --> https://bugzilla.kernel.org/attachment.cgi?id=279385&action=edit
Contains outputs of dmesg and lspci

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.

I have contacted the Linux wireless team of Intel, which suggested me to report
this bug as a PCIe bug.

--
You are receiving this mail because:
You are watching the assignee of the bug.

       reply	other threads:[~2018-11-09 21:43 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 ` Bjorn Helgaas [this message]
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
2018-12-10 22:24       ` Bjorn Helgaas
2018-12-11  6:35         ` Grumbach, Emmanuel
2018-12-11 13:51           ` Bjorn Helgaas
     [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=CABhMZUXc4FS-f52ZDsErEhbkm_jjEz+kn75YO5Tuvp42Qm+1xw@mail.gmail.com \
    --to=bjorn.helgaas@gmail.com \
    --cc=Mertarg10@gmail.com \
    --cc=bjorn@helgaas.com \
    --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).