From dgreid:

I've got a convoluted but reliable kernel hang on Eve that is
preceeded by a bunch of drm warnings.

I reproduce this by running our version of android-master on Eve (go/berthacare)

[   83.602454] EXT4-fs (loop6): warning: maximal mount count reached,
running e2fsck is recommended
[   83.603418] EXT4-fs (loop6): recovery complete
[   83.604381] EXT4-fs (loop6): mounted filesystem with ordered data
mode. Opts: (null)
[   83.693141] EXT4-fs (loop7): warning: maximal mount count reached,
running e2fsck is recommended
[   83.694096] EXT4-fs (loop7): recovery complete
[   83.695055] EXT4-fs (loop7): mounted filesystem with ordered data
mode. Opts: (null)
[   83.815612] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
[   83.821332] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
[   84.632536] binder: 4167:4167 ioctl 620a 0 returned -22
[   84.642938] BUG: sleeping function called from invalid context at
/mnt/host/source/src/third_party/kernel/v4.4/arch/x86/include/asm/uaccess.h:697
[   84.642945] in_atomic(): 1, irqs_disabled(): 0, pid: 4178, name:
configstore@1.1
[   84.642951] CPU: 3 PID: 4178 Comm: configstore@1.1 Tainted: G
 W       4.4.70 #3
[   84.642954] Hardware name: Google Eve/Eve, BIOS
Google_Eve.9584.18.0 06/26/2017
[   84.642958]  0000000000000286 00000000bb605f8f ffff88023a08fc80
ffffffffbb6d569a
[   84.642967]  0000000000001052 ffff88025b76d400 ffff88023a08fca0
ffffffffbb4cbde9
[   84.642974]  ffffffffbbdbe1b0 00000000000002b9 ffff88023a08fcc8
ffffffffbb4cbe8d
[   84.642981] Call Trace:
[   84.642991]  [<ffffffffbb6d569a>] dump_stack+0x4d/0x63
[   84.642997]  [<ffffffffbb4cbde9>] ___might_sleep+0x149/0x14e
[   84.643002]  [<ffffffffbb4cbe8d>] __might_sleep+0x9f/0xa6
[   84.643007]  [<ffffffffbb5826c7>] __might_fault+0x35/0x37
[   84.643013]  [<ffffffffbba1455b>] binder_thread_write+0x7f5/0xdff
[   84.643016]  [<ffffffffbb4cbce4>] ? ___might_sleep+0x44/0x14e
[   84.643019]  [<ffffffffbb4cbe8d>] ? __might_sleep+0x9f/0xa6
[   84.643024]  [<ffffffffbba14c06>]
binder_ioctl_write_read.constprop.47+0xa1/0x25b
[   84.643028]  [<ffffffffbba14f44>] binder_ioctl+0x184/0x423
[   84.643033]  [<ffffffffbb5e9368>] compat_SyS_ioctl+0x1d2/0x115c
[   84.643038]  [<ffffffffbb4b696e>] ? ptrace_notify+0x7b/0x7e
[   84.643042]  [<ffffffffbb401193>] ? ptrace_report_syscall.isra.9+0x31/0xa0
[   84.643045]  [<ffffffffbb401639>] ? syscall_trace_enter_phase2+0x106/0x11e
[   84.643049]  [<ffffffffbb40193c>] do_fast_syscall_32+0xaa/0xea
[   84.643054]  [<ffffffffbbb53a72>] sysenter_flags_fixed+0x8/0x12
[   85.709088] BUG: sleeping function called from invalid context at
/mnt/host/source/src/third_party/kernel/v4.4/arch/x86/include/asm/uaccess.h:697
[   85.709094] in_atomic(): 1, irqs_disabled(): 0, pid: 4178, name:
configstore@1.1
[   85.709099] CPU: 3 PID: 4178 Comm: configstore@1.1 Tainted: G
 W       4.4.70 #3
[   85.709101] Hardware name: Google Eve/Eve, BIOS
Google_Eve.9584.18.0 06/26/2017
[   85.709104]  0000000000000286 00000000bb605f8f ffff88023a08fc80
ffffffffbb6d569a
[   85.709111]  0000000000001052 ffff88025b76d400 ffff88023a08fca0
ffffffffbb4cbde9
[   85.709117]  ffffffffbbdbe1b0 00000000000002b9 ffff88023a08fcc8
ffffffffbb4cbe8d
[   85.709123] Call Trace:
[   85.709131]  [<ffffffffbb6d569a>] dump_stack+0x4d/0x63
[   85.709136]  [<ffffffffbb4cbde9>] ___might_sleep+0x149/0x14e
[   85.709139]  [<ffffffffbb4cbe8d>] __might_sleep+0x9f/0xa6
[   85.709144]  [<ffffffffbb5826c7>] __might_fault+0x35/0x37
[   85.709149]  [<ffffffffbba1455b>] binder_thread_write+0x7f5/0xdff
[   85.709154]  [<ffffffffbbb5161b>] ? _raw_spin_unlock_irq+0xe/0x21
[   85.709158]  [<ffffffffbb4cbce4>] ? ___might_sleep+0x44/0x14e
[   85.709161]  [<ffffffffbb4cbe8d>] ? __might_sleep+0x9f/0xa6
[   85.709165]  [<ffffffffbba14c06>]
binder_ioctl_write_read.constprop.47+0xa1/0x25b
[   85.709169]  [<ffffffffbba14f44>] binder_ioctl+0x184/0x423
[   85.709174]  [<ffffffffbb5e9368>] compat_SyS_ioctl+0x1d2/0x115c
[   85.709178]  [<ffffffffbb4b696e>] ? ptrace_notify+0x7b/0x7e
[   85.709183]  [<ffffffffbb401193>] ? ptrace_report_syscall.isra.9+0x31/0xa0
[   85.709186]  [<ffffffffbb401639>] ? syscall_trace_enter_phase2+0x106/0x11e