Description

This article discusses the meaning of the "I2C Accel: Fatal corruption in queue handling" error reported in the messages log by the corresponding Flexible PIC Concentrator (FPC) and details the steps for troubleshooting the error.

Note: The i2c (inter-integrated circuits) is a serial communication mechanism in which states for various components are polled at regular intervals by the chassis.

Symptoms

Users may see the ""I2C Accel: Fatal corruption in queue handling" error message scrolling continuously, indicating that there is a component for which the chassis is not able to read the i2c values and that this error needs to be addressed.

Solution

Perform the following troubleshooting steps:

  1. Check the timestamp for the following messages:
PTX5K - - - - fpc5 I2C Accel: Fatal corruption in queue handling   <<<<
PTX5K - - - - fpc5 I2C Accel: Failed to trash request id 0xa62e

  1. Scroll up and check if the following events are also logged within a few minutes of seeing the "Fatal corruption in queue handling" message for the FPC.

PTX5K - - - - fpc5 I2C Accel driver:i2c_accel_onebyte_res_table_read no match slave dev group = 0x3 device = 0x50
PTX5K - - - - fpc5 QSFP INFO: qsfp-5/1/6 I2C transaction did not complete: bytes requested: 23 (read: 0)
PTX5K - - - - fpc5 qsfp_i2c_accel_cb_cmd_notify : QSFP qsfp-5/1/6 expected req id 0xa62d for req_read_num 0 not equal to recvd req id 0xa62e
PTX5K- - - - fpc5 I2C Accel: async notification failed err 1
When you check the log, you see that the "qsfp-5/1/6 I2C" transaction has not completed in the problematic FPC.

  1. You can use the following command to collect the FPC's NVRAM and syslog data to get more details.

request pfe execute command "show syslog messages" target fpc<slot>
request pfe execute command "show nvram" target fpc<slot>
The following log entry may be seen in FPC's syslog messages:
[Nov 15 16:50:35.259 LOG: Info] QSFP INFO: qsfp-5/1/6 I2C transaction status: request ID: 35762 err_timeout=0 err_abort=0 unknown_error=1
[Nov 15 16:50:35.259 LOG: Notice] QSFP INFO: qsfp-5/1/6 I2C transaction did not complete: bytes requested: 23 (read: 0)

  1. In a Maintenance Window, re-seat the QSFP device that is reporting the error. Run the checks detailed above again.

  2. If issue persists after QSFP re-seat, open a Support case for further investigation.

Modification History

2022-07-11: Initial version