Adding regressions list so that this can be tracked properly, including
the full report below.

Oleksandr Natalenko <oleksa...@natalenko.name> writes:

> Hello.
>
> The following upstream commits:
>
> aa6f8dcbab47 swiotlb: rework "fix info leak with DMA_FROM_DEVICE"
> ddbd89deb7d3 swiotlb: fix info leak with DMA_FROM_DEVICE
>
> break ath9k-based Wi-Fi access point for me. The AP emits beacons, but no 
> client can connect to it, either from the very beginning, or shortly after 
> start. These are the only symptoms I've noticed (i.e., no BUG/WARNING 
> messages in `dmesg` etc).
>
> The hardware is:
>
> ```
> $ dmesg | grep -i swiotlb
> [    0.426785] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
>
> BIOS Information
>     Vendor: American Megatrends Inc.
>     Version: P1.50
>     Release Date: 04/16/2018
>
> Base Board Information
>     Manufacturer: ASRock
>     Product Name: J3710-ITX
>
> 02:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
> (rev 01)
>       Subsystem: Lite-On Communications Inc Device 6621
>       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
>       Interrupt: pin A routed to IRQ 17
>       Region 0: Memory at 81400000 (64-bit, non-prefetchable) [size=512K]
>       Expansion ROM at 81480000 [disabled] [size=64K]
>       Capabilities: [40] Power Management version 2
>               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>               Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>       Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
>               Address: 0000000000000000  Data: 0000
>               Masking: 00000000  Pending: 00000000
>       Capabilities: [70] Express (v2) Endpoint, MSI 00
>               DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 
> unlimited, L1 <64us
>                       ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
> SlotPowerLimit 10.000W
>               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 2.5GT/s, Width x1, ASPM L0s L1, Exit 
> Latency L0s <4us, L1 <64us
>                       ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
>               LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
>                       ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>               LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
>                       TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
>               DevCap2: Completion Timeout: Not Supported, TimeoutDis+ 
> NROPrPrP- LTR-
>                        10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
> EETLPPrefix-
>                        EmergencyPowerReduction Not Supported, 
> EmergencyPowerReductionInit-
>                        FRS- TPHComp- ExtTPHComp-
>                        AtomicOpsCap: 32bit- 64bit- 128bitCAS-
>               DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
> OBFF Disabled,
>                        AtomicOpsCtl: ReqEn-
>               LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 
> 2Retimers- DRS-
>               LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
>                        Transmit Margin: Normal Operating Range, 
> EnterModifiedCompliance- ComplianceSOS-
>                        Compliance De-emphasis: -6dB
>               LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- 
> EqualizationPhase1-
>                        EqualizationPhase2- EqualizationPhase3- 
> LinkEqualizationRequest-
>                        Retimer- 2Retimers- CrosslinkRes: unsupported
>       Capabilities: [100 v1] Advanced Error Reporting
>               UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>               UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>               UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
>               CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
> AdvNonFatalErr-
>               CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
> AdvNonFatalErr+
>               AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- 
> ECRCChkCap- ECRCChkEn-
>                       MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
>               HeaderLog: 00000000 00000000 00000000 00000000
>       Capabilities: [140 v1] Virtual Channel
>               Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
>               Arb:    Fixed- WRR32- WRR64- WRR128-
>               Ctrl:   ArbSelect=Fixed
>               Status: InProgress-
>               VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
>                       Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
>                       Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
>                       Status: NegoPending- InProgress-
>       Capabilities: [160 v1] Device Serial Number 00-00-00-00-00-00-00-00
>       Kernel driver in use: ath9k
>       Kernel modules: ath9k
> ```
>
> These commits appeared in v5.17 and v5.16.15, and both kernels are broken for 
> me. I'm pretty confident these commits make the difference since I've built 
> both v5.17 and v5.16.15 without them, and it fixed the issue.
>
> The machine has also got another Wi-Fi card that acts as a 802.11ax AP, and 
> it is not affected:
>
> ```
> 01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI 
> Express Wireless Network Adapter (prog-if 80)
> ```
>
> So, I do understand this might be an issue with regard to SG I/O handling in 
> ath9k, hence relevant people in Cc.
>
> Please suggest on how to deal with this. Both me and Olha (in Cc) will be 
> glad to test patches if needed. In case any extra info is required, please 
> also let me know.
>
> Thanks.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

Reply via email to