Artful i386 with MaaS deployment will bump into kernel panic issue (4.13.0-36)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
| Artful |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
This issue was only spotted with a specific HW, node "fozzie" Dell PowerEdge R320, in our test pool. Other nodes like onibi (Dell PowerEdge R310), gonzo (Dell PowerEdge R415), pepe (Dell PowerEdge R310), onza (Dell PowerEdge R310) they don't have such issue.
Steps:
1. Deploy the system with i386 Artful, with a SRU regression-testing job on jenkins.
Result:
* The deployment task will fail, from the virtual console you will see kernel panic error message
The deployment will stuck here after the "Rebooting for dist-upgrade" task:
+ /var/lib/
. Provisioner setup
Deployed
. Fixup /etc/hosts
. Remove /etc/apt/
. Enabling Proposed
. Enabling Src
. for the pure love of rebooting
. Disabling Periodic APT Updates
. Installing python-minimal
. Installing Required Packages
. Dist Upgrade
. Rebooting for dist-upgrade
Build was aborted
Here is the MaaS deployment log: https:/
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #2 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| tags: | added: artful |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu Artful): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: kernel-da-key |
| Po-Hsu Lin (cypressyew) wrote | #4 |
| Changed in linux (Ubuntu): | |
| status: | Triaged → Invalid |
| Changed in linux (Ubuntu Artful): | |
| status: | Triaged → Invalid |
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 1755149
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.