Ubuntu
linux package

  1. Vivid (15.04)
  2. Bug #1440103
  3. Comment #22

Comment 22 for bug 1440103

Revision history for this message
Chris Valean (cvalean) wrote :

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