From @wma_semihalf.com:
It looks that the problem with em0 is exactly the same which we faced on some other hw - the em card is detected 32 times, like it was present on every pci function on the bus which is connected to.
Details
Details
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
It depends on what the underlying issue is, I think. We really need to just fix the underlying issue and I'd commit this hack temporarily to get the ThunderX at Sentex usable in the short term.
Comment Actions
I'm fine with that workaround. Also, don't think the configuration variable is necessary. I've just tested few cards and the em is not the only one prone to multi-enumeration. Let's leave it as is, we'll only loose the ability of using pcie switches in thuderx external pci, which is in fact an extremely rare scenario.
This week I'll try to at least check the generic pci to ensure it properly configures thunderx internal bridge.
Comment Actions
It might be a bug in the PCI config space access. I.e. if you are hardcoding slot 0 in the MCFG access for some reason. Presumably if that were broken at the MCFG level you wouldn't be getting this far though. Is ARI (or something like it) enabled on the bridge by chance?
Comment Actions
Good point, John. That would also explain why sriov-capable cards are working fine and do not require this hack. I'll look at ari configuration more closely.