Difference between revisions of "CentOS IOMMU related errors on system boot"

From Notes_Wiki
m
m
 
Line 1: Line 1:
<yambe:breadcrumb self="CentOS IOMMU related errors on system boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Server administration tips and tricks]] > [[CentOS IOMMU related errors on system boot]]
=CentOS IOMMU related errors on system boot=


On booting CentOS, RHEL or Fedora it is possible to receive large number of messages of
On booting CentOS, RHEL or Fedora it is possible to receive large number of messages of
Line 21: Line 20:




<yambe:breadcrumb self="CentOS IOMMU related errors on system boot">Server administration tips and tricks|Server administration tips and tricks</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Server administration tips and tricks]] > [[CentOS IOMMU related errors on system boot]]

Latest revision as of 15:53, 22 July 2022

Home > CentOS > CentOS 6.x > Server administration tips and tricks > CentOS IOMMU related errors on system boot

On booting CentOS, RHEL or Fedora it is possible to receive large number of messages of

   PTE read access is not set

This is caused by some problem with IOMMU unit. This can be avoided (not solved) by disabling IOMMU altogether. This requires editing /etc/grub/grub.conf file and removing

   intel_iommu=on
   amd_iommu=on

options.

Note that ignoring these message flooding is not a good idea. This will cause /var/log/messages flie to become very big, system to be very slow due to continuous disk write of these log messages and would make debugging things that require /var/log/messages to be read very difficult.

This was learned from http://www.gossamer-threads.com/lists/linux/kernel/1647852



Home > CentOS > CentOS 6.x > Server administration tips and tricks > CentOS IOMMU related errors on system boot