It resolved the bug. Tested successfully on Wily with 4.2.0-10-generic #12~lp1440103 test kernel.
These are the traces in dmesg in the crash logs: [ 187.204774] CPU: 3 PID: 946 Comm: bash Not tainted 4.2.0-10-generic #12~lp1440103 [ 187.204774] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 [ 187.204774] task: ffff8800f077cb00 ti: ffff8800f23ac000 task.ti: ffff8800f23ac000 [ 187.204774] RIP: 0010:[<ffffffff814a1786>] [ 187.204774] [<ffffffff814a1786>] sysrq_handle_crash+0x16/0x20 [ 187.204774] RSP: 0018:ffff8800f23afe28 EFLAGS: 00010296 [ 187.204774] RAX: 000000000000000f RBX: 0000000000000063 RCX: 000000000000000f [ 187.204774] RDX: ffff8801026d12f8 RSI: ffff8801026cea58 RDI: 0000000000000063 [ 187.204774] RBP: ffff8800f23afe28 R08: 00000000000000c2 R09: 0000000000000002 [ 187.204774] R10: 0000000000000260 R11: 0000000000000002 R12: 0000000000000004 [ 187.204774] R13: 0000000000000000 R14: ffffffff81cc2560 R15: 0000000000000000 [ 187.204774] FS: 00007f385dfc0700(0000) GS:ffff8801026c0000(0000) knlGS:0000000000000000 [ 187.204774] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 187.204774] CR2: 0000000000000000 CR3: 00000000f1111000 CR4: 00000000000006e0 [ 187.204774] Stack: [ 187.204774] ffff8800f23afe58 ffffffff814a1f86 0000000000000002 fffffffffffffffb [ 187.204774] 0000000000980408 0000000000000002 ffff8800f23afe78 ffffffff814a23e3 [ 187.204774] 0000000000000002 ffff8800edeec180 ffff8800f23afe98 ffffffff81252278 [ 187.204774] Call Trace: [ 187.204774] [<ffffffff814a1f86>] __handle_sysrq+0xf6/0x150 [ 187.204774] [<ffffffff814a23e3>] write_sysrq_trigger+0x33/0x40 [ 187.204774] [<ffffffff81252278>] proc_reg_write+0x48/0x70 [ 187.204774] [<ffffffff811eb598>] __vfs_write+0x18/0x40 [ 187.204774] [<ffffffff811ebbd9>] vfs_write+0xa9/0x190 [ 187.204774] [<ffffffff811ec946>] SyS_write+0x46/0xa0 [ 187.204774] [<ffffffff81208f0f>] ? __close_fd+0x8f/0xb0 [ 187.204774] [<ffffffff817b8132>] entry_SYSCALL_64_fastpath+0x16/0x75 [ 187.204774] Code: 45 39 7d 34 75 e5 4c 89 ef e8 17 f8 ff ff eb db 0f 1f 44 00 00 0f 1f 44 00 00 55 c7 05 28 3c a6 00 01 00 00 00 48 89 e5 0f ae f8 <c6> 04 25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 31 c0 48 89 e5 [ 187.204774] RIP [<ffffffff814a1786>] sysrq_handle_crash+0x16/0x20 [ 187.204774] RSP <ffff8800f23afe28> [ 187.204774] CR2: 0000000000000000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440103 Title: [Hyper-V] Kernel panic not functional on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
