[Bug 1822118] Re: Kernel Panic while rebooting cloud instance

[Colin Ian King]

And for Standard_D2s_v3

IP addr	Mac Addr	Kernel	Reboots
104.42.252.54	00:0d:3a:32:df:92	5.0.0-1020-azure	500
104.42.150.26	00:0d:3a:31:1b:50	5.0.0-1020-azure	500
104.42.147.144	00:0d:3a:32:d8:2f	5.0.0-1020-azure	500
40.112.129.232	00:0d:3a:32:d5:7c	5.0.0-1020-azure	500
40.112.134.251	00:0d:3a:32:d9:2d	5.0.0-1020-azure	500
13.64.195.21	00:0d:3a:5a:7b:51	5.0.0-1020-azure	500
40.83.214.204	00:0d:3a:36:47:98	5.0.0-1020-azure	500
13.64.195.27	00:0d:3a:5a:7f:05	5.0.0-1020-azure	500
13.64.195.31	00:0d:3a:5a:78:55	5.0.0-1020-azure	500
13.64.195.69	00:0d:3a:5a:7c:72	5.0.0-1020-azure	500
104.42.51.23	00:0d:3a:37:47:0a	5.0.0-1020-azure	500
13.64.233.120	00:0d:3a:37:46:ab	5.0.0-1020-azure	500
13.64.233.216	00:0d:3a:37:49:fb	5.0.0-1020-azure	500
13.64.239.157	00:0d:3a:37:43:cf	5.0.0-1020-azure	16   [hang]
52.160.87.177	00:0d:3a:35:fc:b1	5.0.0-1020-azure	500

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions