[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Tim Gardner]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-49.55

---
linux (3.19.0-49.55) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1536775

  [ Colin Ian King ]

  * SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT addresses
- LP: #1529381

  [ Tim Gardner ]

  * [Config] Add DRM ast driver to udeb installer image
- LP: #1514711
  * SAUCE: (no-up) Revert "[SCSI] libiscsi: Reduce locking contention in
fast path"
- LP: #1517142

  [ Upstream Kernel Changes ]

  * powerpc/eeh: Fix recursive fenced PHB on Broadcom shiner adapter
- LP: #1532942
  * Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
- LP: #1440103
  * Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and
vmbus_connection pages on shutdown
- LP: #1440103
  * drivers: hv: vmbus: Teardown synthetic interrupt controllers on module
unload
- LP: #1440103
  * clockevents: export clockevents_unbind_device instead of
clockevents_unbind
- LP: #1440103
  * Drivers: hv: vmbus: Teardown clockevent devices on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Add support for VMBus panic notifier handler
- LP: #1440103
  * hv: run non-blocking message handlers in the dispatch tasklet
- LP: #1440103
  * Drivers: hv: vmbus: unregister panic notifier on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Implement the protocol for tearing down vmbus state
- LP: #1440103
  * kexec: define kexec_in_progress in !CONFIG_KEXEC case
- LP: #1440103
  * Drivers: hv: vmbus: add special kexec handler
- LP: #1440103
  * Drivers: hv: don't do hypercalls when hypercall_page is NULL
- LP: #1440103
  * Drivers: hv: vmbus: add special crash handler
- LP: #1440103
  * Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
- LP: #1440103
  * hyperv: Implement netvsc_get_channels() ethool op
- LP: #1494423
  * hv_netvsc: Properly size the vrss queues
- LP: #1494423
  * hv_netvsc: Allocate the sendbuf in a NUMA aware way
- LP: #1494423
  * hv_netvsc: Allocate the receive buffer from the correct NUMA node
- LP: #1494423
  * Drivers: hv: vmbus: Implement NUMA aware CPU affinity for channels
- LP: #1494423
  * Drivers: hv: vmbus: Allocate ring buffer memory in NUMA aware fashion
- LP: #1494423
  * Drivers: hv: vmbus: Improve the CPU affiliation for channels
- LP: #1494423
  * Drivers: hv: vmbus: Further improve CPU affiliation logic
- LP: #1494423

linux (3.19.0-48.54) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1536124
  * Merged back Ubuntu-3.19.0-46.52

 -- Brad Figg   Thu, 21 Jan 2016 12:29:48 -0800

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-49.55

---
linux (3.19.0-49.55) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1536775

  [ Colin Ian King ]

  * SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT addresses
- LP: #1529381

  [ Tim Gardner ]

  * [Config] Add DRM ast driver to udeb installer image
- LP: #1514711
  * SAUCE: (no-up) Revert "[SCSI] libiscsi: Reduce locking contention in
fast path"
- LP: #1517142

  [ Upstream Kernel Changes ]

  * powerpc/eeh: Fix recursive fenced PHB on Broadcom shiner adapter
- LP: #1532942
  * Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
- LP: #1440103
  * Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and
vmbus_connection pages on shutdown
- LP: #1440103
  * drivers: hv: vmbus: Teardown synthetic interrupt controllers on module
unload
- LP: #1440103
  * clockevents: export clockevents_unbind_device instead of
clockevents_unbind
- LP: #1440103
  * Drivers: hv: vmbus: Teardown clockevent devices on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Add support for VMBus panic notifier handler
- LP: #1440103
  * hv: run non-blocking message handlers in the dispatch tasklet
- LP: #1440103
  * Drivers: hv: vmbus: unregister panic notifier on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Implement the protocol for tearing down vmbus state
- LP: #1440103
  * kexec: define kexec_in_progress in !CONFIG_KEXEC case
- LP: #1440103
  * Drivers: hv: vmbus: add special kexec handler
- LP: #1440103
  * Drivers: hv: don't do hypercalls when hypercall_page is NULL
- LP: #1440103
  * Drivers: hv: vmbus: add special crash handler
- LP: #1440103
  * Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
- LP: #1440103
  * hyperv: Implement netvsc_get_channels() ethool op
- LP: #1494423
  * hv_netvsc: Properly size the vrss queues
- LP: #1494423
  * hv_netvsc: Allocate the sendbuf in a NUMA aware way
- LP: #1494423
  * hv_netvsc: Allocate the receive buffer from the correct NUMA node
- LP: #1494423
  * Drivers: hv: vmbus: Implement NUMA aware CPU affinity for channels
- LP: #1494423
  * Drivers: hv: vmbus: Allocate ring buffer memory in NUMA aware fashion
- LP: #1494423
  * Drivers: hv: vmbus: Improve the CPU affiliation for channels
- LP: #1494423
  * Drivers: hv: vmbus: Further improve CPU affiliation logic
- LP: #1494423

linux (3.19.0-48.54) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1536124
  * Merged back Ubuntu-3.19.0-46.52

 -- Brad Figg   Thu, 21 Jan 2016 12:29:48 -0800

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[paula crismaru]

Hello!

I installed the kernel in -proposed (kernel version 3.19.0-49-generic),
triggered a kernel panic and it worked as expected. The crashkernel
memory sizes I used are 512M and 384M.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

Hi Chris,

Can you verify the kernel in -proposed as requested in #33?  That way
the fix can move into -updates.

Thanks in advance!

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

We're looking at it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

To manage notifications about this bug go 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Brad Figg]

** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

Hi Joe,
Can you provide a list of commits and dependencies you have to include for the 
working test kernel?
The same or a similar issue might be occurring on Ubuntu with linux-next so we 
want to compare them.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

Hi Chris,

Here is the list of commits used in test kernel:

0f22bce staging: lustre: check kzalloc return value
1d67237 Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
a28d64c Drivers: hv: vmbus: add special crash handler
5990a10 Drivers: hv: don't do hypercalls when hypercall_page is NULL
7d8e182 Drivers: hv: vmbus: add special kexec handler
c3e9e25 kexec: define kexec_in_progress in !CONFIG_KEXEC case
e051d15 Drivers: hv: vmbus: Implement the protocol for tearing down vmbus state
7f0f4f3 Drivers: hv: vmbus: unregister panic notifier on module unload
2f940da hv: run non-blocking message handlers in the dispatch tasklet
ce30250 Drivers: hv: vmbus: Add support for VMBus panic notifier handler
9ed3a0e Drivers: hv: vmbus: Teardown clockevent devices on module unload
25a696e clockevents: export clockevents_unbind_device instead of 
clockevents_unbind
891b295 drivers: hv: vmbus: Teardown synthetic interrupt controllers on module 
unload
3efe049 Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and 
vmbus_connection pages on shutdown
45a0fc8 Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors


The following commits did not cherry-pick cleanly and needed backporting:  
e513229, 96c1d05, 652594c, 2db84ef, 2517281 and 510f7aef

The subjects listed above are the same as in mainline, but SHA1s are
different, since that is from my local repo.  Just let me know if you
need me to post the original SHA1s and I will

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[paula crismaru]

Hello!

I tested the following kernel
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/ with the following
crashkernel values: 384M and 512M. Everything worked as expected.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

That is good news, paula.  If those commits now fix this bug, I'll SRU
them to Vivid.

Thanks for the help testing!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

I created one more test kernel, which is v5.  I confirmed this test
kernel now boots.  One of the prereq backports needed to be done
differently.

The new test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/

Can you test this kernel and see if it resolves this bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[paula crismaru]

Hello!

I tested Willy with the latest kernel version (4.2.0-23-generic) and VM reboots 
itself after kernel panic.
I also tested Vivid with the following kernel 
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/. The VM doesn't boot 
after installing the kernel. I attached the log.

** Attachment added: "vivid_lp1440103V3.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4546320/+files/vivid_lp1440103V3.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

Joe, can you please re-check on the patches included, based on the no-boot 
issue from comment #24?
Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

I made some changes to the backports and have a new V3 test kernel to
try.  The test kernel  can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid

Can you test this kernel and see if it resolves this bug?

Also, can you confirm that Wily with the latest updates does not exhibit
this bug anymore?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Ovidiu Rusu]

I've installed the test kernel but the VM doesn't boot.

You can check the boot log which I attached.

** Attachment added: "boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4516994/+files/boot.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

I built a V2 Vivid test kernel with the six patches posted in comment
#16 and some prereq commits I applied instead of backporting.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid

Can you test this kernel and see if it resolves this bug?


Also, can you confirm that Wily with the latest updates does not exhibit this 
bug anymore?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

The use of a different kdump-tools package version as in bug #1400319
was due to a different error, which was anyway only on 32bit.

Nevertheless, I still tried this on the Vivid VM and verified the crash 
functionality with kdump-tools from Trusty and then the one from Wily.
With both attempts, kdump still fails with the same behavior as in comment #19.

Validation for kdump setup:
# cat /sys/kernel/kexec_*
1
402653184

