Re: Linux error `[DMA Write NO_PASID] Request device [3c:00.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set`

[Baolu Lu <baolu.lu@linux.intel.com>]

On 2/8/26 03:10, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> On the Intel Kaby Lake laptop Dell XPS 13 9360, Linux logs the error below:
> 
>      [17959.189315] ACPI: EC: event unblocked
>      [17959.197876] DMAR: DRHD: handling fault status reg 2
>      [17959.197882] DMAR: [DMA Write NO_PASID] Request device [3c:00.0] 
> fault addr 0x0 [fault reason 0x05] PTE Write access is not set
>      [17959.198366] DMAR: DRHD: handling fault status reg 2
>      [17959.198369] DMAR: [DMA Write NO_PASID] Request device [3c:00.0] 
> fault addr 0x0 [fault reason 0x05] PTE Write access is not set
>      [17959.198923] DMAR: DRHD: handling fault status reg 2
>      [17959.201477] nvme nvme0: 4/0/0 default/read/poll queues
> 
> 3c:00.0 is the NVMe controller/device.
> 
>      $ lspci -nn -s 3c:00.0
>      3c:00.0 Non-Volatile memory controller [0108]: SK hynix PC300 NVMe 
> Solid State Drive 512GB [1c5c:1284]
> 
> This seems to happen only *sometimes* when resuming from ACPI S3.
> 
> To my knowledge, this is *not* a new problem. Please find the log 
> messages attached. (Ignore the other DMAR error for now.)

These IOMMU DMA faults are triggered when the NVMe controller attempts
DMA writes to system memory address 0x0. The IOMMU hardware blocked
these accesses because the system software has not granted the device
permission to write to this specific address. It's unlikely a bug or
problem in the iommu driver as far as I can see.

> Kind regards,
> 
> Paul

Thanks,
baolu