This is the #1 bug for the stable release we're already pushing for Eve
12.62%	1367	

We bumped up the priority as this needs to be resolved by the next stable.

2018-12-28T12:11:35.359310-08:00 INFO session_manager[1354]: [INFO:system_utils_impl.cc(94)] Sending 15 to 1370 as 1000
2018-12-28T12:11:35.573705-08:00 INFO kernel: [45828.150776] binder: release 3053:1417 transaction 696222 in, still active
2018-12-28T12:11:35.573719-08:00 INFO kernel: [45828.150783] binder: send failed reply for transaction 696222, target dead
2018-12-28T12:11:35.573721-08:00 INFO kernel: [45828.150788] binder: release 3053:3203 transaction 697524 in, still active
2018-12-28T12:11:35.573722-08:00 INFO kernel: [45828.150790] binder: send failed reply for transaction 697524, target dead
2018-12-28T12:11:35.573724-08:00 INFO kernel: [45828.150795] binder: release 3053:4710 transaction 702918 in, still active
2018-12-28T12:11:35.573725-08:00 INFO kernel: [45828.150798] binder: send failed reply for transaction 702918 to 5044:5074
2018-12-28T12:11:35.573726-08:00 INFO kernel: [45828.150801] binder: release 3053:4799 transaction 695971 in, still active
2018-12-28T12:11:35.573727-08:00 INFO kernel: [45828.150804] binder: send failed reply for transaction 695971, target dead
2018-12-28T12:11:35.573728-08:00 INFO kernel: [45828.150813] binder: undelivered death notification, 00000000f47acf80
2018-12-28T12:11:35.573729-08:00 INFO kernel: [45828.150816] binder: undelivered death notification, 00000000f50875c0
2018-12-28T12:11:35.573730-08:00 INFO kernel: [45828.150819] binder: undelivered death notification, 00000000f4990dc0
2018-12-28T12:11:35.959971-08:00 INFO chrome[1370]: [1370:1370:1228/121135.959882:INFO:remote_commands_invalidator.cc(45)] Shutdown RemoteCommandsInvalidator.
2018-12-28T12:11:35.960095-08:00 INFO chrome[1370]: [1370:1370:1228/121135.960061:INFO:remote_commands_invalidator.cc(68)] Stopping RemoteCommandsInvalidator.
2018-12-28T12:11:35.960184-08:00 INFO chrome[1370]: [1370:1370:1228/121135.960155:INFO:remote_commands_invalidator.cc(167)] Unregister RemoteCommandsInvalidator.
2018-12-28T12:11:36.332378-08:00 INFO chrome[1370]: [1370:1370:1228/121136.332314:INFO:remote_commands_invalidator.cc(45)] Shutdown RemoteCommandsInvalidator.
2018-12-28T12:11:36.332435-08:00 INFO chrome[1370]: [1370:1370:1228/121136.332410:INFO:remote_commands_invalidator.cc(68)] Stopping RemoteCommandsInvalidator.
2018-12-28T12:11:36.332472-08:00 INFO chrome[1370]: [1370:1370:1228/121136.332449:INFO:remote_commands_invalidator.cc(167)] Unregister RemoteCommandsInvalidator.
2018-12-28T12:11:36.407922-08:00 ERR chapsd[1231]: Attribute does not exist: 297
2018-12-28T12:11:36.565777-08:00 ERR chapsd[1231]: message repeated 5 times: [ Attribute does not exist: 297]
2018-12-28T12:11:37.423411-08:00 INFO session_manager[1354]: [INFO:session_manager_service.cc(504)] SessionManagerService quitting run loop
2018-12-28T12:11:37.439400-08:00 INFO session_manager[1354]: [INFO:android_oci_wrapper.cc(269)] Cleaning up container 2358
2018-12-28T12:11:37.454411-08:00 INFO session_manager[1354]: [INFO:session_manager_impl.cc(1783)] Android Container with pid 2358 stopped
2018-12-28T12:11:37.456897-08:00 WARNING kernel: [45830.033889] audit_printk_skb: 3 callbacks suppressed
2018-12-28T12:11:37.456906-08:00 NOTICE kernel: [45830.033894] audit: type=1400 audit(1546027897.455:875): avc: granted { execute } for pid=10586 comm="init" name="dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.456908-08:00 NOTICE kernel: [45830.034073] audit: type=1400 audit(1546027897.455:876): avc: granted { execute } for pid=10586 comm="sh" path="/bin/dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.458688-08:00 NOTICE kernel: [45830.035629] audit: type=1400 audit(1546027897.457:877): avc: granted { execute } for pid=10587 comm="init" name="dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.458696-08:00 NOTICE kernel: [45830.035759] audit: type=1400 audit(1546027897.457:878): avc: granted { execute } for pid=10587 comm="sh" path="/bin/dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.459680-08:00 WARNING kernel: [45830.036379] init: arc-kmsg-logger main process (2348) killed by TERM signal
2018-12-28T12:11:37.459687-08:00 NOTICE kernel: [45830.037077] audit: type=1400 audit(1546027897.458:879): avc: granted { execute } for pid=10588 comm="init" name="dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.459688-08:00 NOTICE kernel: [45830.037204] audit: type=1400 audit(1546027897.458:880): avc: granted { execute } for pid=10588 comm="sh" path="/bin/dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.464688-08:00 WARNING kernel: [45830.041308] init: arc-removable-media main process (3064) killed by TERM signal
2018-12-28T12:11:37.464701-08:00 NOTICE kernel: [45830.041664] audit: type=1400 audit(1546027897.463:881): avc: granted { execute } for pid=10598 comm="init" name="dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.464702-08:00 NOTICE kernel: [45830.041859] audit: type=1400 audit(1546027897.463:882): avc: granted { execute } for pid=10598 comm="sh" path="/bin/dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.475680-08:00 NOTICE kernel: [45830.053013] audit: type=1400 audit(1546027897.474:883): avc: granted { execute } for pid=10605 comm="init" name="dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.475691-08:00 NOTICE kernel: [45830.053145] audit: type=1400 audit(1546027897.474:884): avc: granted { execute } for pid=10605 comm="sh" path="/bin/dash" dev="dm-0" ino=131160 scontext=u:r:cros_init:s0 tcontext=u:object_r:sh_exec:s0 tclass=file
2018-12-28T12:11:37.479684-08:00 WARNING kernel: [45830.056840] init: arc-sdcard main process (2899) killed by TERM signal
2018-12-28T12:11:37.498744-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /run/arc/shared_mounts/cache: No such file or directory
2018-12-28T12:11:37.498784-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /run/arc/shared_mounts/data: No such file or directory
2018-12-28T12:11:37.498806-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(383)] Failed to stat /run/arc/shared_mounts/demo_apps: No such file or directory
2018-12-28T12:11:37.530868-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /run/arc/shared_mounts: Invalid argument
2018-12-28T12:11:37.541899-08:00 INFO minijail0[2901]: libminijail[2901]: child process 2910 exited with status 254
2018-12-28T12:11:37.558948-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /run/arc/debugfs/tracing: Invalid argument
2018-12-28T12:11:37.559119-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /proc/sys/fs/binfmt_misc: Invalid argument
2018-12-28T12:11:37.559311-08:00 ERR arc-lifetime[10586]: [ERROR:arc_setup_util.cc(374)] Failed to lazy-umount /opt/google/containers/android/rootfs/root/system/lib/arm: Invalid argument
2018-12-28T12:11:37.598418-08:00 INFO session_manager[1354]: [INFO:session_manager_impl.cc(846)] HandleLockScreenDismissed() method called.
2018-12-28T12:11:37.598478-08:00 INFO session_manager[1354]: [INFO:session_manager_service.cc(221)] SessionManagerService exiting
2018-12-28T12:11:37.604361-08:00 NOTICE usbguard-wrapper[10629]: Unlocking USB.
2018-12-28T12:11:37.610854-08:00 WARNING minijail0[2621]: libminijail[2621]: child process 2645 received signal 15
2018-12-28T12:11:37.611681-08:00 WARNING kernel: [45830.189038] init: bluetoothlog main process (2621) terminated with status 143
EOF

The arc-lifetime errors should be benign.

Can you elaborate on #5?  These are appearing in crash reporting at high frequency, which create false-positives for those of us performing analysis.  Can these be suppressed or logged in a different way?

It is my impression that if the bluetooth log size exceeds a certain amount, the bluetoothlog daemon might crash. I am not sure whether this issue still exists. Qiyu, could you please help take a look?

These are still coming in if you check the day chart per the link Dan included in #1:

https://crash.corp.google.com/browse?q=product_name%3D%27ChromeOS%27+AND+product.Version%3D%2711151.61.0%27+AND+stable_signature%3D%2747e28778-exit143-bluetoothlog%27

Adding 'eve' to the summary since we're only seeing this on eve, as well as calling out the Chrome OS version since I don't want to confuse this as an issue potentially impacting M71-STABLE-CHROMEOS-1

b/116256960

Re C#11: the issue https://b.corp.google.com/issues/116256960#comment21 was closed out because the crash number was not significant. If this is not the case for now, may need to take a closer look. Thanks.