| 2019-03-28 15:06:38 |
Sean Feole |
bug |
|
|
added bug |
| 2019-03-28 15:07:10 |
Sean Feole |
linux-azure (Ubuntu): assignee |
|
Colin Ian King (colin-king) |
|
| 2019-03-28 15:21:54 |
Colin Ian King |
linux-azure (Ubuntu): importance |
Undecided |
High |
|
| 2019-03-28 15:21:57 |
Colin Ian King |
linux-azure (Ubuntu): status |
New |
In Progress |
|
| 2019-03-28 17:42:04 |
Brad Figg |
bug |
|
|
added subscriber Joshua R. Poulson |
| 2019-03-28 17:42:18 |
Brad Figg |
bug |
|
|
added subscriber Joseph Salisbury |
| 2019-03-28 19:21:14 |
Joseph Salisbury |
tags |
|
kernel-hyper-v |
|
| 2019-03-29 02:25:40 |
Sean Feole |
attachment added |
|
rebootme.py https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+attachment/5250368/+files/rebootme.py |
|
| 2019-03-29 15:44:56 |
Patricia Gaughen |
bug task added |
|
systemd (Ubuntu) |
|
| 2019-03-30 12:25:36 |
Francis Ginther |
tags |
kernel-hyper-v |
id-5c9e3d984ba1ad4df84a6b1c kernel-hyper-v |
|
| 2019-09-18 14:09:08 |
Colin Ian King |
linux-azure (Ubuntu): status |
In Progress |
Incomplete |
|
| 2020-01-06 20:45:07 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2020-01-06 20:54:55 |
Finom Davoi |
attachment added |
|
ubuntu16-vm.d2bed824-7c13-4ee8-a278-d550884c35c9.serialconsole.txt https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+attachment/5317984/+files/ubuntu16-vm.d2bed824-7c13-4ee8-a278-d550884c35c9.serialconsole.txt |
|
| 2020-02-11 09:29:38 |
Colin Ian King |
systemd (Ubuntu): importance |
Undecided |
High |
|
| 2020-02-11 09:31:02 |
Colin Ian King |
systemd (Ubuntu): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2020-02-11 09:31:56 |
Colin Ian King |
description |
Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely.
In My case, it was a kernel panic. See specifics below..
Series: Disco
Instance Size: Basic_A3
Region: (Default) US-WEST-2
Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50.
After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console.
[ OK ] Reached target Reboot.
/shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 89.498980]
[ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu
[ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017
[ 89.508026] Call Trace:
[ 89.508026] dump_stack+0x63/0x8a
[ 89.508026] panic+0xe7/0x247
[ 89.508026] do_exit.cold.23+0x26/0x75
[ 89.508026] do_group_exit+0x43/0xb0
[ 89.508026] __x64_sys_exit_group+0x18/0x20
[ 89.508026] do_syscall_64+0x5a/0x110
[ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 89.508026] RIP: 0033:0x7f7bf0154d86
[ 89.508026] Code: Bad RIP value.
[ 89.508026] RSP: 002b:00007ffd6be693b8 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
[ 89.508026] RAX: ffffffffffffffda RBX: 00007f7bf015e420 RCX: 00007f7bf0154d86
[ 89.508026] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f
[ 89.508026] RBP: 00007f7bef9449c0 R08: 00000000000000e7 R09: 00000000ffffffff
[ 89.508026] R10: 00007ffd6be6974c R11: 0000000000000206 R12: 0000000000000018
[ 89.508026] R13: 00007f7bef944ac8 R14: 00007f7bef944a00 R15: 0000000000000000
[ 89.508026] Kernel Offset: 0x16000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 89.508026] ]---
this only occurred once in my testing. |
Very occasionally systemd panics on reboots of an azure instance. A workaround to this issue is described in comment #20
------------
Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely.
In My case, it was a kernel panic. See specifics below..
Series: Disco
Instance Size: Basic_A3
Region: (Default) US-WEST-2
Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50.
After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console.
[ OK ] Reached target Reboot.
/shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 89.498980]
[ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu
[ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017
[ 89.508026] Call Trace:
[ 89.508026] dump_stack+0x63/0x8a
[ 89.508026] panic+0xe7/0x247
[ 89.508026] do_exit.cold.23+0x26/0x75
[ 89.508026] do_group_exit+0x43/0xb0
[ 89.508026] __x64_sys_exit_group+0x18/0x20
[ 89.508026] do_syscall_64+0x5a/0x110
[ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 89.508026] RIP: 0033:0x7f7bf0154d86
[ 89.508026] Code: Bad RIP value.
[ 89.508026] RSP: 002b:00007ffd6be693b8 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
[ 89.508026] RAX: ffffffffffffffda RBX: 00007f7bf015e420 RCX: 00007f7bf0154d86
[ 89.508026] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f
[ 89.508026] RBP: 00007f7bef9449c0 R08: 00000000000000e7 R09: 00000000ffffffff
[ 89.508026] R10: 00007ffd6be6974c R11: 0000000000000206 R12: 0000000000000018
[ 89.508026] R13: 00007f7bef944ac8 R14: 00007f7bef944a00 R15: 0000000000000000
[ 89.508026] Kernel Offset: 0x16000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 89.508026] ]---
this only occurred once in my testing. |
|
| 2021-06-30 22:25:03 |
Dan Streetman |
systemd (Ubuntu): status |
Confirmed |
Invalid |
|
| 2021-10-08 15:09:53 |
Colin Ian King |
linux-azure (Ubuntu): assignee |
Colin Ian King (colin-king) |
|
|
| 2021-12-08 04:17:25 |
Launchpad Janitor |
linux-azure (Ubuntu): status |
Incomplete |
Expired |
|
| 2024-03-14 13:20:45 |
Bernard Gaum |
bug |
|
|
added subscriber Bernard Gaum |
