On 2022-10-31T08:49:33.000+00:00, Greenman Gregory <gregory.greenman@xxxxxxxxx> wrote: > On Wed, 2022-10-26 at 20:11 +0200, Florian Schmidt wrote: > > > On 2022-10-26T18:47:20.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > On 10/26/22 10:37, Florian Schmidt wrote: > > > > > > > > > > On 2022-10-26T18:04:33.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > > > > > > > > > > > On 10/26/2022 8:56 AM, Florian Schmidt wrote: > > > > > > > > > > > > > > > > > > > > > Hi Gregory, > > > > > > > > > > > > Thank you for having a look at this. The .pnvm file was present in my test as shown by my original message: > > > > > > > > > > > > > > > > > > > > > > > > > md5sum /lib/firmware/* > > > > > > > 787381c60d907f81a3ddadc5c990a82b ./iwlwifi-ty-a0-gf-a0-71.ucode > > > > > > > d93cbdcc4bb5be69aac128e2fe291359 ./iwlwifi-ty-a0-gf-a0.pnvm > > > > > > > 33d13d236512466e71c81257209a356f ./regulatory.db > > > > > > > > > > > > I just ran the test again, ensuring I have the .pnvm you mention and the result is indeed the same. > > > > > > > > > > > > Any other ideas to solve this are welcome. > > > > > > > > > > The driver indicated it wanted to load iwlwifi-ty-a0-gf-a0-72.ucode, > > > > > which you do seem to have based upon the listing above? > > > > > -- > > > > > Florian > > > > > > > > Hi Florian, > > > > > > > > Indeed, my first log seems to load -72.ucode when my dump show a -71 file, that's strange. I must have mismatched some test, sorry for the confusion. During my tests, I've actually tried with > > > > many different firmwares (I think I've done all the compatible firmware I could find), tested both with and without the pnvm file and many kernel versions, it always seems to fail. The > > > > suspicious thing to me is that during my tests, I've confirmed several times that the same sets of wifi card, kernel and firmware work well on my intel desktop. > > > > > > > > Below are the logs from my latest test today with firmware -71 and the .pnvm from git. > > > > > > > > I'd be happy to help debug more, but I have zero visibility on the firmware so those register dumps just mean nothing to me. Let me know how I can assist with this. > > > > > > I am not familiar with ax210, but have worked quite a bit with the 7260 > > > chips (iwlwifi) and errors like those typically occurred when the PCIe > > > end-point device, that is the ax210 is not able to do PCIe inbound > > > accesses into your system's memory. Now in your case it could be that > > > the inaility to load the appropriate ucode results in ... you guessed > > > it, the ucode not being loaded which causes the timeout to happen. > > > > > > Can you tell us more about your ARM32 system here? What PCIe host > > > bridge/controller does it use, do you have an IOMMU attached to that > > > PCIe host brideg somehow? > > > > > > Thanks! > > > > > > > We're using a Xilinx FPGA Based PCIe root complex on a custom zynq-700 board. The doc of the PCIe block can be found here: > > https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/axi_pcie/v2_8/pg055-axi-bridge-pcie.pdf > > > > I'm not really familiar with IOMMU (or PCIexpress) but to my knowledge there is no support of IOMMU on our arm32 platform, at least I couldn't enable it in kernel options, it required some other > > platform flags. > > > > You can find everything lspci has to say about our device below. > > > > root@BV1-27109:~# lspci -vv > > 00:00.0 PCI bridge: Xilinx Corporation Device 7121 (prog-if 00 [Normal decode]) > > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Latency: 0, Cache Line Size: 64 bytes > > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > > I/O behind bridge: 00000000-00000fff [size=4K] > > Memory behind bridge: 00000000-000fffff [size=1M] > > Prefetchable memory behind bridge: 00000000-000fffff [size=1M] > > Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- <SERR- <PERR- > > BridgeCtl: Parity+ SERR+ NoISA- VGA- VGA16- MAbort- Reset- FastB2B- > > PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- > > Capabilities: [40] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [48] MSI: Enable- Count=1/32 Maskable+ 64bit+ > > Address: 0000000000000000 Data: 0000 > > Masking: 00000000 Pending: 00000000 > > Capabilities: [60] Express (v2) Root Port (Slot+), MSI 00 > > DevCap: MaxPayload 256 bytes, PhantFunc 1 > > ExtTag+ RBE+ > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ > > MaxPayload 128 bytes, MaxReadReq 512 bytes > > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- > > LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s, Exit Latency L0s unlimited > > ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- > > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- > > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > > LnkSta: Speed 5GT/s (ok), Width x1 (ok) > > TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt+ > > SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- > > Slot #0, PowerLimit 0.000W; Interlock- NoCompl- > > SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- > > Control: AttnInd Off, PwrInd Off, Power- Interlock- > > SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- > > Changed: MRL- PresDet- LinkState- > > RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- > > RootCap: CRSVisible- > > RootSta: PME ReqID 0000, PMEStatus- PMEPending- > > DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd- > > AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- > > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- > > AtomicOpsCtl: ReqEn- EgressBlck- > > LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- > > Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- > > Compliance De-emphasis: -6dB > > LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- > > EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- > > Capabilities: [100 v1] Device Serial Number 00-00-00-00-00-00-00-00 > > Capabilities: [128 v1] Vendor Specific Information: ID=0001 Rev=0 Len=038 <?> > > Capabilities: [200 v1] Vendor Specific Information: ID=0002 Rev=0 Len=038 <?> > > > > 01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a) > > Subsystem: Intel Corporation Device 0020 > > Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Interrupt: pin A routed to IRQ 52 > > Region 0: Memory at 80000000 (64-bit, non-prefetchable) [size=16K] > > Capabilities: [c8] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ > > Address: 0000000001374000 Data: 0000 > > Capabilities: [40] Express (v2) Endpoint, MSI 00 > > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited > > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag- PhantFunc- On Wed, 2022-10-26 at 20:11 +0200, Florian Schmidt wrote: > > On 2022-10-26T18:47:20.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > On 10/26/22 10:37, Florian Schmidt wrote: > > > > > > > > > > On 2022-10-26T18:04:33.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > > > > > > > > > > > On 10/26/2022 8:56 AM, Florian Schmidt wrote: > > > > > > > > > > > > > > > > > > > > > Hi Gregory, > > > > > > > > > > > > Thank you for having a look at this. The .pnvm file was present in my test as shown by my original message: > > > > > > > > > > > > > > > > > > > > > > > > > md5sum /lib/firmware/* > > > > > > > 787381c60d907f81a3ddadc5c990a82b ./iwlwifi-ty-a0-gf-a0-71.ucode > > > > > > > d93cbdcc4bb5be69aac128e2fe291359 ./iwlwifi-ty-a0-gf-a0.pnvm > > > > > > > 33d13d236512466e71c81257209a356f ./regulatory.db > > > > > > > > > > > > I just ran the test again, ensuring I have the .pnvm you mention and the result is indeed the same. > > > > > > > > > > > > Any other ideas to solve this are welcome. > > > > > > > > > > The driver indicated it wanted to load iwlwifi-ty-a0-gf-a0-72.ucode, > > > > > which you do seem to have based upon the listing above? > > > > > -- > > > > > Florian > > > > > > > > Hi Florian, > > > > > > > > Indeed, my first log seems to load -72.ucode when my dump show a -71 file, that's strange. I must have mismatched some test, sorry for the confusion. During my tests, I've actually tried with > > > > many different firmwares (I think I've done all the compatible firmware I could find), tested both with and without the pnvm file and many kernel versions, it always seems to fail. The > > > > suspicious thing to me is that during my tests, I've confirmed several times that the same sets of wifi card, kernel and firmware work well on my intel desktop. > > > > > > > > Below are the logs from my latest test today with firmware -71 and the .pnvm from git. > > > > > > > > I'd be happy to help debug more, but I have zero visibility on the firmware so those register dumps just mean nothing to me. Let me know how I can assist with this. > > > > > > I am not familiar with ax210, but have worked quite a bit with the 7260 > > > chips (iwlwifi) and errors like those typically occurred when the PCIe > > > end-point device, that is the ax210 is not able to do PCIe inbound > > > accesses into your system's memory. Now in your case it could be that > > > the inaility to load the appropriate ucode results in ... you guessed > > > it, the ucode not being loaded which causes the timeout to happen. > > > > > > Can you tell us more about your ARM32 system here? What PCIe host > > > bridge/controller does it use, do you have an IOMMU attached to that > > > PCIe host brideg somehow? > > > > > > Thanks! > > > > > > > We're using a Xilinx FPGA Based PCIe root complex on a custom zynq-700 board. The doc of the PCIe block can be found here: > > https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/axi_pcie/v2_8/pg055-axi-bridge-pcie.pdf > > > > I'm not really familiar with IOMMU (or PCIexpress) but to my knowledge there is no support of IOMMU on our arm32 platform, at least I couldn't enable it in kernel options, it required some other > > platform flags. > > > > You can find everything lspci has to say about our device below. > > > > root@BV1-27109:~# lspci -vv > > 00:00.0 PCI bridge: Xilinx Corporation Device 7121 (prog-if 00 [Normal decode]) > > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Latency: 0, Cache Line Size: 64 bytes > > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > > I/O behind bridge: 00000000-00000fff [size=4K] > > Memory behind bridge: 00000000-000fffff [size=1M] > > Prefetchable memory behind bridge: 00000000-000fffff [size=1M] > > Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- <SERR- <PERR- > > BridgeCtl: Parity+ SERR+ NoISA- VGA- VGA16- MAbort- Reset- FastB2B- > > PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- > > Capabilities: [40] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [48] MSI: Enable- Count=1/32 Maskable+ 64bit+ > > Address: 0000000000000000 Data: 0000 > > Masking: 00000000 Pending: 00000000 > > Capabilities: [60] Express (v2) Root Port (Slot+), MSI 00 > > DevCap: MaxPayload 256 bytes, PhantFunc 1 > > ExtTag+ RBE+ > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ > > MaxPayload 128 bytes, MaxReadReq 512 bytes > > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- > > LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s, Exit Latency L0s unlimited > > ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- > > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- > > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > > LnkSta: Speed 5GT/s (ok), Width x1 (ok) > > TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt+ > > SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- > > Slot #0, PowerLimit 0.000W; Interlock- NoCompl- > > SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- > > Control: AttnInd Off, PwrInd Off, Power- Interlock- > > SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- > > Changed: MRL- PresDet- LinkState- > > RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- > > RootCap: CRSVisible- > > RootSta: PME ReqID 0000, PMEStatus- PMEPending- > > DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd- > > AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- > > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- > > AtomicOpsCtl: ReqEn- EgressBlck- > > LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- > > Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- > > Compliance De-emphasis: -6dB > > LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- > > EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- > > Capabilities: [100 v1] Device Serial Number 00-00-00-00-00-00-00-00 > > Capabilities: [128 v1] Vendor Specific Information: ID=0001 Rev=0 Len=038 <?> > > Capabilities: [200 v1] Vendor Specific Information: ID=0002 Rev=0 Len=038 <?> > > > > 01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a) > > Subsystem: Intel Corporation Device 0020 > > Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Interrupt: pin A routed to IRQ 52 > > Region 0: Memory at 80000000 (64-bit, non-prefetchable) [size=16K] > > Capabilities: [c8] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ > > Address: 0000000001374000 Data: 0000 > > Capabilities: [40] Express (v2) Endpoint, MSI 00 > > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited > > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag- PhantFunc- On Wed, 2022-10-26 at 20:11 +0200, Florian Schmidt wrote: > > On 2022-10-26T18:47:20.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > On 10/26/22 10:37, Florian Schmidt wrote: > > > > > > > > > > On 2022-10-26T18:04:33.000+01:00, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote: > > > > > > > > > > > > > > > > > On 10/26/2022 8:56 AM, Florian Schmidt wrote: > > > > > > > > > > > > > > > > > > > > > Hi Gregory, > > > > > > > > > > > > Thank you for having a look at this. The .pnvm file was present in my test as shown by my original message: > > > > > > > > > > > > > > > > > > > > > > > > > md5sum /lib/firmware/* > > > > > > > 787381c60d907f81a3ddadc5c990a82b ./iwlwifi-ty-a0-gf-a0-71.ucode > > > > > > > d93cbdcc4bb5be69aac128e2fe291359 ./iwlwifi-ty-a0-gf-a0.pnvm > > > > > > > 33d13d236512466e71c81257209a356f ./regulatory.db > > > > > > > > > > > > I just ran the test again, ensuring I have the .pnvm you mention and the result is indeed the same. > > > > > > > > > > > > Any other ideas to solve this are welcome. > > > > > > > > > > The driver indicated it wanted to load iwlwifi-ty-a0-gf-a0-72.ucode, > > > > > which you do seem to have based upon the listing above? > > > > > -- > > > > > Florian > > > > > > > > Hi Florian, > > > > > > > > Indeed, my first log seems to load -72.ucode when my dump show a -71 file, that's strange. I must have mismatched some test, sorry for the confusion. During my tests, I've actually tried with > > > > many different firmwares (I think I've done all the compatible firmware I could find), tested both with and without the pnvm file and many kernel versions, it always seems to fail. The > > > > suspicious thing to me is that during my tests, I've confirmed several times that the same sets of wifi card, kernel and firmware work well on my intel desktop. > > > > > > > > Below are the logs from my latest test today with firmware -71 and the .pnvm from git. > > > > > > > > I'd be happy to help debug more, but I have zero visibility on the firmware so those register dumps just mean nothing to me. Let me know how I can assist with this. > > > > > > I am not familiar with ax210, but have worked quite a bit with the 7260 > > > chips (iwlwifi) and errors like those typically occurred when the PCIe > > > end-point device, that is the ax210 is not able to do PCIe inbound > > > accesses into your system's memory. Now in your case it could be that > > > the inaility to load the appropriate ucode results in ... you guessed > > > it, the ucode not being loaded which causes the timeout to happen. > > > > > > Can you tell us more about your ARM32 system here? What PCIe host > > > bridge/controller does it use, do you have an IOMMU attached to that > > > PCIe host brideg somehow? > > > > > > Thanks! > > > > > > > We're using a Xilinx FPGA Based PCIe root complex on a custom zynq-700 board. The doc of the PCIe block can be found here: > > https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/axi_pcie/v2_8/pg055-axi-bridge-pcie.pdf > > > > I'm not really familiar with IOMMU (or PCIexpress) but to my knowledge there is no support of IOMMU on our arm32 platform, at least I couldn't enable it in kernel options, it required some other > > platform flags. > > > > You can find everything lspci has to say about our device below. > > > > root@BV1-27109:~# lspci -vv > > 00:00.0 PCI bridge: Xilinx Corporation Device 7121 (prog-if 00 [Normal decode]) > > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Latency: 0, Cache Line Size: 64 bytes > > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > > I/O behind bridge: 00000000-00000fff [size=4K] > > Memory behind bridge: 00000000-000fffff [size=1M] > > Prefetchable memory behind bridge: 00000000-000fffff [size=1M] > > Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- <SERR- <PERR- > > BridgeCtl: Parity+ SERR+ NoISA- VGA- VGA16- MAbort- Reset- FastB2B- > > PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- > > Capabilities: [40] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [48] MSI: Enable- Count=1/32 Maskable+ 64bit+ > > Address: 0000000000000000 Data: 0000 > > Masking: 00000000 Pending: 00000000 > > Capabilities: [60] Express (v2) Root Port (Slot+), MSI 00 > > DevCap: MaxPayload 256 bytes, PhantFunc 1 > > ExtTag+ RBE+ > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ > > MaxPayload 128 bytes, MaxReadReq 512 bytes > > DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- > > LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s, Exit Latency L0s unlimited > > ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- > > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- > > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > > LnkSta: Speed 5GT/s (ok), Width x1 (ok) > > TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt+ > > SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- > > Slot #0, PowerLimit 0.000W; Interlock- NoCompl- > > SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- > > Control: AttnInd Off, PwrInd Off, Power- Interlock- > > SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- > > Changed: MRL- PresDet- LinkState- > > RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- > > RootCap: CRSVisible- > > RootSta: PME ReqID 0000, PMEStatus- PMEPending- > > DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd- > > AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- > > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- > > AtomicOpsCtl: ReqEn- EgressBlck- > > LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- > > Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- > > Compliance De-emphasis: -6dB > > LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- > > EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- > > Capabilities: [100 v1] Device Serial Number 00-00-00-00-00-00-00-00 > > Capabilities: [128 v1] Vendor Specific Information: ID=0001 Rev=0 Len=038 <?> > > Capabilities: [200 v1] Vendor Specific Information: ID=0002 Rev=0 Len=038 <?> > > > > 01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a) > > Subsystem: Intel Corporation Device 0020 > > Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- <TAbort- <MAbort- SERR- <PERR- INTx- > > Interrupt: pin A routed to IRQ 52 > > Region 0: Memory at 80000000 (64-bit, non-prefetchable) [size=16K] > > Capabilities: [c8] Power Management version 3 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ > > Address: 0000000001374000 Data: 0000 > > Capabilities: [40] Express (v2) Endpoint, MSI 00 > > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited > > ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W > > DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- > > RlxdOrd+ ExtTag- PhantFunc-0000:01:00.0: 0x804792E6 | umac data2 > > > > > > > > > iwlwifi 0000:01:00.0: 0x00000000 | umac data3 > > > > iwlwifi 0000:01:00.0: 0x00000047 | umac major > > > > iwlwifi 0000:01:00.0: 0x058653F6 | umac minor > > > > iwlwifi 0000:01:00.0: 0x0006488D | frame pointer > > > > iwlwifi 0000:01:00.0: 0xC0886244 | stack pointer > > > > iwlwifi 0000:01:00.0: 0x00000000 | last host cmd > > > > iwlwifi 0000:01:00.0: 0x00000400 | isr status reg > > > > iwlwifi 0000:01:00.0: IML/ROM dump: > > > > iwlwifi 0000:01:00.0: 0x00000B03 | IML/ROM error/state > > > > iwlwifi 0000:01:00.0: 0x000080F3 | IML/ROM data1 > > > > iwlwifi 0000:01:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0 > > > > iwlwifi 0000:01:00.0: Fseq Registers: > > > > iwlwifi 0000:01:00.0: 0x60000000 | FSEQ_ERROR_CODE > > > > iwlwifi 0000:01:00.0: 0x80440005 | FSEQ_TOP_INIT_VERSION > > > > iwlwifi 0000:01:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION > > > > iwlwifi 0000:01:00.0: 0x0000A652 | FSEQ_OTP_VERSION > > > > iwlwifi 0000:01:00.0: 0x00000002 | FSEQ_TOP_CONTENT_VERSION > > > > iwlwifi 0000:01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN > > > > iwlwifi 0000:01:00.0: 0x00400410 | FSEQ_CNVI_ID > > > > iwlwifi 0000:01:00.0: 0x00400410 | FSEQ_CNVR_ID > > > > iwlwifi 0000:01:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP > > > > iwlwifi 0000:01:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP > > > > iwlwifi 0000:01:00.0: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM > > > > iwlwifi 0000:01:00.0: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR > > > > iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110 > > > > iwlwifi 0000:01:00.0: retry init count 2 > > > > > > -- > > > Florian > > > > I tried exactly this combination of firmware and PNVM versions on a couple of (Intel based) machines > > that I have and the driver loads ok. It can point to some PCIe related issue indeed. I see we already > > have a related bug, that probably covers a bunch of different issues with similar behavior. Maybe you can > > try the suggestion from the last comment https://bugzilla.kernel.org/show_bug.cgi?id=212371#c34? > > If you will be able to enable IOMMU, it'd be possible to get a firmware debug dump that can shed some > > light on what's going on there. > > > > Gregory. > Hi Gregory, Regarding the bugzilla comment, I can't remove "pci=nomsi,noaer" from bootargs. They're were never there (my bootarg are "console=ttyPS0,921600 earlyprintk uio_pdrv_genirq.of_id=generic-uio"). Kernel config PCIAER is enabled. The listing above from lspci -v seems to indicate that MSI is working properly, it enabled one vector for the ax210. This all indicate I should be in the suggested configuration. Unfortunately, this hardware (Xilinx Zynq-7000) has no IOMMU support. I've also tried the same kernel/firmware/pnvm on x64 and x32 intel computers without issue. On which level of PCIe do you think the issue would be? I could get access access to a serialtek pcie analyzer if this kind of low level trace could be of any help investigating the issue. Thank you for taking time to help with this, Florian
