What Can I Do If an Error is Reported After I Run the dmesg Command?

Symptom

Error information is displayed after you run the dmesg command. See Figure 6-27, Figure 6-28, and Figure 6-29.

Figure 6-27 Error information 1

Figure 6-28 Error information 2

Figure 6-29 Error information 3

Cause Analysis

• ioapci: probe of XXX failed with error -22

  The Kylin official website says this error has no adverse impact on the system.

• ERST: Error Record Serializtion Table support is initialized

  The Kylin official website says this error has no adverse impact on the system. https://access.redhat.com/solutions/527433

  Root cause: An error occurs during ERST initialization. ERST is a method of recording hardware errors provided by the ACPI Platform Error Interface (APEI).

• sda3: WRITE SAME failed. Manually zeroing

  Normal print. If a device supports WRITE SAME, the kernel will use a SCSI command to optimize zeroing of data blocks. If a device does not support WRITE SAME, the following command output is displayed:

• tpm_crb: probe of MSFT0101:00 failed with error -12

  tpm crb MSFT0101:00: ioremap of the command buffer failed

• system-readahead[6143]:open(/var/tmp/initramfs.uclVZz /usr/bin/XXX) failed: Too Many levels of symbolic links

  The cause of and solution to the two errors are the same.

  Cause: The trusted platform module (TPM) 2.0 driver has a bug.

  Solution:

  Linux on a KunLun server does not support TPM 2.0. To resolve this issue, disable tpm_crb driver loading during server startup as follows:

  1. Start the operating system (OS) and open the command terminal.
  2. Run the following command:

     vim /etc/modprobe.d/nobeep.conf

  3. Add the content shown in Figure 6-30 to the nobeep.conf file.
     Figure 6-30 Adding content to the nobeep.conf file
     

  4. Save the change and exit. Then run the cat command to view the file content, as shown in Figure 6-31.
     Figure 6-31 Viewing file content
     

  5. Restart the OS and run the dmesg| grep -i error and dmesg | grep -i fail commands to check for tpm_crb driver errors, as shown in Figure 6-32 and Figure 6-33. Ensure that no error is found.

Figure 6-32 Running the dmesg| grep -i error command

Figure 6-33 Running the dmesg | grep -i fail command