# service kdump-tools status
â kdump-tools.service - Kernel crash dump capture service
   Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2015-11-05 03:01:05 PST; 1min 51s ago
  Process: 661 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
 Main PID: 661 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/kdump-tools.service

Nov 05 03:01:03 ubuntu1504srv systemd[1]: Starting Kernel crash dump capture 
service...
Nov 05 03:01:05 ubuntu1504srv kdump-tools[661]: Starting kdump-tools:  * loaded 
kdump kernel
Nov 05 03:01:05 ubuntu1504srv systemd[1]: Started Kernel crash dump capture 
service.

kdump-tools packages tested:
- vivid default
- kdump-tools_1.5.5-2ubuntu1_all - Trusty
- kdump-tools_1.5.8-4_all - Wily

** Attachment added: "crash_vivid.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4513335/+files/crash_vivid.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

It was found in bug 1400319 that the issue may be due to kdump-tools.
Can you see if this is also the case with this bug and try the version
of kdump-tools mentioned in comment #33 and #20?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

It may be that we need a combination of the six patches in the test
kernel and a new kdump-tools.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

Hi Joe,
I'm running the test kernel 3.19.0-32_3.19.0-32.37~lp1440103_amd64 on a Vivid 
either default installed or fully updated, however crashdump is not happening 
as expected.

It will show the usual crash log output, but the system will hang, never
reboot - and the crash dump file is not generated.

Attaching you the full crash serial log output.
One note to mention here is that on the console itself, after several minutes, 
there is a message showing up that CPU x, command bash not tainted.
This is showing up *only* on the console, doesn't get logged on serial output.

For validaton, I'm running this on WS 2012R2.
For crashkernel memory sizes, I tried either the default - 384M-:128M, 384M or 
512M. All of these in sets of SMP or single core.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

I built a Vivid test kernel with the six patches posted in comment #16.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid

Can you test this kernel and see if it resolves this bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.2.0-14.16

---
linux (4.2.0-14.16) wily; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1501818
  * rebase to v4.2.2
  * [Config] CONFIG_RTC_DRV_XGENE=y
- LP: #1499869

  [ Upstream Kernel Changes ]

  * mei: do not access freed cb in blocking write
- LP: #1494076
  * mei: bus: fix drivers and devices names confusion
- LP: #1494076
  * mei: bus: rename nfc.c to bus-fixup.c
- LP: #1494076
  * mei: bus: move driver api functions at the start of the file
- LP: #1494076
  * mei: bus: rename uevent handler to mei_cl_device_uevent
- LP: #1494076
  * mei: bus: don't enable events implicitly in device enable
- LP: #1494076
  * mei: bus: report if event registration failed
- LP: #1494076
  * mei: bus: revamp device matching
- LP: #1494076
  * mei: bus: revamp probe and remove functions
- LP: #1494076
  * mei: bus: add reference to bus device in struct mei_cl_client
- LP: #1494076
  * mei: bus: add me client device list infrastructure
- LP: #1494076
  * mei: bus: enable running fixup routines before device registration
- LP: #1494076
  * mei: bus: blacklist the nfc info client
- LP: #1494076
  * mei: bus: blacklist clients by number of connections
- LP: #1494076
  * mei: bus: simplify how we build nfc bus name
- LP: #1494076
  * mei: bus: link client devices instead of host clients
- LP: #1494076
  * mei: support for dynamic clients
- LP: #1494076
  * mei: disconnect on connection request timeout
- LP: #1494076
  * mei: define async notification hbm commands
- LP: #1494076
  * mei: implement async notification hbm messages
- LP: #1494076
  * mei: enable async event notifications only from hbm version 2.0
- LP: #1494076
  * mei: add mei_cl_notify_request command
- LP: #1494076
  * mei: add a handler that waits for notification on event
- LP: #1494076
  * mei: add async event notification ioctls
- LP: #1494076
  * mei: support polling for event notification
- LP: #1494076
  * mei: implement fasync for event notification
- LP: #1494076
  * mei: bus: add and call callback on notify event
- LP: #1494076
  * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED
- LP: #1494076
  * mei: me: d0i3: add the control registers
- LP: #1494076
  * mei: me: d0i3: add flag to indicate D0i3 support
- LP: #1494076
  * mei: me: d0i3: enable d0i3 interrupts
- LP: #1494076
  * mei: hbm: reorganize the power gating responses
- LP: #1494076
  * mei: me: d0i3: add d0i3 enter/exit state machine
- LP: #1494076
  * mei: me: d0i3: move mei_me_hw_reset down in the file
