New issue
Advanced search Search tips

Issue 891024 link

Starred by 5 users
Status: Duplicate
Merged: issue 906523
Owner:
mutexlox@chromium.org
Closed: Jan 4
Cc:
smbar...@chromium.org
mutexlox@chromium.org
dgreid@chromium.org
za...@chromium.org
tbuck...@chromium.org
rohi...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crostini: Terminal closing after device woke up from sleep mode

Project Member Reported by avkodipelli@chromium.org, Oct 1 
Chrome Version: 70.0.3538.34
Chrome OS Version: 11021.28.0
Chrome OS Platform: Eve, snappy
Network info: WiFi

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Install crostini and open terminal.
(2) Either close lid or leave device to go sleep mode.
(3) Open lid or press any key from keyboard.

Expected Result:
- Terminal should work without any issues.

Actual Result:
- Terminal is closing.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Sometimes. Rare case scenario.

Comment 2 by tbuck...@chromium.org, Oct 1

Owner: mutexlox@chromium.org
Status: Assigned (was: Untriaged)
@mutexlox this might be related to TSC init / clock drift? Feel free to dedupe if so.

Comment 3 by mutexlox@chromium.org, Oct 3 

Yes, this definitely seems related.

Logs contain:

2018-10-01T20:52:12.612234+00:00 INFO VM(3)[6670]: [    0.001000] WARNING: CPU: 0 PID: 0 at ../../../../../tmp/portage/sys-kernel/chromeos-kernel-4_14-4.14.67-r477/work/chromeos-kernel-4_14-4.14.67/arch/x86/kernel/tsc.c:1315             determine_cpu_tsc_frequencies+0xf3/0xfa#015

< snip >

2018-10-01T20:52:12.650769+00:00 INFO VM(3)[6670]: [    0.004005] tsc: Marking TSC unstable due to could not calculate TSC khz#015

< snip >

2018-10-01T21:04:38.320368+00:00 INFO VM(3)[6670]: [  745.552162] watchdog: BUG: soft lockup - CPU#2 stuck for 121s! [swapper/2:0]#015

I haven't looked at this deeply enough to *definitively* say that it's the same bug, but it seems very time related and if nothing else related to  https://crbug.com/823406 .

Comment 4 by mutexlox@chromium.org, Oct 4

Cc: smbar...@chromium.org mutexlox@chromium.org za...@chromium.org
 Issue 884938  has been merged into this issue.

Comment 5 by avkodipelli@chromium.org, Nov 26

Labels: M-72
Observed this issue on basking(reef) device in 11297.0.0, 72.0.3618.0.
Feedback report: https://listnr.corp.google.com/report/85810311536

Comment 6 by mutexlox@chromium.org, Nov 27 

This log also contains:

2018-11-26T23:34:20.328720+00:00 INFO VM(5)[21028]: [ 3402.994403] watchdog: BUG: soft lockup - CPU#0 stuck for 2722s! [swapper/0:0]#015

however this log does *not* have the "Marking TSC unstable" warning, which does make me think it's distinct from  https://crbug.com/878908 

I suspect that this is the same as https://crbug.com/906523.

Does this issue happen more reliably when you are using near-100% CPU when the chromebook is suspended?

Comment 7 by avkodipelli@chromium.org, Nov 27 

not observed every time while device wake up from sleep mode. randomly observing this issue.

Comment 8 by mutexlox@chromium.org, Nov 27 

If you have some time, can you try to run a workload that uses at 100% CPU in the guest (say, a long-running compilation), and see if it reproduces more reliably?

Comment 9 by mutexlox@chromium.org, Jan 4

Mergedinto: 906523
Status: Duplicate (was: Assigned)
Deduping this into 906523, as I believe it's the same issue.
►

Sign in to add a comment