dasharo-issues icon indicating copy to clipboard operation
dasharo-issues copied to clipboard

"DMAR: [DMA Read NO_PASID] ... fault addr " messages on start

Open serpack opened this issue 1 year ago • 1 comments

Device

novacustom NV41 Intel 12Gen

Dasharo version

1.7.2 beta

Affected component(s) or functionality

DMA

Brief summary

Sometimes DMAR reports fault addresses

How reproducible

a couple of times

How to reproduce

I don't know

Expected behavior

Not reporting fault addresses

Actual behavior

[    0.361089] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x7cd80000 [fault reason 0x01] Present bit in root entry is clear
[    0.361100] DMAR: DRHD: handling fault status reg 3
[    0.361102] DMAR: [DMA Read NO_PASID] Request device [00:02.0] fault addr 0x7cd87000 [fault reason 0x01] Present bit in root entry is clear

Screenshots

No response

Additional context

I got this error a couple of times, but I don't know why. Last time this message appeared only once while the first boot after I changed in BIOS the suspend mode from S0ix to S3. Full dmesg log. I was, however, unable to reproduce the message this way.

Solutions you've tried

No response

serpack avatar Dec 18 '23 21:12 serpack

@BeataZdunczyk @mkopec We need to take some action here

macpijan avatar Jun 28 '24 20:06 macpijan

dmesg-log-dmar.txt

Managed to reproduce the issue on 1.7.2 firmware. Options set when issue appeared only once: S3 sleep Early boot DMA protection Keep IOMMU enable when transfer control to OS Issue appeared at third boot after these settings were chosen, seems very random

SebastianCzapla avatar Dec 10 '24 14:12 SebastianCzapla

Managed to reproduce the issue once again, with Early boot DMA prot + IOMMU transfer enable, I swapped between s3 and s0ix sleep modes, and booted into live cd ubuntu 24.10 system. Every second or third swap, this issue appears in dmesg. Happened with both s3 and s0ix sleep modes active, so it seems act of changing this setting is prone to causing this issue.

dmesg-log-dmar-2.txt

SebastianCzapla avatar Dec 10 '24 14:12 SebastianCzapla

This would need testing on the more recent v1.8.0-rc1 and further analysis

filipleple avatar Jul 08 '25 11:07 filipleple

Swapping the sleep mode is not necessary to trigger this issue. I've tried repeated reboots with:

  • default settings - no reproduction for 6 reboots
  • default settings + swapping sleep mode - no reproduction for 6 reboots
  • Early DMA protection, IOMMU not checked - no reproduction for 6 reboots
  • Early DMA protection, IOMMU not checked + swapping sleep mode - no reproduction for 6 reboots
  • Early DMA protection, IOMMU checked - reproduced on second reboot

dmar_dmesg.log

philipanda avatar Oct 01 '25 06:10 philipanda