[Leon] Entering docked mode causes kcrash |
|||||||
Issue descriptionCHROME VERSION: 64.0.3280.5 dev CHROMEOS_FIRMWARE_VERSION: Google_Leon.4389.61.46 CHROMEOS_RELEASE_VERSION: 10176.3.0 What steps will reproduce the problem? (1) Plug in external display (2) Close lid to enter docked mode (3) Observe device try to enter docked mode, screen goes blank and kcrash occurs Repro 3/5 attempts What is the expected result? Closing the device lid should enter docked mode What happens instead? Kcrash happens instead *Notes - I've found that if I can't repro on the 1st time entering docked mode, entering and exiting docked mode several more times will cause the crash to occur. - If the device is left in docked mode after the first kcrash occurs, it will enter a crash loop after it tries to reboot.
,
Dec 6 2017
,
Dec 6 2017
In addition to the kcrash, both the internal and external displays show a lot of graphical distortion when entering and exiting docked mode (see screenshots uploaded to the link in #1). From the kcrash log: <5>[ 111.217313] general protection fault: 0000 [#1] SMP <0>[ 111.219751] gsmi: Log Shutdown Reason 0x03 <5>[ 111.219784] Modules linked in: snd_usb_audio snd_usbmidi_lib rfcomm cmac uinput i2c_dev zram(C) zsmalloc(C) memconsole snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc fuse nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter snd_seq_midi ip6_tables snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer ath9k_btcoex ath9k_common_btcoex ath9k_hw_btcoex ath mac80211 cfg80211 ath3k btusb btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_core joydev hid_plantronics <5>[ 111.220231] CPU 0 <5>[ 111.220254] Pid: 1254, comm: chrome Tainted: G WC 3.8.11 #1 <5>[ 111.220288] RIP: 0010:[<ffffffffb6cad7aa>] [<ffffffffb6cad7aa>] list_move_tail+0x8/0x26 <5>[ 111.220352] RSP: 0018:ffff880064587d50 EFLAGS: 00010282 <5>[ 111.220375] RAX: dead000000200200 RBX: ffff88005ade3c00 RCX: 00000000000011ce <5>[ 111.220409] RDX: dead000000100100 RSI: ffff8800756aa5b0 RDI: ffff88005ade3cc8 <5>[ 111.220441] RBP: ffff880064587d68 R08: 0000000000000010 R09: ffffffffb6caed00 <5>[ 111.220473] R10: ffff880064587d50 R11: 0000000000000246 R12: ffff8800756a9ac0 <5>[ 111.220500] R13: 00000000000011cd R14: ffff8800756a9ad0 R15: ffff880073bd9060 <5>[ 111.220533] FS: 00007f948d2ae780(0000) GS:ffff880100200000(0000) knlGS:0000000000000000 <5>[ 111.220568] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <5>[ 111.220593] CR2: 00007f9486065000 CR3: 000000006461e000 CR4: 00000000000407f0 <5>[ 111.220624] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <5>[ 111.220655] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <5>[ 111.220690] Process chrome (pid: 1254, threadinfo ffff880064586000, task ffff880070a88000) <5>[ 111.220723] Stack: <5>[ 111.220739] ffff880064587d68 ffffffffb6cade08 ffff8800756a99e8 ffff880064587db0 <5>[ 111.220787] ffffffffb6caed2d ffff880064587d88 ffff88003f7d3a80 ffff88005ade2800 <5>[ 111.220839] 0000000000000000 ffff88010004f000 ffff880064587e08 ffff880064587e08 <5>[ 111.220889] Call Trace: <5>[ 111.220916] [<ffffffffb6cade08>] ? i915_gem_object_move_to_inactive+0x3e/0xb1 <5>[ 111.220952] [<ffffffffb6caed2d>] i915_gem_retire_requests_ring+0x159/0x181 <5>[ 111.220993] [<ffffffffb6cb1af1>] i915_gem_busy_ioctl+0x6d/0xbb <5>[ 111.221023] [<ffffffffb6cb1a84>] ? i915_gem_unpin_ioctl+0xa9/0xa9 <5>[ 111.221063] [<ffffffffb6c833d3>] drm_ioctl+0x2fb/0x3e5 <5>[ 111.221113] [<ffffffffb6a918e6>] ? __secure_computing+0xd2/0x2b1 <5>[ 111.221160] [<ffffffffb6b049e7>] do_vfs_ioctl+0x35e/0x420 <5>[ 111.221204] [<ffffffffb6ed0e37>] ? _raw_spin_unlock_irq+0xe/0x11 <5>[ 111.221254] [<ffffffffb6a5c2bf>] ? finish_task_switch+0x63/0xa1 <5>[ 111.221286] [<ffffffffb6b04b16>] sys_ioctl+0x6d/0xa5 <5>[ 111.221313] [<ffffffffb6ed1d79>] tracesys+0xd0/0xd5 <5>[ 111.221337] Code: df 48 8b 7d c8 e8 ad 12 22 00 48 89 df e8 a3 2c 03 00 48 83 c4 30 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 8b 47 08 48 8b 17 55 <48> 89 42 08 48 89 10 48 89 e5 48 8b 46 08 48 89 7e 08 48 89 37 <1>[ 111.221715] RIP [<ffffffffb6cad7aa>] list_move_tail+0x8/0x26 <5>[ 111.221752] RSP <ffff880064587d50> <4>[ 111.221842] ---[ end trace 7c6c6bb5ef6d9f5e ]--- I've also tested on R64-10176.5.0 and the kcrash happens less often but the distortion happens very often.
,
Dec 6 2017
Matt, can you post the crashes URLs?
,
Dec 6 2017
Here is the link to the 6 or so crashes that were uploaded: https://crash.corp.google.com/browse?q=ClientID%3D%2791096f8c139245e28d366d759d3ebbe4%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=72a74e24061e32a5&index=4#0
,
Dec 6 2017
just tried on falco, repro 0/5.
,
Jan 4 2018
Can we identify an owner and bump in priority? Tagged as a stable blocker, but really with an edge workflow and board limited?
,
Jan 20 2018
This crash seems related to one already fixed here issue 783208 +Brian to confirm
,
Jan 20 2018
Hrm, what? The crash linked doesn't seem related to this bug's $subject. It's also on 10176.5.0, which is an earlier build than the M64 build where bug 783208 was fixed. Please try 10176.18.0 or newer for fixing the cups/upstart bug. But anyway, the graphics issues are likely from crash 2 of 7, like this one: https://crash.corp.google.com/browse?q=ClientID%3D%2791096f8c139245e28d366d759d3ebbe4%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=862cddaddeab67dd&index=1#0 This ain't my area of expertise...
,
Jan 20 2018
Actually, I'd probably suggest the reporter retest, if possible, given marcheu@ couldn't repro, and you're also reporting other crashes that are already fixed :)
,
Jan 22 2018
Issue appears to be resolved as I'm unable to repro on R64-10176.58.0 after entering and exiting Docked mode ~20 times. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by matthewjoseph@chromium.org
, Dec 5 2017