https://bugzilla.kernel.org/show_bug.cgi?id=202055 --- Comment #35 from Alex Williamson (alex.williamson@xxxxxxxxxx) --- (In reply to LimeTech from comment #34) > > A user is reporting a flood of syslog messages as a result of running fstrim > on one of these devices: > > 02:00.0 Non-Volatile memory controller [0108]: Silicon Motion, Inc. Device > [126f:2262] (rev 03) > Subsystem: Silicon Motion, Inc. Device [126f:2262] > Kernel driver in use: nvme > Kernel modules: nvme > > Jan 27 07:00:11 unRAID kernel: DMAR: DRHD: handling fault status reg 3 > Jan 27 07:00:11 unRAID kernel: DMAR: [DMA Read] Request device [02:00.0] > fault addr ef321000 [fault reason 06] PTE Read access is not set > Jan 27 07:00:11 unRAID kernel: DMAR: DRHD: handling fault status reg 3 > Jan 27 07:00:11 unRAID kernel: DMAR: [DMA Read] Request device [02:00.0] > fault addr f0a19000 [fault reason 06] PTE Read access is not set > Jan 27 07:00:11 unRAID kernel: DMAR: DRHD: handling fault status reg 3 > Jan 27 07:00:11 unRAID kernel: DMAR: [DMA Read] Request device [02:00.0] > fault addr efe93000 [fault reason 06] PTE Read access is not set > Jan 27 07:00:11 unRAID kernel: DMAR: DRHD: handling fault status reg 3 > Jan 27 07:00:17 unRAID kernel: dmar_fault: 77 callbacks suppressed > > Do you think your latest patch might fix this? Not likely. Gosh, how many ways can these devices be broken? This was while the device was in use by the host or within a guest? Those faults indicate the device is trying to do a DMA read from an IOVA it doesn't have mapped through the IOMMU. Based on the addresses, I'd guess this is not a VM use case. Either way, it's not the issue this bug is tracking. -- You are receiving this mail because: You are watching the assignee of the bug.
