2 DMAR messages appear after Grub and before Plymouth-like status messages

[bullgard4]

Since ~ 2020-02-01 2 DMAR messages appear every time when booting:

DMAR: DRHD: handling default status reg 3
DMAR: [DMA Write] Request device  [00:02.0] PASID ffffffff fault addr ffffed000 [fault reason 05] PTE Write access  is not set

I can find these 2 messages also using '~$ journalctl -xb'.

I believe I have not done anything that provoked these 2 messages except dist-upgrade.
Do I need to care about them?
I do not use explicitely virtualization let alone virtualization with DMAR.

[der_bud]

The first 4 search results I get for this all recommend setting 'intel_iommu=off' as kernel parameter. But that was told you in IRC already yesterday - did it not help?

[bullgard4]

Inserting your suggested kernel parameter makes the two messages disappear.

I'd expected this result.
But my question was if I need to care if the two messages appear (in case of not adding an additional kernel parameter).

[hendrikL]

Please provide us the output of

Code Select Expand


:~$ inxi -v1 -a


[bullgard4]

~$ inxi -v1 -a
System:    Host: siductionbox Kernel: 5.4.17-towo.1-siduction-amd64 x86-64 bits:64                   
                    parameters: BOOT_IMAGE=/boot/vmlinuz-5.4.17-towo.1-siduction-amd64 root =UUID=49afe06...d7 ro quiet                       Desktop: Xfce 4.12.2 Distro: siduction 13.2.1 December - xfce - (201401272206)CPU:          Dual Core: Intel Core i5 M 520 type: MT MCP speed: 1463 MHz min/max: 1199/2400 MHzGraphics:Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel                     
                     Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: fbdev, vesa resolution: 1280x800~60Hz                            OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 19.3.3Drives:       Local Storage: total: 465.76 GiB used: 91.13 GiB (19,6%)Info:           Processes: 214 Uptime: 2m Memory: 3.71 GiBused: 770.6 MiB (20.3%) Shell: bash inxi: 3.0.37