kernel-packages team mailing list archive

[Launchpad Bug Tracker <1466013@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package makedumpfile - 1.5.5-2ubuntu1.3

---------------
makedumpfile (1.5.5-2ubuntu1.3) trusty; urgency=medium

  * Add upstart job to minimize interferences from sysVinit scripts
    during kernel crash dump collection. (LP: #1466013)

 -- Louis Bouchard <louis.bouchard@xxxxxxxxxx>  Thu, 18 Jun 2015
11:16:13 +0200

** Changed in: makedumpfile (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

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

Title:
  kdump-tools does not have an upstart job

Status in makedumpfile package in Ubuntu:
  Invalid
Status in makedumpfile source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  The upstart job avoids the sysVinit scripts to be run while kdump-tools is doing the kernel crash dump capture

  [Impact]
  Potential impossibility to capture a kernel crash dump

  [Fix]
  Add kdump-tools.conf upstart job

  [Test Case]
  With the upstart job, the kdump-tools kernel dump capture will run before any of the tasks triggered by RUNLEVEL [2345] will run.

  [Regression]
  Minimal; The job uses the same syntax as the sysVinit job currently in use.

  [Original description of the problem]

  kdump-tools relies on a sysVinit script to  capture the kernel dump.
  It sometimes gets interference from other jobs starting at runlevels 2
  to 5.

  An upstart job starting before RUNLEVEL is emitted would alleviate
  that.

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