xenial 4.4.0-191-generic in -proposed has a regression
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Stefan Bader |
Bug Description
[Impact]
The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS.
I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops:
[ 0.549557] BUG: unable to handle kernel paging request at ffffffffff5f3000
[ 0.552000] IP: [<ffffffff81059
[ 0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0
[ 0.552000] Oops: 0002 [#1] SMP
[ 0.552000] Modules linked in:
[ 0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu
[ 0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[ 0.552000] task: ffff88010a0f0000 ti: ffff88010a0f8000 task.ti: ffff88010a0f8000
[ 0.552000] RIP: 0010:[<
[ 0.552000] RSP: 0000:ffff88010a
[ 0.552000] RAX: 0000000000000086 RBX: ffff88010a1df480 RCX: 0000000000000000
[ 0.552000] RDX: ffffffffff5f3000 RSI: 0000000000000001 RDI: 000000000020c000
[ 0.552000] RBP: ffff88010a0fbc50 R08: ffffffff81ebdfd0 R09: 00000000ffffffff
[ 0.552000] R10: 0000000000000011 R11: 0000000000000009 R12: ffff88010ad95400
[ 0.552000] R13: 0000000000000001 R14: 0000000000000009 R15: ffff88010a1fc480
[ 0.552000] FS: 000000000000000
[ 0.552000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.552000] CR2: ffffffffff5f3000 CR3: 0000000001e0a000 CR4: 0000000000160670
[ 0.552000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 0.552000] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 0.552000] Stack:
[ 0.552000] ffff88010ac0ba58 ffff88010a0fbc70 ffffffff810ea644 ffff88010ac0ba00
[ 0.552000] ffff88010ac0ba58 ffff88010a0fbca0 ffffffff810e6d88 ffffffff810e1009
[ 0.552000] ffff88010ac0ba00 ffff88010ac0baa0 ffff88010a1fc480 ffff88010a0fbd38
[ 0.552000] Call Trace:
[ 0.552000] [<ffffffff810ea
[ 0.552000] [<ffffffff810e6
[ 0.552000] [<ffffffff810e1
[ 0.552000] [<ffffffff810e5
[ 0.552000] [<ffffffff811fc
[ 0.552000] [<ffffffff814a3
[ 0.552000] [<ffffffff810e5
[ 0.552000] [<ffffffff814a3
[ 0.552000] [<ffffffff814bf
[ 0.552000] [<ffffffff814a3
[ 0.552000] [<ffffffff81fb2
[ 0.552000] [<ffffffff814bf
[ 0.552000] [<ffffffff814bc
[ 0.552000] [<ffffffff81fb3
[ 0.552000] [<ffffffff81fb2
[ 0.552000] [<ffffffff8141e
[ 0.552000] [<ffffffff81fb2
[ 0.552000] [<ffffffff81002
[ 0.552000] [<ffffffff810a6
[ 0.552000] [<ffffffff81f69
[ 0.552000] [<ffffffff8185d
[ 0.552000] [<ffffffff8185d
[ 0.552000] [<ffffffff8186a
[ 0.552000] [<ffffffff8185d
[ 0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f
[ 0.552000] RIP [<ffffffff81059
[ 0.996006] RSP <ffff88010a0fbc48>
[ 0.996006] CR2: ffffffffff5f3000
[ 0.996006] ---[ end trace 1d0c3bd610d641a0 ]---
[ 1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
CVE References
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → High |
description: | updated |
summary: |
- Kernel panic with AWS 4.4.0-1115-aws + xenial 4.4.0-191-generic in -proposed has a regression |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Stefan Bader (smb) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in linux (Ubuntu Xenial): | |
status: | Confirmed → In Progress |
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 1896725
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.