> Source: [sk181914](https://support.checkpoint.com/results/sk/sk181914)

# sk181914 - 9700 / 9800 appliances and 19000 / 29000 appliance series show messages "Hardware error from APEI Generic Hardware Error Source - It has been corrected by h/w and requires no further action"

| Property | Value |
|----------|-------|
| Solution ID | sk181914 |
| Date Created | 2024-01-24 |
| Last Modified | 2025-01-16 |
| Technical Level | General |
| Products | Hardware |
| Versions | Not Version-Specific |
| OS | Gaia |
| Platform | 9000, 19000, 29000 |

## Symptoms

- In rare cases on Quantum Force 9700 / 9800 appliances ([sk181698](https://support.checkpoint.com/results/sk/sk181698)) and 19000 / 29000 appliance series ([sk180520](https://support.checkpoint.com/results/sk/sk180520)), the `dmesg` command (and the `/var/log/messages ` file) may show messages about a PCIe hardware error that has been corrected.

Example:

`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: It has been corrected by h/w and requires no further action`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: event severity: corrected`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: Error 0, type: corrected`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: section_type: PCIe error`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: port_type: 4, root port`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: version: 3.0`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: command: 0x0547, status: 0x0010`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: device_id: 0000:64:03.0`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: slot: 11`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: secondary_bus: 0x66`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x347b`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: class_code: 000406`  
`
[Thu Jan 4 17:19:39 2024] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0013`  
`
[Thu Jan 4 17:19:39 2024] pcieport 0000:64:03.0: aer_status: 0x00000001, aer_mask: 0x00000000`  
`
[Thu Jan 4 17:19:39 2024] Receiver Error`  
`
[Thu Jan 4 17:19:39 2024] pcieport 0000:64:03.0: aer`

## Cause

The PCI-e interface hardware logic has several mechanisms to correct minor errors that are reported through a PCI-e Advanced Error Reporting (AER) Linux driver.

These messages indicate that a correction was made.

These hardware error corrections are automatic, with no loss of data and no impact on the performance of the PCI-e bus, where the correction was made.

## Solution

No fix is required. This behavior is by design.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
