From: Robin Murphy robin.murphy@arm.com
Now that PCI inbound window restrictions are handled generically between the of_pci resource parsing and the IOMMU layer, and described in the Juno DT, we can finally enable the PCIe SMMU without the risk of DMA mappings inadvertently allocating unusable addresses.
Similarly, the relevant support for IOMMU mappings for peripheral transfers has been hooked up in the pl330 driver for ages, so we can happily enable the DMA SMMU without that breaking anything either.
Signed-off-by: Robin Murphy robin.murphy@arm.com
When we build a kernel with 64k page size and run the ltp syscalls we sporadically see a kernel crash while doing a mkfs on a connected SATA drive. This is happening every third test run on any juno-r2 device in the lab with the same kernel image (stable-rc 5.13.y, mainline and next) with gcc-11.
Here is a snippet of the boot log [1]:
+ mkfs -t ext4 /dev/disk/by-id/ata-SanDisk_SDSSDA120G_165192443611 mke2fs 1.43.8 (1-Jan-2018) Discarding device blocks: 4096/29305200 [ 55.344291] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 55.351423] ata1.00: irq_stat 0x00020002, failed to transmit command FIS [ 55.358205] ata1.00: failed command: DATA SET MANAGEMENT [ 55.363561] ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 12 dma 512 out [ 55.363561] res ec/ff:00:00:00:00/00:00:00:00:ec/00 Emask 0x12 (ATA bus error) [ 55.378955] ata1.00: status: { Busy } [ 55.382658] ata1.00: error: { ICRC UNC AMNF IDNF ABRT } [ 55.387947] ata1: hard resetting link [ 55.391653] ata1: controller in dubious state, performing PORT_RST [ 57.588447] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0) [ 57.613471] ata1.00: configured for UDMA/100 [ 57.617866] ata1.00: device reported invalid CHS sector 0 [ 57.623397] ata1: EH complete
When we revert this patch we don't see any issue.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Cheers, Anders [1] https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.13.y/build/v5.13....