New issue
Advanced search Search tips

Issue 726719 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

M58 broke enterprise reporting temperatures for Intel CPUs

Project Member Reported by jayhlee@google.com, May 26 2017

Issue description

Chrome Version: Chrome OS 58 on Intel boards

What steps will reproduce the problem?
(1) put an Intel Chrome device on 57 and enterprise enroll device so that it gets a policy to auto-start a kiosk app.
(2) give device 5 minutes and observe device temperatures including CPU cores are reporting and visible in admin console (should see something like "Core 1", "Core 2" as well as motherboard sensors on devices with motherboard sensors)
(3) Allow device to update to M58 stable.
(4) Let device run on M58 for 5 minutes with auto-started kiosk app.

What is the expected result?
M58 should continue to report Intel CPU temps.

What happens instead?
Intel CPU temps are no longer reported by M58

Other details:
Sigh. looks like something changed with M58 kernel so the files are moved around. Temps for Intel CPUs were reported in:

/sys/class/hwmon/hwmon*/device/temp*_input

files but now they seem to have moved to:

/sys/class/hwmon/hwmon*/temp*_input

The problem is right here:

https://chromium.googlesource.com/chromium/src/+/master/chrome/browser/chromeos/policy/device_status_collector.cc#186
 

Comment 1 by jayhlee@google.com, May 26 2017

Cc: pastarmovj@chromium.org pbond@chromium.org atwilson@chromium.org
I think we can solve by just removing the if statement, everything we need should be in:

/sys/class/hwmon/hwmon*/temp*_input

for Intel and ARM now. Will put together a CL.
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 14 2017

Labels: Hotlist-Google

Comment 3 by kotah@chromium.org, Aug 16 2017

@jayhlee, can you assign this bug to appropriate Eng team or archive this issue?
Components: Enterprise

Comment 5 by jayhlee@google.com, Oct 9 2017

Status: WontFix (was: Untriaged)
This is working properly now.

Sign in to add a comment