> Reading or writing to PCI devices in D3cold is a problem on every > system and we should avoid it in generic ways. I don't know what's > special about these MacBooks.
I did not know about, i will try to remove the ignore_access code, and will tell you the results, i added it as a failsafe > > +++ b/drivers/pci/pcie/portdrv.c > > @@ -688,7 +688,7 @@ static int pcie_portdrv_probe(struct pci_dev *dev, > > int type = pci_pcie_type(dev); > > int status; > > > > - if (!pci_is_pcie(dev) || > > + if (!pci_is_pcie(dev) || dev->no_pcie_port || > > ((type != PCI_EXP_TYPE_ROOT_PORT) && > > (type != PCI_EXP_TYPE_UPSTREAM) && > > (type != PCI_EXP_TYPE_DOWNSTREAM) && > > Nor does this. I don't know what the purpose of this is. This is however nessacary, without this The CPU just catters, so something used the PCIE address space or the config space of the bridges, unfortunately dmesg dosent show anything or journalctl.
