Logs from the buddy unit: https://drive.google.com/a/google.com/file/d/0Bx12NVyIouI0Q1JoQkwwY3NSaW5zVEtnbW50ZDh5TWdoWlZV/view?usp=sharing

This is a corp device in debug mode.

The issue happened around and before 1:30pm pacific time.  I think it crashed more than 5 to 6 times today. Ignore restarts which happened after 3pm... those were probably triggered manually.

I see multiple stack traces which mention videobuf2-core which seem to coincide my crashes... and I see even on at 4:50 PM when my device was not in use (I was away)
 

This is unbearable. my devices is not very useful now. Crashes every 5 minutes. Should I go ahead and replace it ? 

Pawel - any ideas on this one?

Royans - is this one unit repeatedly failing or do we have multiple? Does it repro on other versions or only 56?

We have googler reports of instability, and at least one external report. The "warning" stack trace in logs seems consistent, but I'm not sure if its the root cause.

2 questions.

1. Is this Buddy running in CfM mode?
2. Is it running Thor?

It has both and crashes on both. (I can switch between the two modes)

I don't know if the below is benign or something meaningful.

2017-03-28T13:39:13.808721-07:00 WARNING kernel: [   26.607085] use VIDIOC_DECODER_CMD(V4L2_DEC_CMD_STOP) instead.
2017-03-28T13:39:13.808733-07:00 ERR kernel: [   26.607132] go2001 0000:03:00.0: go2001_dec_g_fmt_cap:1574 Frame info not available yet
2017-03-28T13:39:13.817722-07:00 ERR kernel: [   26.616118] go2001 0000:03:00.0: go2001_dec_g_fmt_cap:1574 Frame info not available yet
2017-03-28T13:39:13.861725-07:00 ERR kernel: [   26.660629] go2001 0000:03:00.0: go2001_dec_g_fmt_cap:1574 Frame info not available yet

These are benign warnings that are printed by the driver on Hangouts sessions simply b/c the decoder output format is not available yet. As such it is very unlikely that these would be related to the crash.

videobuf2 is the mechanism used to share frame buffers along devices on the video path without the need to copy them over to the next device. If you have stack trace prints from this part indicating errors, I would look there first

There are several Chrome crash logs.  I wonder if they're related or not.

yungleem@yung:~/Downloads/logs/buddy_royans/var/log/chrome/Crash Reports$ cat uploads.log 
1479841467,09caf5c300000000,Chrome
1480157631,5a01e80f00000000,Chrome
1480414121,e2f6be9f00000000,Chrome
1480630376,d98db95f00000000,Chrome
1480641251,d52a355f00000000,Chrome
1480846265,df2899df00000000,Chrome
1480972734,ee316c3f00000000,Chrome
1481367182,d642d47f00000000,Chrome
1483745266,3593285080000000,Chrome
1484869620,54c228e580000000,Chrome
1487038031,32f6bbd040000000,Chrome

Most of them expired so can't see but seems unrelated.  last 3 that I can view are bluez crash

Then it may be the same issue I reported before as well in  crbug.com/670462 . It had stopped happening for a while and now its happening again.

found the attached file in /dev/pstore/console-ramoops

Mentions "drmModeDirtyFB failed: Permission denied" which seems to be referenced in  crbug.com/646945 

Deleted: console-ramoops 92.1 KB

console-ramoops 92.1 KB View Download

I am not convinced the "frecon drmModeDirtyFB failed: Permission denied" is really causing the crash.  ramoops probably was generated because of the benign kernel warning earlier.  I don't see a real kernel stack trace that led to what seems to be a kernel crash.  This is a mystery to me.

From the crashes in #11 this appears to be crbug.com/683270.

Ah, sorry about that, I misread the above comments, issue 683270 was happening previously on your device. The newer reports seem not to be ready yet. I'll take a look once they are.

