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

Issue 834062 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ frankhu@chromium.org
█ choonc@google.com
█ jtho@chromium.org
█ katierh@chromium.org
EstimatedDays: ----
NextAction: 2019-07-09
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Teemo: core temperature above threshold

Project Member Reported by mzhuo@chromium.org, Apr 17 2018 
ChromeOS: R67-10575.0.0
Teemo: meeting mode
Teemo has Mimo, Huddly and Atrus connected. 

What steps will reproduce the problem?
(1) Reboot Teemo
(2) Run meeting 
(3)

What is the expected result?
No error log for "core temperature above threshold"

What happens instead?
1. After Teemo boots up "core temperature above threshold" is reported. 
2 During meeting test "core temperature above threshold" is reported too.


log
=====2018-04-17T08:46:02.905488-07:00 CRIT kernel: [    6.937756] CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905493-07:00 CRIT kernel: [    6.937756] CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905493-07:00 CRIT kernel: [    6.937758] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905494-07:00 CRIT kernel: [    6.937760] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905494-07:00 CRIT kernel: [    6.937760] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905494-07:00 CRIT kernel: [    6.937761] CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905495-07:00 CRIT kernel: [    6.937762] CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905495-07:00 CRIT kernel: [    6.937775] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905496-07:00 CRIT kernel: [    6.937792] CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.905496-07:00 CRIT kernel: [    6.937794] CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)
2018-04-17T08:46:02.943473-07:00 INFO kernel: [    6.975744] CPU2: Core temperature/speed normal
2018-04-17T08:46:02.943478-07:00 INFO kernel: [    6.975744] CPU0: Core temperature/speed normal
2018-04-17T08:46:02.943478-07:00 INFO kernel: [    6.975745] CPU1: Package temperature/speed normal
2018-04-17T08:46:02.943479-07:00 INFO kernel: [    6.975746] CPU3: Package temperature/speed normal
2018-04-17T08:46:02.943479-07:00 INFO kernel: [    6.975746] CPU0: Package temperature/speed normal
2018-04-17T08:46:02.943480-07:00 INFO kernel: [    6.975751] CPU2: Package temperature/speed normal
2018-04-17T08:46:02.943480-07:00 INFO kernel: [    6.975781] CPU6: Package temperature/speed normal
2018-04-17T08:46:02.943480-07:00 INFO kernel: [    6.975782] CPU4: Package temperature/speed normal
2018-04-17T08:46:02.943481-07:00 INFO kernel: [    6.975783] CPU5: Package temperature/speed normal
2018-04-17T08:46:02.943481-07:00 INFO kernel: [    6.975785] CPU7: Package temperature/speed normal
2018-04-17T08:55:37.030476-07:00 CRIT kernel: [  581.334591] CPU1: Core temperature above threshold, cpu clock throttled (total events = 68)
2018-04-17T08:55:37.030485-07:00 CRIT kernel: [  581.334592] CPU3: Core temperature above threshold, cpu clock throttled (total events = 68)
2018-04-17T08:55:37.030486-07:00 CRIT kernel: [  581.334594] CPU3: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030486-07:00 CRIT kernel: [  581.334595] CPU4: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030486-07:00 CRIT kernel: [  581.334596] CPU5: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030487-07:00 CRIT kernel: [  581.334622] CPU1: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030487-07:00 CRIT kernel: [  581.334624] CPU0: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030494-07:00 CRIT kernel: [  581.334625] CPU2: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030495-07:00 CRIT kernel: [  581.334626] CPU7: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.030495-07:00 CRIT kernel: [  581.334627] CPU6: Package temperature above threshold, cpu clock throttled (total events = 123)
2018-04-17T08:55:37.031471-07:00 INFO kernel: [  581.335590] CPU1: Core temperature/speed normal
2018-04-17T08:55:37.031475-07:00 INFO kernel: [  581.335591] CPU6: Package temperature/speed normal
2018-04-17T08:55:37.031476-07:00 INFO kernel: [  581.335592] CPU7: Package temperature/speed normal
2018-04-17T08:55:37.031476-07:00 INFO kernel: [  581.335592] CPU3: Core temperature/speed normal
2018-04-17T08:55:37.031477-07:00 INFO kernel: [  581.335594] CPU3: Package temperature/speed normal
2018-04-17T08:55:37.031477-07:00 INFO kernel: [  581.335594] CPU5: Package temperature/speed normal
2018-04-17T08:55:37.031477-07:00 INFO kernel: [  581.335595] CPU4: Package temperature/speed normal
2018-04-17T08:55:37.031478-07:00 INFO kernel: [  581.335619] CPU1: Package temperature/speed normal
2018-04-17T08:55:37.031478-07:00 INFO kernel: [  581.335622] CPU0: Package temperature/speed normal
2018-04-17T08:55:37.031479-07:00 INFO kernel: [  581.335623] CPU2: Package temperature/speed normal
2018-04-17T09:00:55.016477-07:00 CRIT kernel: [  899.327672] CPU0: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016489-07:00 CRIT kernel: [  899.327673] CPU2: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016490-07:00 CRIT kernel: [  899.327675] CPU5: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016491-07:00 CRIT kernel: [  899.327676] CPU4: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016496-07:00 CRIT kernel: [  899.327677] CPU3: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016497-07:00 CRIT kernel: [  899.327678] CPU1: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016497-07:00 CRIT kernel: [  899.327680] CPU7: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.016498-07:00 CRIT kernel: [  899.327681] CPU6: Package temperature above threshold, cpu clock throttled (total events = 185)
2018-04-17T09:00:55.044480-07:00 INFO kernel: [  899.355647] CPU6: Package temperature/speed normal
debug-logs_20180417-085526.tgz
10.8 MB Download

Comment 1 by mzhuo@chromium.org, Apr 17 2018

Cc: jtho@chromium.org

Comment 2 by mzhuo@chromium.org, Apr 17 2018

Cc: choonc@google.com

Comment 3 by jtho@google.com, Apr 18 2018 

I think we were seeing the same messages also during run-in tests in factory for bleemo.

Do we see this in Teemo also during other use cases than ours?

The throttling seems to last only extremely short time, after which everything is normal for a long time.

Comment 4 by darekm@chromium.org, May 14 2018 

What would be a way to go forward with this bug? It seems the time the temp is above normal is pretty short, could it be a problem with temperature reporting? Is it possible that throttling CPU for 0.03 s brings temperature back to normal?

Comment 5 by benhenry@google.com, Jan 10

Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.
►

Sign in to add a comment