Can't stop dptf upstart job |
||||||
Issue descriptionChromeOS Test Image Version: 9971.0.0 What steps will reproduce the problem? (1) Install a fresh new 9971.0.0 test image. (2) "stop dptf" What is the expected result? The dptf job should be stopped. What happens instead? Command is stuck and doesn't complete. The result of "status dptf" shows that upstart is tracking the wrong pid.
,
Sep 25 2017
,
Sep 26 2017
https://chromium-review.googlesource.com/684188 fixes the issue for me
,
Sep 26 2017
,
Sep 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/12880aa5aa4d4266b61bec0a5a199c555d7b6bc6 commit 12880aa5aa4d4266b61bec0a5a199c555d7b6bc6 Author: Patrick Georgi <pgeorgi@google.com> Date: Tue Sep 26 18:15:53 2017 sys-power/dptf: Fix upstart configuration "expect fork" doesn't work properly with scripted (or through-shell) invocation of the daemon. Instead keep esif_ufd in foreground (-n) and let upstart track that process (which is upstart's preferred approach anyway). BUG= chromium:768297 BRANCH=none TEST=Boot Chrome OS, check that `status dptf` returns the PID of the esif_ufd process, that `stop dptf` works, and that `start dptf` returns the correct PID of the newly started process. Change-Id: Ic1743e15af15ab07916435e1da9e1a4ce562513a Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://chromium-review.googlesource.com/684188 Commit-Ready: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Pi-Hsun Shih <pihsun@chromium.org> [modify] https://crrev.com/12880aa5aa4d4266b61bec0a5a199c555d7b6bc6/sys-power/dptf/files/dptf.conf [rename] https://crrev.com/12880aa5aa4d4266b61bec0a5a199c555d7b6bc6/sys-power/dptf/dptf-8.4.10100-r5.ebuild
,
Sep 26 2017
,
Jan 22 2018
,
Jan 23 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by pihsun@chromium.org
, Sep 25 2017