Comment # 13 on bug 1187701 from Mathew McBride

(In reply to Jiri Slaby from comment #12)
> (In reply to Jiri Slaby from comment #11)
> > (In reply to Mathew McBride from comment #4)
> > > I also have an ath10k_pci wireless card (QCA6174) in this system and
> > > 'modprobe ath10k_pci' simply stalls with no error messages. So a general
> > > PCIe issue is quite likely here.
> > 
> > The above crash explains this.
> 
> Anyway, if you blacklist ath10k_pci, does the system boot or the nvme issue
> remains?

The nvme issue remains, it occurs in systems where the only the NVMe device is
the only PCIe device.

It turns out I did not have kdump started for the other two cases, so I now
have crashdumps for:

a) Crash on ahci module load

https://user.fm/files/v2-b292f37d90102413f7eb4af2b47dc3be/bug-1187701-ahci-crash.tar

b) Crash on ath10k_pci module load

https://user.fm/files/v2-8a9b2e2fe9203736ec0f9bea779294c3/bug-1187701-ath10k_pci-crash.tar

In both of the above, the relevant PCIe device is the only card installed.

Interesting to note that both the above occur through PCI probing:
[  124.230047] Call trace:
[  124.232492]  ahci_enable_ahci+0x20/0x90 [libahci]
[  124.237196]  ahci_save_initial_config+0x34/0x390 [libahci]
[  124.242689]  ahci_init_one+0x360/0xd7c [ahci]
[  124.247044]  local_pci_probe+0x44/0x98
[  124.250790]  pci_device_probe+0x130/0x1c0

[  167.941476] Call trace:
[  167.943923]  ath10k_pci_wake_wait+0x44/0xf0 [ath10k_pci]
[  167.949236]  ath10k_pci_wake.part.6+0xf4/0x138 [ath10k_pci]
[  167.954810]  ath10k_bus_pci_write32+0x88/0xd8 [ath10k_pci]
[  167.960322]  ath10k_ce_deinit_pipe+0x5c/0x218 [ath10k_core]
[  167.965896]  ath10k_pci_probe+0x44c/0x828 [ath10k_pci]
[  167.971034]  local_pci_probe+0x44/0x98
[  167.974779]  pci_device_probe+0x130/0x1c0
[  167.978786]  really_probe+0xdc/0x448
[  167.982357]  driver_probe_device+0x12c/0x148
[  167.986623]  device_driver_attach+0x74/0x98
[  167.990801]  __driver_attach+0x6c/0x168