- LP: #1494076
  * mei: me: d0i3: exit d0i3 on driver start and enter it on stop
- LP: #1494076
  * mei: me: add sunrise point device ids
- LP: #1494076
  * mei: hbm: bump supported HBM version to 2.0
- LP: #1494076
  * mei: remove check on pm_runtime_active in __mei_cl_disconnect
- LP: #1494076
  * mei: fix debugfs files leak on error path
- LP: #1494076

  [ Upstream Kernel Changes ]

  * rebase to v4.2.2
- LP: #1492132

 -- Tim Gardner   Tue, 29 Sep 2015 09:02:13
-0700

** Changed in: linux (Ubuntu Wily)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Tim Gardner]

Applied to Wily:

Drivers: hv: kvp: check kzalloc return value
Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
Drivers: hv: vmbus: add special crash handler
Drivers: hv: don't do hypercalls when hypercall_page is NULL
Drivers: hv: vmbus: add special kexec handler
kexec: define kexec_in_progress in !CONFIG_KEXEC case


** Changed in: linux (Ubuntu Wily)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

Hi Joseph,
We got the confirmation that all the below patches must be included for the 
kdump issue.
Please provide us with a test kernel with these included so we can re-test.

Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=510f7aef65bb7ed22cf9c7f94f955727f963ede4
 

Drivers: hv: vmbus: add special crash handler
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b4370df2b1f5158de028e167974263c5757b34a6
 

Drivers: hv: don't do hypercalls when hypercall_page is NULL
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7646eaa7678fe5adc42247b4bdfbe9d9db8c253
 

Drivers: hv: vmbus: add special kexec handler
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2517281d63a2b09d94aedfb522943617048f337e
 

kexec: define kexec_in_progress in !CONFIG_KEXEC case
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2b94ed245861a7d378dcde6eef7fa7717e06e349

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Zsolt Dudás]

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: 8800f077cb00 ti: 8800f23ac000 task.ti: 
8800f23ac000
[  187.204774] RIP: 0010:[]
[  187.204774]  [] sysrq_handle_crash+0x16/0x20
[  187.204774] RSP: 0018:8800f23afe28  EFLAGS: 00010296
[  187.204774] RAX: 000f RBX: 0063 RCX: 000f
[  187.204774] RDX: 8801026d12f8 RSI: 8801026cea58 RDI: 0063
[  187.204774] RBP: 8800f23afe28 R08: 00c2 R09: 0002
[  187.204774] R10: 0260 R11: 0002 R12: 0004
[  187.204774] R13:  R14: 81cc2560 R15: 
[  187.204774] FS:  7f385dfc0700() GS:8801026c() 
knlGS:
[  187.204774] CS:  0010 DS:  ES:  CR0: 80050033
[  187.204774] CR2:  CR3: f000 CR4: 06e0
[  187.204774] Stack:
[  187.204774]  8800f23afe58 814a1f86 0002 
fffb
[  187.204774]  00980408 0002 8800f23afe78 
814a23e3
[  187.204774]  0002 8800edeec180 8800f23afe98 
81252278
[  187.204774] Call Trace:
[  187.204774]  [] __handle_sysrq+0xf6/0x150
[  187.204774]  [] write_sysrq_trigger+0x33/0x40
[  187.204774]  [] proc_reg_write+0x48/0x70
[  187.204774]  [] __vfs_write+0x18/0x40
[  187.204774]  [] vfs_write+0xa9/0x190
[  187.204774]  [] SyS_write+0x46/0xa0
[  187.204774]  [] ? __close_fd+0x8f/0xb0
[  187.204774]  [] 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  04 
25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 31 c0 48 89 e5
[  187.204774] RIP  [] sysrq_handle_crash+0x16/0x20
[  187.204774]  RSP 
[  187.204774] CR2: 

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

I performed a cherry pick of the following three commits into Wily:

2b94ed2 kexec: define kexec_in_progress in !CONFIG_KEXEC case
2517281 Drivers: hv: vmbus: add special kexec handler
b4370df Drivers: hv: vmbus: add special crash handler

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/wily/

Can you test this kernel and see if it resolves this bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

It looks like the commits requested in this bug have now landed in
upstream v4.3-rc1

** Also affects: linux (Ubuntu Wily)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Tags added: wily

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

Upstream thread:

https://lkml.org/lkml/2015/6/28/70

We can cherry-pick these commits once they are accepted in mainline.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Importance: Undecided = Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) = Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
   Status: Triaged = In Progress

** Changed in: linux (Ubuntu Vivid)
   Status: New = In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Tags removed: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

