When the incoming amplitude is marginal, data has very long run lengths, or the line rate is high (above 5 Gb/s), the Out-of-Band (OOB) circuitry might not be completely reliable. The RXBYTEISALIGNED signal uses one of the outputs of the OOB block as one of its conditions, hence this signal might occasionally de-assert even when the received data is good and there is no change in the byte boundary.
For protocols with line rates above 5 Gb/s that do not use the OOB functionality, OOB block can decoupled from the RXBYTEISALIGNED signal with some caveats.
General ES and IES:
For applications with line rates above 5 Gb/s that do not require the OOB functionality, the OOB block should be decoupled from RXBYTEISALIGNED by driving RXELECIDLEMODE [1, 0] signals to 11. In this case, excessive noise in the system might occasionally look like a valid comma character when no valid data is present and cause a false assertion of RXBYTEISALIGNED. In such cases, a system level check should be in place to check the validity of data and byte alignment.
For those protocols in this frequency range that require the OOB functionality, OOB block cannot be decoupled from the RXBYTEISALIGNED signal. In this case, the RXBYTEISALIGNED signal might not be reliable after the first assertion.
If the OOB is not being used in production silicon, it can be powered downby setting PCS_RSVD_ATTR to "0" and setting RXBUF_RESET_ON_EIDLE=FALSE.