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

Issue 921195 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Fizz device doe not boot in Meet mode, crashes observed

Project Member Reported by ykrychala@google.com, Jan 11

Issue description

ChromeOS version: 70.0.3538.110
ChromeOS device model: ASUS Chromebox 3 (Fizz)
Case#: 17585467

Description:
Customer is unable to get their CfM device working in Meet mode, the device shows an error on startup. Multiple crashes were found in log files.
Wiping the device did not help.
Upgrading the device manually via USB from v68 to v70 did not help.
It is shown as healthy in Admin Console.

Steps to reproduce: 
1. Enroll the device as CfM
2. Boot it up

Current Behavior / Reproduction: 
Error 'Could not start Meet restart device. Contact the organization's support team if meet does not start. ' is shown on the screen, Meet mode does not start

Expected Behavior: 
Device successfully boots up and goes to Meet mode allowing conference calls.

Drive link to logs: 
https://drive.google.com/open?id=1MVPDKCuqFGaETHKy9AQGgNFiZvbDY0Cv (v68)
https://drive.google.com/open?id=1oFbUXaNK6b_uQZHOecZ2ie-HIv9XBk3H (v70)

Screenshot:
https://drive.google.com/open?id=1O6aF6O_VOL38t4fyZi8u-1H4zC4IECHO

S/N:
J7MSCX014361

I've found CRIT errors related to CPU temperature so it seems to be a hardware issue:


019-01-10T12:28:24.827033+01:00 CRIT kernel: [   11.859547] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827034+01:00 CRIT kernel: [   11.859548] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827035+01:00 CRIT kernel: [   11.859549] CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827035+01:00 CRIT kernel: [   11.859550] CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827036+01:00 CRIT kernel: [   11.859551] CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827036+01:00 CRIT kernel: [   11.859552] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827037+01:00 CRIT kernel: [   11.859553] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
2019-01-10T12:28:24.827038+01:00 CRIT kernel: [   11.859562] CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)

Please advise is RMS the only option or the device can be recovered to working state.

Latest crash IDs:
1544023733,8ea6180bde5ca814,ChromeOS_ARC
1544028112,a53b90c8bac7cfd5,ChromeOS
1544028376,e84fbad3d534f38b,ChromeOS
1544087543,f491c76748d278e1,ChromeOS
1544088096,230af2843334039f,ChromeOS
1544088132,5be3629d5e9ff220,ChromeOS
1544088399,e9144071f3469b8c,ChromeOS
1544099206,79ae256895c6c9bc,ChromeOS
1544099278,234c372e8564cf91,ChromeOS
1544102963,ab558165d114f980,ChromeOS
1544103466,547c77628cc1e676,ChromeOS
1544173561,93d688b66af49ca6,ChromeOS
 
This unit is affected by b/120858063. This crbug may be closed as duplicate.

Sign in to add a comment