https://bugzilla.kernel.org/show_bug.cgi?id=202055 --- Comment #34 from LimeTech (tomm@xxxxxxxxxxxxxxxxxxx) --- (In reply to Alex Williamson from comment #33) > Created attachment 280913 [details] > NVMe subsystem reset with ACS masking > > Dongli, I'd appreciate testing of this patch series. The differences from > the previous version are: > > 1) Use NVMe subsystem reset rather than secondary bus reset, this simplifies > some of the hotplug slot code from the previous version > 2) Mask ACS Source Validation around reset, this eliminates some of the > magic voodoo that avoided the fault on my system, but not yours > > This exploded into a several patch series to simplify the ACS masking, but > it should still apply easily. Testing by others obviously welcome as well. > Thanks 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? -- You are receiving this mail because: You are watching the assignee of the bug.