We have a customer with same issue with Buddy. 
After entering a Hangout, waiting for about 15 min, the device reboots and shows no crash IDs. 

Steps to reproduce the issue: 
-Enter a Hangout 
-Wait for a few minutes 
-Device reboots 

- Chrome OS version. 
56.0.2924.110 

2017-04-21T08:59:40.554076-05:00 WARNING kernel: [   27.107970] ------------[ cut here ]------------
2017-04-21T08:59:40.554087-05:00 WARNING kernel: [   27.107985] WARNING: CPU: 0 PID: 3289 at /mnt/host/source/src/third_party/kernel/v3.14/drivers/media/v4l2-core/videobuf2-core.c:1185 __fill_vb2_buffer+0x65/0x
29a()
2017-04-21T08:59:40.554092-05:00 NOTICE kernel: [   27.107999] Modules linked in: ccm rfcomm i2c_dev uinput iwlmvm memc_x86 snd_soc_sst_bdw_rt5650_mach x86_pkg_temp_thermal iwlwifi snd_hda_codec_hdmi iwl7000_mac80211 iio_trig_sysfs cfg80211 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_soc_sst_haswell_pcm snd_soc_sst_dsp snd_soc_sst_acpi snd_soc_rt5645 snd_soc_rl6231 fuse zram btusb btbcm btintel bluetooth ip6table_filter ip6_tables snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device uvcvideo videobuf2_vmalloc r8169 mii joydev cros_ec_accel kfifo_buf industrialio
2017-04-21T08:59:40.554093-05:00 NOTICE kernel: [   27.108092] CPU: 0 PID: 3289 Comm: V4L2DecoderThre Not tainted 3.14.0 #1
2017-04-21T08:59:40.554095-05:00 NOTICE kernel: [   27.108100] Hardware name: GOOGLE Buddy, BIOS Google_Buddy.6301.202.5 01/09/2016
2017-04-21T08:59:40.554096-05:00 NOTICE kernel: [   27.108108]  0000000000000000 000000002532deec ffff880073353bc8 ffffffffaca09c05
2017-04-21T08:59:40.554098-05:00 NOTICE kernel: [   27.108120]  0000000000000000 ffff880073353c00 ffffffffac45d88f ffffffffac8787a2
2017-04-21T08:59:40.554099-05:00 NOTICE kernel: [   27.108132]  ffff880073353dd0 ffff88006512c000 ffff88006512c058 0000000000000000
2017-04-21T08:59:40.554100-05:00 NOTICE kernel: [   27.108148] Call Trace:
2017-04-21T08:59:40.554103-05:00 NOTICE kernel: [   27.108155]  [<ffffffffaca09c05>] dump_stack+0x4d/0x6f
2017-04-21T08:59:40.554104-05:00 NOTICE kernel: [   27.108164]  [<ffffffffac45d88f>] warn_slowpath_common+0x7f/0x98
2017-04-21T08:59:40.554106-05:00 NOTICE kernel: [   27.108173]  [<ffffffffac8787a2>] ? __fill_vb2_buffer+0x65/0x29a
2017-04-21T08:59:40.554107-05:00 NOTICE kernel: [   27.108181]  [<ffffffffac45d9a1>] warn_slowpath_null+0x1a/0x1c
2017-04-21T08:59:40.554108-05:00 NOTICE kernel: [   27.108188]  [<ffffffffac8787a2>] __fill_vb2_buffer+0x65/0x29a
2017-04-21T08:59:40.554110-05:00 NOTICE kernel: [   27.108197]  [<ffffffffac87aa85>] __buf_prepare+0x14d/0x252
2017-04-21T08:59:40.554111-05:00 NOTICE kernel: [   27.108204]  [<ffffffffac87ad75>] vb2_internal_qbuf+0x91/0x217
2017-04-21T08:59:40.554112-05:00 NOTICE kernel: [   27.108212]  [<ffffffffac87af39>] vb2_qbuf+0x3e/0x45
2017-04-21T08:59:40.554114-05:00 NOTICE kernel: [   27.108221]  [<ffffffffac882091>] go2001_qbuf+0x7e/0x8a
2017-04-21T08:59:40.554115-05:00 NOTICE kernel: [   27.108229]  [<ffffffffac86ccf5>] v4l_qbuf+0x3b/0x44
2017-04-21T08:59:40.554117-05:00 NOTICE kernel: [   27.108237]  [<ffffffffac86e052>] __video_do_ioctl+0x1a7/0x28a
2017-04-21T08:59:40.554118-05:00 NOTICE kernel: [   27.108246]  [<ffffffffac86dc82>] video_usercopy+0x2ae/0x4c0
2017-04-21T08:59:40.554120-05:00 NOTICE kernel: [   27.108253]  [<ffffffffac86deab>] ? video_ioctl2+0x17/0x17
2017-04-21T08:59:40.554121-05:00 NOTICE kernel: [   27.108263]  [<ffffffffac433dc7>] ? __do_page_fault+0x2f2/0x386
2017-04-21T08:59:40.554122-05:00 NOTICE kernel: [   27.108271]  [<ffffffffac86dea9>] video_ioctl2+0x15/0x17
2017-04-21T08:59:40.554124-05:00 NOTICE kernel: [   27.108279]  [<ffffffffac86945c>] v4l2_ioctl+0x79/0x100
2017-04-21T08:59:40.554125-05:00 NOTICE kernel: [   27.108287]  [<ffffffffac556c84>] do_vfs_ioctl+0x355/0x416
2017-04-21T08:59:40.554127-05:00 NOTICE kernel: [   27.108296]  [<ffffffffac556d9c>] SyS_ioctl+0x57/0x79
2017-04-21T08:59:40.554128-05:00 NOTICE kernel: [   27.108304]  [<ffffffffaca125df>] tracesys+0xe7/0xec
2017-04-21T08:59:40.554129-05:00 WARNING kernel: [   27.108311] ---[ end trace 945c8e19760a5b1b ]---
2017-04-21T08:59:40.554130-05:00 WARNING kernel: [   27.108317] use of bytesused == 0 is deprecated and will be removed in the future,
2017-04-21T08:59:40.554132-05:00 WARNING kernel: [   27.108324] use VIDIOC_DECODER_CMD(V4L2_DEC_CMD_STOP) instead.
2017-04-21T08:59:40.554133-05:00 ERR kernel: [   27.108365] go2001 0000:03:00.0: go2001_dec_g_fmt_cap:1574 Frame info not available ye

Full log: https://drive.google.com/a/google.com/file/d/0By9xEkAUmm_cWWFnU0tiZzlTVVU/view?usp=sharing

The stack trace in #18 is an expected and benign kernel warning printed on boot, please see issue 702322 for context.

I was unfortunately not able to find any clues that would point to video stack issues in the logs from #18.

Royans - does this repro on later chromeos versions?

Feel free to "borrow" the buddy unit from my desk. It repro's on all versions recently released.

Considering that this is just happening on my unit, I'm really not sure whats going on. But I do believe Yung that this looks like a software issue because I can't reproduce the crash in a non-CFM mode.

Mats - what are next steps here? Who could look into this?

Recently on M59, I have not observed crashes on my buddy. 
Ran a session of 4+ hours on buddy with (59 / 9460.67.0 / 59.0.3071.113) and did not see buddy crashing.

dropping priority if it's not seen lately... not sure which post 56 changes would have improved this... any ideas?

Hi team,

I have a customer that is being affected with this issue. Unfortunately his CFM license expired and he is not willing to renew it until he can confirm this issue has been resolved. Now, I'm unable to complete any troubleshooting with him since the license has expired. Any thoughts about this? 

This bug is not actionable. We can reopen if we get examples of cases from the current chrome versions.