This same issue can be found on the following kernel on the same a1.metal instance as well:
* H-AWS-5.11.0-1023.24
* F-AWS-5.4.0-1061.64
* F-AWS-5.11.0-1023.24~20.04.1
* F-AWS-5.13.0-1008.9~20.04.2
* B-AWS-5.4.0-1061.64~18.04.1
* B-AWS-4.15.0-1118.125
And it did pass in the previous cycle.
The only explanation I can think of is there are some HW related changes in AWS cloud.
This same issue can be found on the following kernel on the same a1.metal instance as well: 11.0-1023. 24 11.0-1023. 24~20.04. 1 13.0-1008. 9~20.04. 2 4.0-1061. 64~18.04. 1 15.0-1118. 125
* H-AWS-5.
* F-AWS-5.4.0-1061.64
* F-AWS-5.
* F-AWS-5.
* B-AWS-5.
* B-AWS-4.
And it did pass in the previous cycle.
The only explanation I can think of is there are some HW related changes in AWS cloud.