This issue only occur on one of AWS testing instance ""
Reproduce rate: 100% (All jenkins deployment job failed with this instance)
Steps:
1. Deploy this instance with AWS kernel (4.4.0-1052)
2. Enable -proposed, upgrade it and reboot.
Result:
* System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue.
This is a POTENTIAL REGRESSION.
This issue only occur on one of AWS testing instance ""
Reproduce rate: 100% (All jenkins deployment job failed with this instance)
Steps:
1. Deploy this instance with AWS kernel (4.4.0-1052)
2. Enable -proposed, upgrade it and reboot.
Result:
* System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue.
Output from the command: https:/ /pastebin. ubuntu. com/p/3JvWNk5CT s/ (it's a bit difficult to get full output, the instance will keep rebooting itself)