- Notes, Cautions, and Warnings
- Introduction
- AMP Event Messages
- ASR Event Messages
- BAR Event Messages
- BAT Event Messages
- BIOS Event Messages
- BOOT Event Messages
- CBL Event Messages
- CMC Event Messages
- CPU Event Messages
- CPUA Event Messages
- CTL Event Messages
- DH Event Messages
- DIAG Event Messages
- DIS Event Messages
- DKM Event Messages
- ECM Event Messages
- ENC Event Messages
- EPP Event Messages
- FAN Event Messages
- FC Event Messages
- FCD Event Messages
- FLDC Event Messages
- FSD Event Messages
- HWC Event Messages
- IOID Event Messages
- IOV Event Messages
- IPA Event Messages
- ISM Event Messages
- JCP Event Messages
- LC Event Messages
- LIC Event Messages
- LNK Event Messages
- LOG Event Messages
- MEM Event Messages
- NIC Event Messages
- OSD Event Messages
- OSE Event Messages
- PCI Event Messages
- PDR Event Messages
- PFM Event Messages
- POW Event Messages
- PR Event Messages
- PST Event Messages
- PSU Event Messages
- PSUA Event Messages
- PWR Event Messages
- RAC Event Messages
- RDU Event Messages
- RED Event Messages
- RFL Event Messages
- RFLA Event Messages
- RFM Event Messages
- RRDU Event Messages
- RSI Event Messages
- SEC Event Messages
- SEL Event Messages
- SSD Event Messages
- STOR Event Messages
- SUP Event Messages
- SWC Event Messages
- SWU Event Messages
- SYS Event Messages
- TMP Event Messages
- TMPS Event Messages
- TST Event Messages
- UEFI Event Messages
- USR Event Messages
- VDR Event Messages
- VF Event Messages
- VFL Event Messages
- VFLA Event Messages
- VLT Event Messages
- VME Event Messages
- VRM Event Messages
Event and Error Message Reference Guide for 13th Generation Dell PowerEdge ServersVersion 1.2
DIAG Event Messages
DIAG0111
- Message
- CPU arg1 : arg2 exception occurred.
- Arguments
- arg1 = Cpu Number, arg2 = Exception Type
- Detailed Description
- Recommended Response Action
- Issue is on system board. Recommend flash the latest BIOS and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0112
- Message
- CPU arg1 - Machine check exception detected.
- Arguments
- arg1 = Cpu Number
- Detailed Description
- Recommended Response Action
- Issue is on system board. Recommend flash the latest BIOS and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0114
- Message
- Cache integrity test discrepancy arg1
- Arguments
- arg1 = Error Reason
- Detailed Description
- Depends on <Error Reason>. If it is "Unable to start" it usually indicates a software problem. "Cache integrity" could signal a processor cache hardware problem. The other CPU messages could result from hardware or from overheating, if for instance, the fans are marginal or airflow is blocked.
- Recommended Response Action
- Check temperatures in System Health tab for abnormally high temperatures and make sure airflow baffles are properly installed in the system, if any. Check fan RPM in System Health tab and verify actual fans are properly installed.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0115
- Message
- CPU Stress Thermal condition. Limit arg1 C, Actual arg2 C.
- Arguments
- arg1 = Degrees, arg2 = Degrees
- Detailed Description
- Recommended Response Action
- Check fans. Check for obstructed air vents. Check for excessive amounts of dust.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0121
- Message
- Memory errors detected, but successfully resolved.
- Detailed Description
- Recommended Response Action
- MemRx is enabled and repaired all memory errors that were found. DIMM replacement is optional.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG0122
- Message
- Memory errors detected. Limit exceeded. Additional errors will not be resolved.
- Detailed Description
- Recommended Response Action
- MemRx is enabled and detected too many errors for safe resolution. Recommend DIMM replacement.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0123
- Message
- UEFI: Memory error detected. :OR: LEGACY: Memory - integrity test discrepancy.
- Detailed Description
- Recommended Response Action
- MemRX not enabled or not supported. Servers UEFI: Power down system and re-seat DIMMS. Retry test and if no error occurs it was a DIMM connection issue. Client LEGACY: Power down system and re-seat DIMMS. Retry test and if no error occurs it was a DIMM connection issue. Check for latest BIOS.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0124
- Message
- arg1 , arg2
- Arguments
- arg1 = Timestamp, arg2 = Log message
- Detailed Description
- Log message is different for the log type supported by the system. An IPMI log may refer to "SEL", other log types also exist.
- Recommended Response Action
- Depends on <Log message>.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG0125
- Message
- The event log indicates degraded or disabled ECC functionality. Memory testing cannot continue until the problems are corrected, the log cleared and the system rebooted.
- Detailed Description
- IPMI System Event Log is full for various reasons or logging has stopped because too many ECC errors have occurred.
- Recommended Response Action
- Clear the log and reboot and retest.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0141
- Message
- Hard Drive - No Hard Drive detected.
- Detailed Description
- Recommended Response Action
- Hard drives are not required on all systems so this message is usually a warning. Desktops and Servers: If the system has a hard disk, power down system and check the signal and power connections to it. Rerun the diagnostic.If no error occurs then it was a cable or connector issue.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG0142
- Message
- Hard Drive arg1 - S/N arg2 , arg3 self test unsuccessful arg4 .
- Arguments
- arg1 = Drive Location, arg2 = Serial Number, arg3 = DST Short, DST Long, arg4 = Error Reason
- Detailed Description
- Recommended Response Action
- If <Error Reason> is "terminated" then the disk controller terminated the test so a retry of the test is advisable.Otherwise the hard drive should be replaced. {In the factory, this test type may also be DEFT, in addition to DST Short and DST Long. The "terminated" case should not occur in the field, only in development due to software issues}
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0145
- Message
- Hard Drive arg1 - S/N arg2 , self test did not complete.
- Arguments
- arg1 = Drive Location, arg2 = Serial Number
- Detailed Description
- Recommended Response Action
- Desktops and Servers: Power down the system and check the signal and power connections to the hard drive. Rerun the diagnostic.If no error occurs then it was a cable or connector issue.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0146
- Message
- Hard Drive arg1 - S/N arg2 , self test log contains previous error(s).
- Arguments
- arg1 = Drive Location, arg2 = Serial Number
- Detailed Description
- Prior failure checking removed, is now obsolete.
- Recommended Response Action
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG0147
- Message
- Optical Drive arg1 - Self test: arg2 .
- Arguments
- arg1 = Nth Drive, arg2 = Error Reason
- Detailed Description
- Recommended Response Action
- This typically is a user error since these drives can be disconnected from the system. If disconnected, reconnect the optical drive to system board. Check BIOS setup to make sure the SATA port the drive is connected and has not been disabled. Rerun the diagnostic. If errors persist the optical drive is defective.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0150
- Message
- Hard Drive - No Hard Drive detected, or disk controller not supported.
- Detailed Description
- Recommended Response Action
- Hard drives on desktops should be found if connected to the chipset disk controller but PERC/SCU/SAS Adapters are not supported by legacy ePSA so if the hard drive is connected to these controllers this message is just a warning. If the system has a hard disk connected to the System Board chipset disk controller, power down the system and check the signal and power connections to it. Rerun the diagnostic.If no error occurs then it was a cable or connector issue.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG0151
- Message
- Hard Drive arg1 - S/N arg2 , incorrect status = arg3 \n arg4 .
- Arguments
- arg1 = Drive Location, arg2 = Serial Number, arg3 = 80000000000000??, arg4 = Error Reason
- Detailed Description
- Recommended Response Action
- SMART Predictive Failure indicates the hard drive has failed SMART and maybe nearing the end of its life. Other types of <Error Reason> in this category may indicate an intermittent or firmware problem, rerun the test again. Desktops, servers: Check the hard disk drive cables and connections. All systems: If error persists, make sure that hard disk drive firmware and BIOS are current. The <80000000000000??> value is an EFI error code returned by the driver.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0152
- Message
- Optical Drive arg1 - Incorrect status = arg2 arg3 .
- Arguments
- arg1 = Nth Drive, arg2 = Hex, arg3 = Error Reason
- Detailed Description
- Recommended Response Action
- Check the drive cables and connections. If error persists, make sure that drive firmware and BIOS are current. The <80000000000000??> value is an EFI error code returned by the driver.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0154
- Message
- Tape Drive arg1 - S/N arg2 , incorrect status = arg3 \n arg4 .
- Arguments
- arg1 = Drive Location, arg2 = Serial Number, arg3 = 80000000000000??, arg4 = Error Reason
- Detailed Description
- Recommended Response Action
- Check installation of the tape drive, cables and connections. If the error persists, ensure that drive firmware is current.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0155
- Message
- Hard Drive - Not installed.
- Detailed Description
- Recommended Response Action
- Power down system and check the signal and power connections to the hard drive. Rerun the diagnostic.If no error occurs then it was a cable or connector issue. This error is issued for notebooks which must have a hard disk so it is an error if not found.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0212
- Message
- System board - CMOS, Location = arg1 h, Expected = arg2 h, Found = arg3 h.
- Arguments
- arg1 = Hex, arg2 = Hex, arg3 = Hex
- Detailed Description
- Recommended Response Action
- Make sure that the system is running with the latest BIOS and rerun the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0213
- Message
- System board - CMOS battery failure detected.
- Detailed Description
- Recommended Response Action
- Replace the CMOS battery and retry the diagnostic. If the error persists, make sure the BIOS is current and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0234
- Message
- System board - HPET arg1 , incorrect time period. Expected = arg2 , Found = arg3 .
- Arguments
- arg1 = 1, arg2 = Decimal, arg3 = Decimal
- Detailed Description
- Recommended Response Action
- Make sure the BIOS is current and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0242
- Message
- System board - Interrupt controller, IRQ = arg1 : arg2 not detected.
- Arguments
- arg1 = Decimal, arg2 = IRQ Description
- Detailed Description
- Recommended Response Action
- Make sure the BIOS is current and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0243
- Message
- USB controller error.
- Detailed Description
- Recommended Response Action
- Ensure that USB ports are intact, contain no failed device and that BIOS is current. After corrective action, rerun the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0244
- Message
- USB device failed with return code 0x arg1 .
- Arguments
- arg1 = Hex
- Detailed Description
- Recommended Response Action
- Ensure that the USB device is correctly inserted or try another USB port or device. After corrective action, rerun the diagnostics. If the problem persists, ensure that BIOS is current.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
DIAG0245
- Message
- Timeout waiting for the device to respond.
- Detailed Description
- Recommended Response Action
- Ensure that the USB device is correctly inserted or try another USB port and/or to see if it is just a particular device or port. After corrective action, rerun the diagnostics. If the problem persists, ensure that BIOS is current.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0251
- Message
- Event log - The log contains failing records.
- Detailed Description
- Recommended Response Action
- This is normally a warning message indicating that the Event Log has not been checked lately. The Event Log provides various BIOS and Diagnostic events.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0313
- Message
- Touchpad - Pointing stick/touchpad not detected.
- Detailed Description
- Recommended Response Action
- Make sure that the device firmware and BIOS are current and rerun the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
DIAG0314
- Message
- Thermal: The ( arg1 ) reading ( arg2 C) exceeds the thermal limit.
- Arguments
- arg1 = Sensor Name, arg2 = Degrees
- Detailed Description
- Recommended Response Action
- Check the event log for thermal events, including defective fans and defective sensors. Inspect the system for clogged or obstructed air vents. Make sure that the BIOS is current and rerun the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0315
- Message
- Sensor: The ( arg1 ) reading arg2 C) is lower than expected.
- Arguments
- arg1 = Sensor Name, arg2 = Degrees
- Detailed Description
- Recommended Response Action
- Check the event log for thermal events, including defective fans and defective sensors. Inspect the system for clogged or obstructed air vents. Make sure that the BIOS is current and rerun the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0321
- Message
- LCD EDID - Unable to access EDID EEPROM.
- Detailed Description
- Recommended Response Action
- This could relate to the LCD connector and cables. Otherwise, flash the latest BIOS and retry diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
DIAG0324
- Message
- LCD panel - User reported LCD BIST colors were not displayed.
- Detailed Description
- Recommended Response Action
- Possible user error, make sure that the BIOS is current and retry diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG0325
- Message
- LCD panel - User provided no input for LCD BIST.
- Detailed Description
- Recommended Response Action
- Possible user error, make sure that the BIOS is current and retry diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG0415
- Message
- Cables - Check the following cable, jumper, connection, or sensor: arg1 .
- Arguments
- arg1 = Name
- Detailed Description
- Recommended Response Action
- Connect the described cable, jumper, sensor, or connection and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG0511
- Message
- Fan - The ( arg1 ) fan failed to respond correctly.
- Arguments
- arg1 = Name
- Detailed Description
- Recommended Response Action
- The fan may be faulty, check for obstructions to the fan and vents. Make sure that BIOS is current and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0512
- Message
- Fan - The ( arg1 ) fan is running faster than expected.
- Arguments
- arg1 = Name
- Detailed Description
- Recommended Response Action
- Retry the diagnostics; if the problem persists, the fan is faulty. Make sure that the BIOS is current and retry the diagnostics.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0620
- Message
- Network arg1 - arg2
- Arguments
- arg1 = Number, arg2 = Failure Message
- Detailed Description
- UEFI Driver provides a DIAGNOSTIC protocol and this protocol supplies a test that failed. Failure Message may be "Packet loopback test failed" or "Register test failed" or something else. Provided by driver not ePSA.
- Recommended Response Action
- The Network (Ethernet) device may be faulty. Check for bent pins in the Ethernet connector. Make sure that Network device firmware is current. Retry test, if still fails, replace the NIC/NDC/LOM Network device. This may be on the motherboard, or an adapter, or a daughter card, depending on the system.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG0621
- Message
- Network arg1 - Driver version arg2 outdated. Version arg3 or newer required for " arg4 "
- Arguments
- arg1 = Number, arg2 = Hex, arg3 = Hex, arg4 = EFI Driver Name
- Detailed Description
- Test only warns because UEFI Network Driver is old and has known false failures.
- Recommended Response Action
- Update Network firmware.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG8002
- Message
- No BIOS support for SMI interface function(ah) arg1 h.;Sensor arg2 exceeded thermal zone arg3 . Peak zone was arg4 .
- Arguments
- arg1 = Hex Function, arg2 = Name, arg3 = Decimal, arg4 = Decimal
- Detailed Description
- Recommended Response Action
- Should not occur
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8005
- Message
- LCD BIST not supported. or Fan - Fan speed failure. Expected at least arg1 , observed arg2 .
- Arguments
- arg1 = RPM, arg2 = RPM
- Detailed Description
- Recommended Response Action
- If LCD BIST error: The LCD BIST may not exist on all systems. Make sure that the BIOS is current and rerun the diagnostics. If Fan speed error: Insure fans are not dirty or obstructed and check for a loose connection.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8007
- Message
- Log contains Fan events;Timer expected arg1 observed arg2 .
- Arguments
- arg1 = Decimal, arg2 = Decimal
- Detailed Description
- Recommended Response Action
- For "Log contains Fan events", the events are placed in the log by other sources and ePSA is merely reporting them.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8008
- Message
- Out of memory! fMalloc() Failed! :OR: Unable to allocate memory for object data. :OR: Unable to arg1 testable memory. :OR: Unable to start application processor(s) :OR: Unable to stop all APs. The system may be unstable and should be rebooted.
- Arguments
- arg1 = Name
- Detailed Description
- Recommended Response Action
- Software error, should not normally occur in field.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8009
- Message
- Cannot find memory to free! fFree() Failed with pointer arg1
- Arguments
- arg1 = Hex
- Detailed Description
- Recommended Response Action
- Software error, should not normally occur in field.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG8012
- Message
- Invalid parameter passed to the device.; Unknown test ( arg1 ) selected.
- Arguments
- arg1 = Decimal
- Detailed Description
- Recommended Response Action
- Software error, should not normally occur in field.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG8014
- Message
- ADDF module ( arg1 ) device ( arg2 ) failed with error code arg3 , number arg4 . No EPSA beep code mapped.
- Arguments
- arg1 = Name, arg2 = Name, arg3 = Hex, arg4 = hex
- Detailed Description
- Recommended Response Action
- Software error, should not normally occur in field.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
DIAG8154
- Message
- Tape Drive arg1 - S/N arg2 , ULTRIUM arg3 media found but drive requires ULTRIUM arg4 for arg5 .
- Arguments
- arg1 = Drive Location, arg2 = Serial Number, arg3 = Generation, arg4 = Generation, arg5 = writes
- Detailed Description
- Each generation of ULTRIUM Tape drives usually supports the previous generation but not newer generation tape media.
- Recommended Response Action
- Install the correct tape media.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8155
- Message
- Tape Drive arg1 - S/N arg2 , data read does not match data written.
- Arguments
- arg1 = Drive Location, arg2 = Serial Number
- Detailed Description
- Data written the the tape read back differently, not as expected.
- Recommended Response Action
- Use a different tape media.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG8156
- Message
- Tape Drive arg1 - S/N arg2 , no media, cannot test drive.
- Arguments
- arg1 = Drive Location, arg2 = Serial Number
- Detailed Description
- Testing requires scratch tape media.
- Recommended Response Action
- Install tape media or skip test.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8157
- Message
- arg1 Drive arg2 - S/N arg3 , drive is not a supported drive.
- Arguments
- arg1 = Tape|Disk, arg2 = Drive Location, arg3 = Serial Number
- Detailed Description
- If <Tape> then only Dell tape drives are tested and supported. If <Disk> then disk drive may not be a Dell drive.
- Recommended Response Action
- Customer appears to have added a non-Dell Tape drive to his system.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
DIAG8158
- Message
- arg1 Drive arg2 - S/N arg3 , incorrect status = arg4 \n arg5 .
- Arguments
- arg1 = Backplane|Expander|RD1000, arg2 = Drive Location, arg3 = Serial Number, arg4 = 80000000000000??, arg5 = Error Reason
- Detailed Description
- A device failed a command and testing cannot complete.
- Recommended Response Action
- Retry test. If failure persists and BIOS is up to date, a hardware problem is indicated.
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG8160
- Message
- PERC Battery arg1 - incorrect status = arg2 \n arg3 .
- Arguments
- arg1 = PERC Controller Location, arg2 = 80000000000000??, arg3 = Error Reason
- Detailed Description
- Recommended Response Action
- "If <Error Reason> is (Battery missing or disconnected) then check the battery cable to the PERC controller. If <Error Reason> is (Replace battery pack) then replace battery pack. If <Error Reason> is (Remaining capacity low) then battery pack may need to be replaced soon."
- Category
- Storage (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG8170
- Message
- PCIe - Training error PciTag- arg1 VendorID- arg2 DeviceID- arg3 SVid- arg4 SDid- arg5 Bus arg6 : Link Degraded, maxLinkWidth = x arg7 , negotiatedLinkWidth = x arg8 , Slot arg9
- Arguments
- arg1 = tag, arg2 = hex, arg3 = hex, arg4 = hex, arg5 = hex, arg6 = decimal, arg7 = decimal, arg8 = decimal, arg9 = slot
- Detailed Description
- A PCI device is functioning at a lower performance that it should be. If the device is in a physical PCI slot then ", Slot <decimal>" will be appended to the message
- Recommended Response Action
- Reseat the PCI-Express adapter described and retest.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 2 (Warning)
DIAG8171
- Message
- PCIe - PCI device in physical Slot arg1 , PciTag arg2 , is present but not responding
- Arguments
- arg1 = decimal, arg2 = hex
- Detailed Description
- A PCI adapter was detected as present but it does not respond to PCI Configuration Space access, so is very sick or not inserted sungly in the PCI physical slot connector
- Recommended Response Action
- Reseat or replace PCI adapter in the PCI slot indicated
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 1 (Critical)
DIAG8611
- Message
- User reported not hearing speaker tone
- Detailed Description
- Recommended Response Action
- If the beep was not heard, verify the internal speakers are connected properly. On some systems, internal speakers are a purchased option. For a given system, if the speaker is optional, it might not exist on that system. If audio is not heard, make sure to unplug anything plugged into an external headphone jack and rerun the test. External HP jacks can mute the internal speakers at the hardware level.
- Category
- System Health (DIAG = Diagnostic)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\