I'm attaching thee patches that went upstream as part of a larger bundle
to fix this kexec issue.


From K. Y. Srinivasan  
Subject [PATCH V2 00/10] Drivers: hv: vmbus: Enable kexec and other misc 
cleanup 
Date Thu, 4 Jun 2015 16:25:39 -0700 
  

In addition to enabling kexec, this patch-set has a bunch of miscellaneous
fixes.

In this version of the patch-set; I have fixed up the subject line for couple
of patches (Greg)

Alex Ng (1):
  Drivers: hv: balloon: Enable dynamic memory protocol negotiation with
Windows 10 hosts

K. Y. Srinivasan (1):
  Drivers: hv: vmbus: Permit sending of packets without payload

Vitaly Kuznetsov (8):
  cpu-hotplug: export cpu_hotplug_enable/cpu_hotplug_disable
  Drivers: hv: vmbus: use cpu_hotplug_enable/disable
  Drivers: hv: vmbus: remove hv_synic_free_cpu() call from
hv_synic_cleanup()
  Drivers: hv: vmbus: add special kexec handler
  Drivers: hv: don't do hypercalls when hypercall_page is NULL
  Drivers: hv: vmbus: use 'die' notification chain instead of 'panic'
  Drivers: hv: kvp: check kzalloc return value
  Drivers: hv: fcopy: dynamically allocate smsg_out in
fcopy_send_data()

 Documentation/power/suspend-and-cpuhotplug.txt |6 +-
 arch/x86/include/asm/mshyperv.h|2 +
 arch/x86/kernel/cpu/mshyperv.c |   30 +
 drivers/hv/channel.c   |4 +-
 drivers/hv/hv.c|   15 +++--
 drivers/hv/hv_balloon.c|   26 ++--
 drivers/hv/hv_fcopy.c  |   21 ---
 drivers/hv/hv_kvp.c|3 +
 drivers/hv/vmbus_drv.c |   76 +---
 kernel/cpu.c   |   13 +++--
 10 files changed, 119 insertions(+), 77 deletions(-)
-- 
1.7.4.1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [ 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

** Patch added: 02.patch
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422110/+files/02.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

** Patch added: 05.patch
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422112/+files/05.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

FYI, re: upstream status, the series was resubmitted on 6/28 but needs
an ack from the CPU hotplug folks before gregkh will accept it into his
tree. We have tested it internally, as well as testing it with our
partners.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joshua R. Poulson]

** Patch added: 03.patch
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422111/+files/03.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

Can you test the latest 4.1 upstream kernel and see if this bug still
exists?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-unstable/

** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

The patch has not been submitted yet upstream, we're going to update
this thread as soon as it will be ready.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

Thanks for the update, Chris!

** Changed in: linux (Ubuntu)
   Status: Confirmed = Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Tags removed: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[nmeier]

It was requested that I test Ballooning on 14.04.02.
Ballooning fails on 14.04.02.

Ballooning test on 14.04.02 after running apt-get upgrade
  Startup Memory : 2048
  Minimum Memory : 1024
  Maximum Memory : 8192
The utility stressapptest was used to generate memory demand.
Let memory settle to 2048MB assigned, 644MB demand.
Addd memory demand of 1664MB
Assigned memory grew to 2624MB assigned, 2125MB demand.
Let system settle to 1044MB assigned, 428MB demand
Added memory demand of 1664MB
Assigned memory grew to 2732MB assigned, 2376MB demand.
After all instances of stressapptest terminated demand dropped to 464MB
Assigned memory did not balloon down after 15 minutes.
Configured second VM to have a startup memory value to consume all of the hosts 
free memory.
Test VM assigned memory did not balloon down.
The dmesg log has stack traces for hung_task_timeout_secs.
The call traces are trying to add pages.
See attached file.

** Attachment added: dmesg.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4412805/+files/dmesg.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] 

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Chris Valean]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided = High

** Tags added: kernel-da-key kernel-hyper-v

** Changed in: linux (Ubuntu)
   Importance: High = Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440103

Title:
  [Hyper-V] Kernel panic not functional on Vivid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[814ae776]  [814ae776] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [814aef96] __handle_sysrq+0x106/0x170
  [  149.346369]  [814af443] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [8125ad98] proc_reg_write+0x48/0x70
  [  149.346369]  [811f33d7] vfs_write+0xb7/0x1f0
  [  149.346369]  [811f3ece] ? vfs_read+0x11e/0x140
  [  149.346369]  [811f3fe6] SyS_write+0x46/0xb0
  [  149.346369]  [817c924d] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [814ae776] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 88007be7fe68
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   :