ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Sometimes WLE900VX 9880 NIC does not appear in lspci.
Date: Tue, 17 Oct 2017 11:47:49 -0700	[thread overview]
Message-ID: <3eefa2db-33a1-ceb3-730b-62627239e873@candelatech.com> (raw)

Sometimes, when booting one of my apu2 systems with two of the WLE900VX
NICs in it, one of them does not show up in lspci.

Here is the pertinent (I think) bit of dmesg:

OK case (the radio in questions shows up on bus 05):

[    0.781610] pci 0000:04:00.0: [8086:157b] type 00 class 0x020000
[    0.781644] pci 0000:04:00.0: reg 0x10: [mem 0xfe700000-0xfe71ffff]
[    0.781705] pci 0000:04:00.0: reg 0x18: [io  0x3000-0x301f]
[    0.781724] pci 0000:04:00.0: reg 0x1c: [mem 0xfe720000-0xfe723fff]
[    0.781920] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
[    0.784265] pci 0000:00:02.4: PCI bridge to [bus 04]
[    0.787984] pci 0000:00:02.4:   bridge window [io  0x3000-0x3fff]
[    0.787991] pci 0000:00:02.4:   bridge window [mem 0xfe700000-0xfe7fffff]
[    0.788157] pci 0000:05:00.0: [168c:003c] type 00 class 0x028000
[    0.788192] pci 0000:05:00.0: reg 0x10: [mem 0xfe200000-0xfe3fffff 64bit]
[    0.788296] pci 0000:05:00.0: reg 0x30: [mem 0xfe400000-0xfe40ffff pref]
[    0.788428] pci 0000:05:00.0: supports D1 D2
[    0.791270] pci 0000:00:02.5: PCI bridge to [bus 05]
[    0.794970] pci 0000:00:02.5:   bridge window [mem 0xfe200000-0xfe4fffff]
[    0.795728] ACPI: PCI Interrupt Link [INTA] (IRQs *3 5 7 10 11 12 15)
....

Failure case:

Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: [8086:10d3] type 00 class 0x020000
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf6800000-0xf681ffff]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: reg 0x18: [io  0xd000-0xd01f]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: reg 0x1c: [mem 0xf6820000-0xf6823fff]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:00:1c.1: PCI bridge to [bus 04]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:00:1c.1:   bridge window [io  0xd000-0xdfff]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:00:1c.1:   bridge window [mem 0xf6800000-0xf71fffff]
Jun 09 09:23:37 localhost.localdomain kernel: pci 0000:00:1c.1:   bridge window [mem 0xf0000000-0xf09fffff 64bit pref]
Jun 09 09:23:37 localhost.localdomain kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
...


Rebooting the system usually 'fixes' the problem, but sometimes it takes several reboots.


Does this provide any clues?

Any suggested work-arounds I could try?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2017-10-17 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 18:47 Ben Greear [this message]
2017-10-18  7:52 ` Sometimes WLE900VX 9880 NIC does not appear in lspci Sebastian Gottschall
2017-10-18 14:34   ` Ben Greear

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=3eefa2db-33a1-ceb3-730b-62627239e873@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.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