New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 704330 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

power_manager: Don't install autosuspend udev rules on 'cros_embedded' devices

Project Member Reported by mka@chromium.org, Mar 22 2017

Issue description

With https://chromium-review.googlesource.com/#/c/434906/ we install udev rules to configure device autosuspend instead of using laptop-mode-tools. The CL assumes that laptop-mode-tools runs on all platforms, and therefore installs the rules on all targets. This is not correct, there are 'embedded' platforms like the OnHub routers which don't use laptop-mode-tools and enabling autosuspend caused at least one problem (b:36470502).

Don't install the autosuspend rules when the USE flag 'cros_embedded' is set. This effectively reverts to the previous situation, since laptop-mode-tools is only included on non-embedded targets by virtual/target-chromium-os.

A more fine grained solution will be needed if new 'embedded' devices are added that need autosuspend.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/25e3b5c4dd326cff1ebf384e4f8e9d86a802a3e1

commit 25e3b5c4dd326cff1ebf384e4f8e9d86a802a3e1
Author: Matthias Kaehlcke <mka@chromium.org>
Date: Thu Mar 23 18:55:50 2017

power: Don't install autosuspend rules on 'embedded' devices

CL:434906 installs static udev rules to configure autosuspend, which was
previously handled by laptop-mode-tools. The rules are installed on all
targets, however laptop-mode-tools is only used on non-'embedded' devices.
Expanding autosuspend unintendedly to all device has caused at least one
problem (b:36470502).

Limit the installation of the autosuspend rules to non-'embedded' devices
to return to the previous situation.

BUG= chromium:704330 , b:36470502
TEST=emerge-whirlwind power_manager
  ls /build/gru/lib/udev/rules.d/99-autosuspend.rules
    => No such file or directory
  emerge-gru power_manager
  ls /build/gru/lib/udev/rules.d/99-autosuspend.rules
    => /build/gru/lib/udev/rules.d/99-autosuspend.rules

Change-Id: Ia87d07746f2457884c8e6641ab4ad93b780c6fdd
Reviewed-on: https://chromium-review.googlesource.com/458557
Commit-Ready: Matthias Kaehlcke <mka@chromium.org>
Tested-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>

[modify] https://crrev.com/25e3b5c4dd326cff1ebf384e4f8e9d86a802a3e1/chromeos-base/power_manager/power_manager-9999.ebuild

Comment 2 by mka@chromium.org, Mar 24 2017

Cc: bhthompson@chromium.org
Labels: Merge-Request-58
Status: Fixed (was: Assigned)
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 25 2017

Labels: -Merge-Request-58 Hotlist-Merge-Approved Merge-Approved-58
Your change meets the bar and is auto-approved for M58. Please go ahead and merge the CL to branch 3029 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 27 2017

Labels: merge-merged-release-R58-9334.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/8d7d51737a0212e56a4e41d3800187ba0820ba17

commit 8d7d51737a0212e56a4e41d3800187ba0820ba17
Author: Matthias Kaehlcke <mka@chromium.org>
Date: Mon Mar 27 16:35:23 2017

power: Don't install autosuspend rules on 'embedded' devices

CL:434906 installs static udev rules to configure autosuspend, which was
previously handled by laptop-mode-tools. The rules are installed on all
targets, however laptop-mode-tools is only used on non-'embedded' devices.
Expanding autosuspend unintendedly to all device has caused at least one
problem (b:36470502).

Limit the installation of the autosuspend rules to non-'embedded' devices
to return to the previous situation.

BUG= chromium:704330 , b:36470502
TEST=emerge-whirlwind power_manager
  ls /build/gru/lib/udev/rules.d/99-autosuspend.rules
    => No such file or directory
  emerge-gru power_manager
  ls /build/gru/lib/udev/rules.d/99-autosuspend.rules
    => /build/gru/lib/udev/rules.d/99-autosuspend.rules

Change-Id: Ia87d07746f2457884c8e6641ab4ad93b780c6fdd
Reviewed-on: https://chromium-review.googlesource.com/458557
Commit-Ready: Matthias Kaehlcke <mka@chromium.org>
Tested-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
(cherry picked from commit 25e3b5c4dd326cff1ebf384e4f8e9d86a802a3e1)
Reviewed-on: https://chromium-review.googlesource.com/458985
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Commit-Queue: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/8d7d51737a0212e56a4e41d3800187ba0820ba17/chromeos-base/power_manager/power_manager-9999.ebuild

Comment 5 by mka@chromium.org, Mar 27 2017

Labels: -Hotlist-Merge-Approved -Merge-Approved-58

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment