Please add the log for this issue 

Is this only on Caroline?

this is not repod on Caroline-ndk-translation device.
Aued from 10192.0.0 => 10196.0.0

unable to generate the logs. please see attached screenshot.

Deleted: 20171211_161819.jpg 1.8 MB

	20171211_161819.jpg 1.8 MB View Download

I've been seeing this for at least a week.  Flashing a caroline test image to a thumbdrive and booting from the thumbdrive, it gets to the Chrome logo, freezes for a bit, and then maybe reboots.  No console-ramoops file shows up, and unfortunately I don't have a serial console on this unit.

I reported it to the sheriffs earlier, not sure what happened after that.

Bad:

dev-channel%2Fcaroline%2F10211.0.0%2FChromeOS-test-R65-10211.0.0-caroline.tar.xz
canary-channel%2Fcaroline%2F10191.0.0%2FChromeOS-test-R65-10191.0.0-caroline.tar.xz

Good:

beta-channel%2Fcaroline%2F10032.71.1%2FChromeOS-test-R63-10032.71.1-caroline.tar.xz
dev-channel%2Fcaroline%2F10172.0.0%2FChromeOS-test-R64-10172.0.0-caroline.tar.xz

My caroline is a DVT2.

If the unit gets stuck at this screen and does not reboot, I can obtain a shell on VT2 and poke around.  ui.LATEST is empty.  /var/log/messages shows segfaults:

2017-12-14T00:45:13.665698+00:00 WARNING crash_reporter[2310]: [user] Received crash notification for chrome[2217] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-12-14T00:45:13.696052+00:00 ERR shill[2283]: [ERROR:crypto_des_cbc.cc(107)] Unable to load key matter from /var/lib/whitelist/owner.key
2017-12-14T00:45:13.698962+00:00 ERR shill[2283]: [ERROR:crypto_des_cbc.cc(107)] Unable to load key matter from /var/lib/whitelist/owner.key
2017-12-14T00:45:13.745742+00:00 INFO session_manager[2159]: [INFO:child_exit_handler.cc(77)] Handling 2217 exit.
2017-12-14T00:45:13.745769+00:00 ERR session_manager[2159]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 11
2017-12-14T00:45:13.745795+00:00 INFO session_manager[2159]: [INFO:session_manager_service.cc(289)] Exiting process is chrome.
2017-12-14T00:45:13.745817+00:00 INFO session_manager[2159]: [INFO:browser_job.cc(159)] Terminating process group: Ensuring browser processes are gone.
2017-12-14T00:45:13.745838+00:00 INFO session_manager[2159]: [INFO:system_utils_impl.cc(93)] Sending 9 to -2217 as 1000
2017-12-14T00:45:13.768253+00:00 INFO session_manager[2159]: [INFO:browser_job.cc(150)] Running child /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=28.0.0.126 --ui-prioritize-in-gpu-process --use-gl=egl --edge-touch-filtering --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --system-developer-mode --login-profile=user --has-chromeos-keyboard --enable-touchview --has-internal-stylus --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --arc-availability=officially-supported --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --vmodule=*arc/*=1,tablet_power_button_controller=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,*night_light*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2


There was nothing in /var/spool/crash, maybe because the machine had not been opted into crash reporting yet.

Deleted: logs.tgz 85.8 KB

logs.tgz 85.8 KB Download

This is strange as we are passing auto tests, so the lab seems to be able to boot ok, does this only happen when booting from USB?

We can skip 65 dev on Caroline for now while this is investigated.

> does this only happen when booting from USB?

In my experience, building a new caroline image from ToT and deploying it via `cros flash ssh://...` would also trigger the bug.  I think that what usually happens is the Chromebook notices that the new image has failed to come up ~3 times, and it reverts back to the old OS image.

If this is Chrome dying whom would be the right person to dig into it?

Can you help triage Albert?

Usually this is a symptom of test image and the chrome binary you're trying to run being too far out of sync.

Folks who are in the best position to look into this have also turned into pumpkins already.

xiyuan@ can I get you to look into this once you're back in Jan?

The segfault happens on sandbox_ipc_thread for #7 log:

2017-12-14T00:45:13.639037+00:00 INFO kernel: [    8.651640] sandbox_ipc_thr[2285]: segfault at 5fb1c26911ab ip 00005fb1c26911ab sp 00007f0370477110 error 15 in chrome[5fb1c2691000+1000]

It is strange that the problem does not happen in lab and caroline bots are green. Let me grab 10196.0.0 caroline build and give it a try.

Today auto updated my caroline device from M64 => M65(10272.0.0) and didn't see this issue. 

Thanks for the update. Feel free to reopen if chrome crashes again. It would be interesting to see the full crash stack.