Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty)
Bug #1758869 reported by
Po-Hsu Lin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
In Progress
|
High
|
Kamal Mostafa | ||
Xenial |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
This is a POTENTIAL REGRESSION.
This issue only occurs on one of the AWS testing instance "c3.large"
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:/
description: | updated |
description: | updated |
tags: | added: xenial |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
status: | Triaged → In Progress |
tags: | added: patch |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1758869
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.