Hi, On Fri, Nov 8, 2019 at 5:09 PM Peter Geis <pgwipeout@xxxxxxxxx> wrote: > > Good Evening, > > I'm not sure, but I believe the pcie address space built into the > rk3399 is not large enough to accommodate the pcie addresses the card > requires. > I've been trying to figure out if it's possible to use system ram > instead, but so far I haven't been successful. > Also, the ram layout for the rk3399 is odd considering the TRM, if > anyone has any insights in to that, I'd be grateful. > > On Mon, Nov 4, 2019 at 1:55 PM Peter Geis <pgwipeout@xxxxxxxxx> wrote: > > > > Good Morning, > > > > I'm attempting to debug an issue with the rockpro64 pcie port. > > It would appear that the port does not like various cards, including > > cards of the same make that randomly work or do not work, such as > > Intel i340 based NICs. > > I'm experiencing it with a GTX645 gpu. > > > > This seems to be a long running issue, referenced both at [0], and [1]. > > There was an attempt to rectify it, by adding a delay between training > > and probing [2], but that doesn't seem to be the issue here. > > It appears that when we probe further into the card, such as devfn > > > 1, we trigger the bug. > > I've added a print statement that prints the devfn, address, and size > > information, which you can see below. > > > > I've attempted setting the available number of lanes to 1 as well, to > > no difference. > > > > If anyone could point me in the right direction as to where to > > continue debugging, I'd greatly appreciate it. I don't have tons of knowledge here, but your thread happened to fly by my Inbox and it reminded me of issues we faced during the bringup of rk3399-gru-kevin where our WiFi driver would kill the whole system in random / hard to debug ways. If I remember, the problem was that the rk3399 PCIe behaved very badly when you try to access the bus is in certain power save modes. I think that traditional x86-based controllers just return 0xff in the same state, but rk3399 gives some sorts of asynchronous bus errors. IIRC our problem was fixed with: https://crrev.com/c/402092 - FROMLIST: mwifiex: fix corner case power save issue ...that's about all the knowledge I have around this area, but possibly it could point you in the right direction? -Doug