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

Issue 850944 link

Starred by 5 users

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Jul 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Freezing issues in Chrome OS

Project Member Reported by marcore@chromium.org, Jun 8 2018

Issue description

ChromeOS version: 66.0.3359.203
ChromeOS device model: Acer Chromebook 11 (C730 / C730E)
Case#: 14813438

Description:
Users are experiencing random freezes on different Acer Chrome devices across different Chrome OS versions. Initially customer reported the issue happened with version 62 and it continues to happen with newer versions.
Issue doesn’t happen with v61. Most of the time, the device freezes and if typing no characters are shown. Many times, after about 20 to 30 seconds, the device will recover itself and anything typed while frozen will be displayed and the cursor starts to respond. Using "alt+volume up+x" does not help recover the devices from a freeze. Users also reported that at times the device will restart and reboot and go back to a login prompt.
The customer did mention that the issue doesn’t happen when using ephemeral profiles.

Steps to reproduce: 
login.
Current Behavior / Reproduction: 
freeze
Expected Behavior: 
no freeze
in the log I see:
file: G5_6-6-18/var/log/ui/ui.20180606-102043
[0606/102250.144208:WARNING:diagnostics_writer.cc(211)] [FAIL] 009 PathUserData (Path contents too large (2084519371) for: /home/chronos)
[0606/102250.248621:WARNING:diagnostics_writer.cc(211)] [FAIL] 016 JSONLocalState (File too big)
[0606/102250.333682:WARNING:diagnostics_writer.cc(211)] [FAIL] 002 SQLiteIntegrityCookie (File not found)
[0606/102250.438137:WARNING:diagnostics_writer.cc(211)] Finished 18 tests.
[0606/102250.438256:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Install type
[0606/102250.438322:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Chrome version test
[0606/102250.438388:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: User data path
[0606/102250.438451:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Local state path
[0606/102250.438516:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: App dictionaries directory path
[0606/102250.438578:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Resources path
[0606/102250.438640:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Available disk space
[0606/102250.438703:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: User preferences integrity
[0606/102250.438767:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Local state integrity
[0606/102250.438831:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Bookmark file
[0606/102250.438895:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Web Data database
[0606/102250.439009:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Cookie database
[0606/102250.439076:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Favicons database
[0606/102250.439138:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: History database
[0606/102250.439199:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Top Sites database
[0606/102250.439260:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: Database tracker database
[0606/102250.439320:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: NSS certificate database
[0606/102250.439381:WARNING:diagnostics_writer.cc(211)] Finished Recovery for: NSS Key database
[0606/102250.439427:WARNING:diagnostics_writer.cc(211)] Finished All Recovery operations.
as in crbug.com/815269

Drive link to logs: 
device a) https://drive.google.com/open?id=1QLWj31UZQNpTk3vAT0i9gpPqFW9mtoMa
device b) https://drive.google.com/open?id=1gcGrlvZIHbhz9Fkib31gPoYGlLm83dqH
policies: https://drive.google.com/open?id=1-Yx09g_K9PScNrTDUC5vDvboXm3OVvwL
Customer info: https://drive.google.com/open?id=1Bi9BoLGaaBLoXOCnrkCSiS99oceHFiA-IZsde1CSCKU
 
Additional info: There are no specific steps to reproduce the issue. The freezes seem to happen randomly when users perform regular activities (e.g. updates, browsing, etc.). Issue only happens when the following is true:

- Device is Acer Chromebook 11 (C730 / C730E)
- Chrome version is 62 or higher
- Device is not configured to have ephemeral profiles (DeviceEphemeralUsersEnabled value is set to "false")

Will check if we can get a video of the issue. Let us know if more information is needed.

Comment 2 by gm...@morris54.org, Jun 12 2018

Moved 29 devices to beta channel. Out of the 29 devices, 5 of the them had lockups within the first few minutes after logging back in with the same user account after updating to 67.0.3396.78. Logs and video links sent to support under case #14813438.
Cc: vkasatkin@google.com
Customer provided additional details, logs and video of the issue:
https://docs.google.com/document/d/1HzHwCIlQGHX5TU05tvib_oyYx6ga3C-nMFdWSYnIWHc/edit?usp=sharing

Hi Team, could we get an update on this issue? Thanks

Comment 5 by ryutas@chromium.org, Jun 26 2018

Hi team,

From device c.) in https://docs.google.com/document/d/1HzHwCIlQGHX5TU05tvib_oyYx6ga3C-nMFdWSYnIWHc/edit
Device locked up on 6/12/2018 at 10:02 a.m. CDT 

I noticed below messages in the message log.
----
2018-06-12T09:59:58.296045-05:00 ERR cras_server[1507]: no ini file /etc/cras/GNAWTY/dsp.ini
2018-06-12T09:59:58.296064-05:00 ERR cras_server[1507]: cannot create dsp ini
2018-06-12T09:59:58.331890-05:00 NOTICE conntrack-tools[1515]: configuring helper `mdns' with queuenum=6 and queuelen=10240
2018-06-12T09:59:58.331916-05:00 NOTICE conntrack-tools[1515]: policy name=mdns expect_timeout=30 expect_max=8
2018-06-12T09:59:58.331965-05:00 NOTICE conntrack-tools[1515]: helper `mdns' configured successfully
2018-06-12T09:59:58.331978-05:00 NOTICE conntrack-tools[1515]: configuring helper `ssdp' with queuenum=5 and queuelen=10240
2018-06-12T09:59:58.332144-05:00 NOTICE conntrack-tools[1515]: policy name=ssdp expect_timeout=300 expect_max=8
2018-06-12T09:59:58.332234-05:00 NOTICE conntrack-tools[1515]: helper `ssdp' configured successfully
2018-06-12T09:59:58.332250-05:00 NOTICE conntrack-tools[1515]: configuring helper `ssdp' with queuenum=5 and queuelen=10240
2018-06-12T09:59:58.332262-05:00 NOTICE conntrack-tools[1515]: policy name=ssdp expect_timeout=300 expect_max=8
2018-06-12T09:59:58.332302-05:00 NOTICE conntrack-tools[1515]: helper `ssdp' configured successfully
2018-06-12T09:59:58.332423-05:00 NOTICE conntrack-tools[1515]: initialization completed
2018-06-12T09:59:58.332448-05:00 NOTICE conntrack-tools[1515]: -- starting in console mode --
2018-06-12T09:59:58.332579-05:00 ERR conntrack-tools[1515]: failed to process message
2018-06-12T09:59:58.344064-05:00 INFO kernel: [   10.404248] zram: Added device: zram0
2018-06-12T09:59:58.349489-05:00 NOTICE swap[1531]: setting zram size to 2944548 Kb
2018-06-12T09:59:58.361057-05:00 INFO kernel: [   10.421251] zram0: detected capacity change from 0 to 2944548864
2018-06-12T09:59:58.394054-05:00 INFO kernel: [   10.454420] Adding 2875532k swap on /dev/zram0.  Priority:-1 extents:1 across:2875532k SS
2018-06-12T09:59:58.483373-05:00 INFO minijail0[1563]: libminijail[1563]: not running init loop, exiting immediately
2018-06-12T09:59:58.524474-05:00 ERR kernel: [   10.584291] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered
2018-06-12T09:59:58.524499-05:00 ERR kernel: [   10.584302] byt-max98090 byt-max98090: snd_soc_register_card failed -517
2018-06-12T09:59:58.554610-05:00 INFO p2p-server[1564]: p2p-server starting [../../../../../../../tmp/portage/chromeos-base/p2p-0.0.1-r2848/work/p2p-0.0.1/p2p/server/main.cc:59]
2018-06-12T09:59:58.577043-05:00 INFO kernel: [   10.637488] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops 0xffffffffb6c6f770)
2018-06-12T09:59:58.577066-05:00 ERR kernel: [   10.637664] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered
2018-06-12T09:59:58.577085-05:00 ERR kernel: [   10.637670] byt-max98090 byt-max98090: snd_soc_register_card failed -517
2018-06-12T09:59:58.649047-05:00 INFO kernel: [   10.709274] Intel(R) Wireless WiFi driver for Linux
2018-06-12T09:59:58.649072-05:00 INFO kernel: [   10.709283] Copyright(c) 2003- 2015 Intel Corporation
2018-06-12T09:59:58.663890-05:00 INFO cryptohomed[1208]: Freeing disk space by deleting user /home/.shadow/21a6aa2229a0697bf8feabee060faa296075fbf1
2018-06-12T09:59:58.672198-05:00 ERR kernel: [   10.732595] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered
2018-06-12T09:59:58.672224-05:00 ERR kernel: [   10.732606] byt-max98090 byt-max98090: snd_soc_register_card failed -517
2018-06-12T09:59:58.672228-05:00 WARNING kernel: [   10.732916] iwlwifi 0000:01:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2
2018-06-12T09:59:58.673040-05:00 ERR kernel: [   10.733880] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered
2018-06-12T09:59:58.673062-05:00 ERR kernel: [   10.733890] byt-max98090 byt-max98090: snd_soc_register_card failed -517
2018-06-12T09:59:58.679155-05:00 INFO kernel: [   10.739923] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
2018-06-12T09:59:58.680045-05:00 INFO kernel: [   10.740385] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
2018-06-12T09:59:58.706055-05:00 INFO kernel: [   10.767155] iwlwifi 0000:01:00.0: loaded firmware version 17.388f111f.0 op_mode iwlmvm
2018-06-12T09:59:58.707203-05:00 INFO p2p-http-server[1583]: p2p-http-server starting [../../../../../../../tmp/portage/chromeos-base/p2p-0.0.1-r2848/work/p2p-0.0.1/p2p/http_server/main.cc:49]
2018-06-12T09:59:58.707271-05:00 INFO p2p-http-server[1583]: Maximum download rate per connection set to 125000 bytes/sec [../../../../../../../tmp/portage/chromeos-base/p2p-0.0.1-r2848/work/p2p-0.0.1/p2p/http_server/main.cc:75]
-----

-----
2018-06-12T10:00:03.990285-05:00 WARNING kernel: [   16.850540] ------------[ cut here ]------------
2018-06-12T10:00:03.990308-05:00 WARNING kernel: [   16.850571] WARNING: CPU: 0 PID: 1094 at ../../../../../tmp/portage/sys-kernel/chromeos-kernel-4_4-4.4.127-r1484/work/chromeos-kernel-4_4-4.4.127/net/wireless/util.c:1143 cfg80211_calculate_bitrate+0xe0/0x195 [cfg80211]
2018-06-12T10:00:03.990312-05:00 WARNING kernel: [   16.850575] Modules linked in: ccm cmac rfcomm uinput iwlmvm snd_hda_codec_hdmi iwlwifi iwl7000_mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_soc_sst_baytrail_pcm snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_sst_byt_max98090_mach snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform ip6t_REJECT nf_reject_ipv6 snd_soc_max98090 snd_soc_sst_acpi snd_soc_sst_match zram fuse cfg80211 ip6table_filter btusb btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core joydev
2018-06-12T10:00:03.990314-05:00 WARNING kernel: [   16.850643] CPU: 0 PID: 1094 Comm: shill Tainted: G        W       4.4.127-13890-g6c206f1711d4 #1
2018-06-12T10:00:03.990317-05:00 WARNING kernel: [   16.850647] Hardware name: GOOGLE Gnawty, BIOS Google_Gnawty.5216.239.123 04/23/2017
2018-06-12T10:00:03.990319-05:00 WARNING kernel: [   16.850651]  ffffffffc03ee46d caf0d7776f283b36 ffff88007256b748 ffffffffb66dd66e
2018-06-12T10:00:03.990322-05:00 WARNING kernel: [   16.850659]  ffff88007256b780 ffffffffb66dd623 caf0d7776f283b36 0000000000000000
2018-06-12T10:00:03.990324-05:00 WARNING kernel: [   16.850667]  0000000000000282 caf0d7776f283b36 0000000000000000 ffff88007256b7c0
2018-06-12T10:00:03.990326-05:00 WARNING kernel: [   16.850675] Call Trace:
2018-06-12T10:00:03.990328-05:00 WARNING kernel: [   16.850685]  [<ffffffffb66dd66e>] __dump_stack+0x19/0x1b
2018-06-12T10:00:03.990330-05:00 WARNING kernel: [   16.850690]  [<ffffffffb66dd623>] dump_stack+0x4f/0x81
2018-06-12T10:00:03.990333-05:00 WARNING kernel: [   16.850696]  [<ffffffffb646ce2c>] __warn+0xba/0xf1
2018-06-12T10:00:03.990335-05:00 WARNING kernel: [   16.850701]  [<ffffffffb646cf8a>] warn_slowpath_null+0x38/0x3d
2018-06-12T10:00:03.990337-05:00 WARNING kernel: [   16.850715]  [<ffffffffc03b08e1>] cfg80211_calculate_bitrate+0xe0/0x195 [cfg80211]
2018-06-12T10:00:03.990339-05:00 WARNING kernel: [   16.850730]  [<ffffffffc03bf1dd>] nl80211_put_sta_rate+0x31/0x13a [cfg80211]
2018-06-12T10:00:03.990342-05:00 WARNING kernel: [   16.850745]  [<ffffffffc03bc396>] nl80211_send_station+0x2bc/0x73b [cfg80211]
2018-06-12T10:00:03.990344-05:00 WARNING kernel: [   16.850751]  [<ffffffffb6584fdf>] ? ksize+0x15/0x8e
2018-06-12T10:00:03.990346-05:00 WARNING kernel: [   16.850766]  [<ffffffffc03c1800>] nl80211_get_station+0x162/0x1be [cfg80211]
2018-06-12T10:00:03.990348-05:00 WARNING kernel: [   16.850777]  [<ffffffffb6ab7ae3>] genl_rcv_msg+0x389/0x3ef
2018-06-12T10:00:03.990350-05:00 WARNING kernel: [   16.850783]  [<ffffffffb6ab775a>] ? genl_unbind+0x81/0x81
2018-06-12T10:00:03.990353-05:00 WARNING kernel: [   16.850787]  [<ffffffffb6ab466a>] netlink_rcv_skb+0x47/0x95
2018-06-12T10:00:03.990355-05:00 WARNING kernel: [   16.850792]  [<ffffffffb6ab7614>] genl_rcv+0x28/0x37
2018-06-12T10:00:03.990357-05:00 WARNING kernel: [   16.850796]  [<ffffffffb6ab3270>] netlink_unicast+0x146/0x1ae
2018-06-12T10:00:03.990359-05:00 WARNING kernel: [   16.850801]  [<ffffffffb6ab5a0a>] netlink_sendmsg+0x2ce/0x300
2018-06-12T10:00:03.990361-05:00 WARNING kernel: [   16.850807]  [<ffffffffb6b71fcf>] sock_sendmsg_nosec+0x18/0x25
2018-06-12T10:00:03.990363-05:00 WARNING kernel: [   16.850812]  [<ffffffffb6b72324>] SyS_sendto+0x114/0x180
2018-06-12T10:00:03.990366-05:00 WARNING kernel: [   16.850817]  [<ffffffffb6b72c9a>] ? SyS_recvmsg+0x6e/0xc1
2018-06-12T10:00:03.990368-05:00 WARNING kernel: [   16.850824]  [<ffffffffb6b9c7d3>] entry_SYSCALL_64_fastpath+0x27/0x9b
2018-06-12T10:00:03.990370-05:00 WARNING kernel: [   16.850828] ---[ end trace 71d380af5da01a65 ]---
2018-06-12T10:00:04.006979-05:00 INFO crash_reporter[2166]: libminijail[2166]: mount /dev/log -> /dev/log type ''
2018-06-12T10:00:04.021255-05:00 INFO crash_reporter[2166]: Processing kernel warning: normal collection
2018-06-12T10:00:04.068118-05:00 INFO crash_reporter[2166]: Stored kernel warning into /var/spool/crash/kernel_warning.20180612.100004.0.kcrash
2018-06-12T10:00:07.938680-05:00 ERR chrome[952]: [952:952:0612/100007.938607:INFO:remote_commands_invalidator.cc(32)] Initialize RemoteCommandsInvalidator.
2018-06-12T10:00:08.000666-05:00 ERR chrome[952]: [952:952:0612/100008.000596:INFO:remote_commands_invalidator.cc(45)] Shutdown RemoteCommandsInvalidator.
2018-06-12T10:00:08.000816-05:00 ERR chrome[952]: [952:952:0612/100008.000782:INFO:remote_commands_invalidator.cc(68)] Stopping RemoteCommandsInvalidator.


Is this related crbug.com/854781?

Comment 6 by ryutas@chromium.org, Jun 27 2018

Components: OS>Kernel
Owner: kotah@chromium.org
Assigning to myself for triage
#c5: shill process was running on cpu 0 when ChromeOS freezed. From stack trace:

2018-06-12T10:00:03.968098-05:00 WARNING kernel: [   16.827878] WARNING: CPU: 0 PID: 1094 at ../../../../../tmp/portage/sys-kernel/chromeos-kernel-4_4-4.4.127-r1484/work/chromeos-kernel-4_4-4.4.127/net/wireless/util.c:1143 cfg80211_calculate_bitrate+0xe0/0x195 [cfg80211]
2018-06-12T10:00:03.968103-05:00 WARNING kernel: [   16.827899] Modules linked in: ccm cmac rfcomm uinput iwlmvm snd_hda_codec_hdmi iwlwifi iwl7000_mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_soc_sst_baytrail_pcm snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_sst_byt_max98090_mach snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform ip6t_REJECT nf_reject_ipv6 snd_soc_max98090 snd_soc_sst_acpi snd_soc_sst_match zram fuse cfg80211 ip6table_filter btusb btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core joydev
2018-06-12T10:00:03.968105-05:00 WARNING kernel: [   16.827970] CPU: 0 PID: 1094 Comm: shill Not tainted 4.4.127-13890-g6c206f1711d4 #1
2018-06-12T10:00:03.968108-05:00 WARNING kernel: [   16.827973] Hardware name: GOOGLE Gnawty, BIOS Google_Gnawty.5216.239.123 04/23/2017
2018-06-12T10:00:03.968110-05:00 WARNING kernel: [   16.827977]  ffffffffc03ee46d caf0d7776f283b36 ffff88007256b748 ffffffffb66dd66e
2018-06-12T10:00:03.968113-05:00 WARNING kernel: [   16.827985]  ffff88007256b780 ffffffffb66dd623 caf0d7776f283b36 0000000000000000
2018-06-12T10:00:03.968115-05:00 WARNING kernel: [   16.827993]  0000000000000282 caf0d7776f283b36 0000000000000000 ffff88007256b7c0
2018-06-12T10:00:03.968118-05:00 WARNING kernel: [   16.828001] Call Trace:
2018-06-12T10:00:03.968120-05:00 WARNING kernel: [   16.828011]  [<ffffffffb66dd66e>] __dump_stack+0x19/0x1b
2018-06-12T10:00:03.968122-05:00 WARNING kernel: [   16.828016]  [<ffffffffb66dd623>] dump_stack+0x4f/0x81
2018-06-12T10:00:03.968124-05:00 WARNING kernel: [   16.828022]  [<ffffffffb646ce2c>] __warn+0xba/0xf1
2018-06-12T10:00:03.968127-05:00 WARNING kernel: [   16.828027]  [<ffffffffb646cf8a>] warn_slowpath_null+0x38/0x3d
2018-06-12T10:00:03.968129-05:00 WARNING kernel: [   16.828041]  [<ffffffffc03b08e1>] cfg80211_calculate_bitrate+0xe0/0x195 [cfg80211]
2018-06-12T10:00:03.968132-05:00 WARNING kernel: [   16.828056]  [<ffffffffc03bf1dd>] nl80211_put_sta_rate+0x31/0x13a [cfg80211]
2018-06-12T10:00:03.968134-05:00 WARNING kernel: [   16.828071]  [<ffffffffc03bc396>] nl80211_send_station+0x2bc/0x73b [cfg80211]
2018-06-12T10:00:03.968136-05:00 WARNING kernel: [   16.828077]  [<ffffffffb6584fdf>] ? ksize+0x15/0x8e
2018-06-12T10:00:03.968138-05:00 WARNING kernel: [   16.828092]  [<ffffffffc03c1800>] nl80211_get_station+0x162/0x1be [cfg80211]
2018-06-12T10:00:03.968141-05:00 WARNING kernel: [   16.828104]  [<ffffffffb6ab7ae3>] genl_rcv_msg+0x389/0x3ef
2018-06-12T10:00:03.968143-05:00 WARNING kernel: [   16.828109]  [<ffffffffb6ab775a>] ? genl_unbind+0x81/0x81
2018-06-12T10:00:03.968145-05:00 WARNING kernel: [   16.828113]  [<ffffffffb6ab466a>] netlink_rcv_skb+0x47/0x95
2018-06-12T10:00:03.968148-05:00 WARNING kernel: [   16.828118]  [<ffffffffb6ab7614>] genl_rcv+0x28/0x37
2018-06-12T10:00:03.968150-05:00 WARNING kernel: [   16.828123]  [<ffffffffb6ab3270>] netlink_unicast+0x146/0x1ae
2018-06-12T10:00:03.968152-05:00 WARNING kernel: [   16.828127]  [<ffffffffb6ab5a0a>] netlink_sendmsg+0x2ce/0x300
2018-06-12T10:00:03.968154-05:00 WARNING kernel: [   16.828133]  [<ffffffffb6b71fcf>] sock_sendmsg_nosec+0x18/0x25
2018-06-12T10:00:03.968156-05:00 WARNING kernel: [   16.828138]  [<ffffffffb6b72324>] SyS_sendto+0x114/0x180
2018-06-12T10:00:03.968159-05:00 WARNING kernel: [   16.828144]  [<ffffffffb646a207>] ? __do_page_fault+0x18a/0x404
2018-06-12T10:00:03.968161-05:00 WARNING kernel: [   16.828151]  [<ffffffffb6b9c7d3>] entry_SYSCALL_64_fastpath+0x27/0x9b
2018-06-12T10:00:03.968163-05:00 WARNING kernel: [   16.828155] ---[ end trace 71d380af5da01a64 ]---

This is crbug.com/838948, which is tracked in b/79542530. I will check other logs too.
Mergedinto: 838948
Status: Duplicate (was: Untriaged)
Reviewed all logs.

- a (L4): Same stack as #c8. crbug.com/838948
- b (L10): Messages log is filled with these messages:

2018-06-12T09:57:35.943488-05:00 ERR kernel: [  539.661059] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-28]
2018-06-12T09:57:35.943517-05:00 WARNING kernel: [  539.661068] ecryptfs_write_end: Error encrypting page (upper index [0x0000000000002286])

This could be  crbug.com/538233 . This device was on M61 when the issue occurred on 2018-06-12 10am, and then updated to M67 after reboot

- c (L12): crbug.com/838948
- d (L18): Same as L10. Same ecryptfs_encrypt_page kernel errors, device was on M61.
- e (L21): Same as L10. Same ecryptfs_encrypt_page kernel errors, device was on M61.

So in summary: Now that customer's devices are in M67, they should see ChromeOS freeze less frequently (because  crbug.com/538233  is fixed but crbug.com/838948 is not yet). We are still working on crbug.com/838948 with Intel at high priority. Duping this bug to crbug.com/838948.
It was reported to me that crbug.com/838948 has been fixed in the beta version 68. Is this correct? I don't have any testing results as of yet from our devices but will have my team go back and test on the beta channel to see if they experience similar lock ups as we seen before.
Further lockups have been seen after update to the v68 beta version on 7/27/2018. Logs and event timelines have been added to the case. Note we had not seen lockups on v61 during the school year with student accounts used daily on the devices.
7/27/2018 CDT
TD6 11:14 lockup after logging into a different account (test@morris54.org) than the one used to update (test@student.morris54.org) the chromebook. Keystroke Alt+VolUp+X did not work until the device unfroze and the keystroke caused a log out of the device.
TD5 11:42 lockup after logging into a different account (mschroeder@morris54.org) than the one used to update (test@student.morris54.org) the chromebook. Keystroke Alt+VolUp+X did not work until the device unfroze and the keystroke caused a log out of the device.
J16 1:04 Locked up after logging on to an account other than  the one used to update the device. Keystroke did not work until the device unfroze. 
TD6-20180730T161418Z-001.zip
1.2 MB Download
TD5-20180730T162522Z-001.zip
641 KB Download
J16-20180730T164101Z-001.zip
1.5 MB Download
7/27/2018 CDT
J22 2:14 Locked up after logging on to an account other than  the one used to update the device. Keystroke did not work until the device unfroze. 
J23 2:14 Locked up after logging on to an account other than  the one used to update the device. Keystroke did not work until the device unfroze. 
J24 2:14 Locked up after logging on to an account other than  the one used to update the device. Keystroke did not work until the device unfroze. 

J22-20180730T163456Z-001.zip
1.4 MB Download
J23-20180730T163731Z-001.zip
1.3 MB Download
J24-20180730T163930Z-001.zip
1.2 MB Download

Sign in to add a comment