Kernel panic on boot (m1.small in cn-north-1)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Medium
|
Kamal Mostafa | ||
Bionic |
Fix Released
|
Medium
|
Kamal Mostafa | ||
linux-aws (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
We're observing the following panic on boot when trying to boot an m1.small in cn-north-1 (which is a region in AWS China):
[ 2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[ 2.271681] RIP: 0010:__
[ 2.271681] RSP: 0000:ffff8e21aa
[ 2.271681] RAX: ffffffff9dd82920 RBX: ffffffffff200000 RCX: 000000008728b34e
[ 2.271681] RDX: ffff8e21a3252800 RSI: ffff8e21a724e000 RDI: 000000000000001c
[ 2.271681] RBP: ffff8e21aa003eb8 R08: ffffffff9ea05040 R09: 0000000000000000
[ 2.271681] R10: ffff8e21aa003f28 R11: 0000000000000000 R12: 0000000000000001
[ 2.271681] R13: 0000000000000000 R14: 0000000000000022 R15: ffff8e21a3246900
[ 2.271681] FS: 000000000000000
[ 2.271681] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.271681] CR2: ffffffffff200000 CR3: 000000000b80a000 CR4: 00000000000006f0
[ 2.271681] Call Trace:
[ 2.271681] <IRQ>
[ 2.271681] xen_hvm_
[ 2.271681] do_hvm_
[ 2.271681] __handle_
[ 2.271681] handle_
[ 2.271681] handle_
[ 2.271681] handle_
[ 2.271681] handle_
[ 2.271681] do_IRQ+0x46/0xd0
[ 2.271681] common_
[ 2.271681] </IRQ>
[ 2.271681] RIP: 0010:native_
[ 2.271681] RSP: 0000:ffffffff9e
[ 2.271681] RAX: ffffffff9e12fba0 RBX: 0000000000000000 RCX: 0000000000000000
[ 2.271681] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 2.271681] RBP: ffffffff9ea03e28 R08: 0000000000000002 R09: ffffffff9ea03e18
[ 2.271681] R10: ffffffff9ea03da0 R11: 00000000eb8a1d25 R12: 0000000000000000
[ 2.271681] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 2.271681] ? __cpuidle_
[ 2.271681] default_
[ 2.271681] arch_cpu_
[ 2.271681] default_
[ 2.271681] do_idle+0x17f/0x1b0
[ 2.271681] cpu_startup_
[ 2.271681] rest_init+0xae/0xb0
[ 2.271681] start_kernel+
[ 2.271681] x86_64_
[ 2.271681] x86_64_
[ 2.271681] secondary_
[ 2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62 <c6> 03 00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05
[ 2.271681] RIP: __xen_evtchn_
[ 2.271681] CR2: ffffffffff200000
[ 2.271681] ---[ end trace 956d0f4244642614 ]---
[ 2.271681] Kernel panic - not syncing: Fatal exception in interrupt
I've attached the full console log.
Changed in linux-aws (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
status: | New → In Progress |
Changed in linux (Ubuntu Artful): | |
status: | New → In Progress |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
no longer affects: | linux-aws (Ubuntu Artful) |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Artful): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
tags: | added: id-5afaf1e185d595101750bb7b |
Changed in linux-aws (Ubuntu): | |
status: | New → Fix Released |
We've only seen this on m1.small instances, but we haven't tested exhaustively (we do know, though, that m3.large is fine).
The command used to create the instance was:
aws --profile=china --region=cn-north-1 ec2 run-instances --key-name= Odd_Bloke --image- id=ami- 8fcd13e2 --security-groups philroche-ssh-only