Public bug reported:
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:__xen_evtchn_do_upcall+0x24/0x80
[ 2.271681] RSP: 0000:ffff8e21aa003ea0 EFLAGS: 00010046
[ 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: 0000000000000000(0000) GS:ffff8e21aa000000(0000)
knlGS:0000000000000000
[ 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_evtchn_do_upcall+0xe/0x10
[ 2.271681] do_hvm_evtchn_intr+0xe/0x20
[ 2.271681] __handle_irq_event_percpu+0x44/0x1a0
[ 2.271681] handle_irq_event_percpu+0x32/0x80
[ 2.271681] handle_irq_event+0x3b/0x60
[ 2.271681] handle_fasteoi_irq+0x75/0x130
[ 2.271681] handle_irq+0x20/0x30
[ 2.271681] do_IRQ+0x46/0xd0
[ 2.271681] common_interrupt+0x84/0x84
[ 2.271681] </IRQ>
[ 2.271681] RIP: 0010:native_safe_halt+0x6/0x10
[ 2.271681] RSP: 0000:ffffffff9ea03e28 EFLAGS: 00000246 ORIG_RAX:
ffffffffffffffdd
[ 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_text_start+0x8/0x8
[ 2.271681] default_idle+0x20/0x100
[ 2.271681] arch_cpu_idle+0x15/0x20
[ 2.271681] default_idle_call+0x23/0x30
[ 2.271681] do_idle+0x17f/0x1b0
[ 2.271681] cpu_startup_entry+0x73/0x80
[ 2.271681] rest_init+0xae/0xb0
[ 2.271681] start_kernel+0x4dc/0x4fd
[ 2.271681] x86_64_start_reservations+0x24/0x26
[ 2.271681] x86_64_start_kernel+0x74/0x77
[ 2.271681] secondary_startup_64+0xa5/0xb0
[ 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_do_upcall+0x24/0x80 RSP: ffff8e21aa003ea0
[ 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.
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Full console log"
https://bugs.launchpad.net/bugs/1771679/+attachment/5140494/+files/panic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771679
Title:
Kernel panic on boot (m1.small in cn-north-1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1771679/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
