New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 678799 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[kevin] Device hanging after entering into mirror mode.

Project Member Reported by son...@google.com, Jan 5 2017

Issue description

Chrome Version: 9000.50.0
Device: Kevin
What steps will reproduce the problem?
(1) Sign in to the device.
(2) Connect external display.(HOHO/Ding-Dong)
(3) Switch to Mirror mode (Ctrl +F4)

What is the expected result?
Device should not hang.

What happens instead?
Device hanging after entering into mirror mode.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 2 by ka...@chromium.org, Jan 5 2017

Cc: osh...@chromium.org afakhry@chromium.org

Comment 3 by ka...@chromium.org, Jan 6 2017

Cc: bhthompson@chromium.org krishna...@chromium.org
Cc: diand...@chromium.org
Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
+dianders for recommendations of other folks whom may be interested in this.

I am not sure if we want to block the 56 beta on this, external display usage is likely not all that common even in the dogfooder fleet, it might block stable though. 
Cc: z...@rock-chips.com dbehr@chromium.org groeck@chromium.org seanpaul@chromium.org hoegsberg@chromium.org
Is this new and also Kevin-specific?

Sontis: you said "logs are taken after hard reboot".  How did you reboot?  Did you follow the standard steps to try to use Alt-Volup-X several times and then eventually Alt-Volup-R?  Quickly looking I don't see a console-ramoops which makes this bug much much less useful.

--


There are some useful bits from the log, though.  Here they are:

2017-01-05T22:55:30.861510+00:00 INFO kernel: [  225.128802] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn
2017-01-05T22:55:30.880273+00:00 INFO kernel: [  225.147992] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
2017-01-05T22:55:33.506255+00:00 INFO kernel: [  227.773985] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn
2017-01-05T22:55:34.594160+00:00 INFO kernel: [  228.861139] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
2017-01-05T22:55:41.668264+00:00 INFO kernel: [  235.935564] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn
2017-01-05T22:55:42.761138+00:00 INFO kernel: [  237.028140] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
2017-01-05T22:55:47.338240+00:00 WARNING kernel: [  241.605333] cros-ec-spi spi5.0: EC failed to respond in time
2017-01-05T22:55:47.338315+00:00 ERR kernel: [  241.605358] cros-ec-spi spi5.0: Command xfer error (err:-110)
2017-01-05T22:55:47.349145+00:00 ERR kernel: [  241.616861] cros-ec-spi spi5.0: Command xfer error (err:-11)
2017-01-05T22:55:47.349182+00:00 WARNING kernel: [  241.616880] iio iio:device3: Unable to read sensor data
2017-01-05T22:55:47.361131+00:00 ERR kernel: [  241.628382] cros-ec-spi spi5.0: Command xfer error (err:-11)
2017-01-05T22:55:47.361165+00:00 WARNING kernel: [  241.628399] iio iio:device1: Unable to read sensor data
2017-01-05T22:55:47.473133+00:00 ERR kernel: [  241.740340] cros-ec-spi spi5.0: Command xfer error (err:-11)
2017-01-05T22:55:47.473179+00:00 WARNING kernel: [  241.740366] iio iio:device1: Unable to read sensor data
2017-01-05T22:55:47.484184+00:00 ERR kernel: [  241.751867] cros-ec-spi spi5.0: Command xfer error (err:-11)
2017-01-05T22:55:47.484233+00:00 WARNING kernel: [  241.751890] iio iio:device3: Unable to read sensor data
2017-01-05T22:55:47.649176+00:00 ERR kernel: [  241.916996] cros-ec-keyb ff200000.spi:ec@0:keyboard-controller: Discarded incomplete key matrix event.
2017-01-05T22:55:59.948191+00:00 WARNING kernel: [  254.216101] frecon(576): Chrome did not release master. Trying again.
2017-01-05T22:56:00.451110+00:00 WARNING kernel: [  254.718187] frecon(576): Chrome did not release master. Trying again.
2017-01-05T22:56:00.953130+00:00 WARNING kernel: [  255.220234] frecon(576): Chrome did not release master. Trying again.
2017-01-05T22:56:01.455124+00:00 WARNING kernel: [  255.722338] frecon(576): Chrome did not release master. Trying again.
2017-01-05T22:56:01.957132+00:00 WARNING kernel: [  256.224381] frecon(576): Chrome did not release master. Frecon will steal master.
2017-01-05T22:56:02.260217+00:00 INFO kernel: [  256.527583] xhci-hcd xhci-hcd.1.auto: remove, state 4
2017-01-05T22:56:02.260264+00:00 INFO kernel: [  256.527631] usb usb6: USB disconnect, device number 1
2017-01-05T22:56:02.260275+00:00 INFO kernel: [  256.528243] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn

===

Seems like something wedged up the DP driver and that's possibly why the EC commands failed (???)

Comment 6 by son...@google.com, Jan 6 2017

I have rebooted the device using power button long press. 
Cc: h...@chromium.org
Are these UDL displays?

Comment 9 by h...@chromium.org, Jan 6 2017

It looks like DP. If the bug report mentions HOHO/Ding-Dong then it is not using UDL.
Owner: tbroch@chromium.org
Since the EC is wedged, could it be a problem with the plug detect fw? Todd do you know?
I've not seen anything like this to-date.

The plug-detect logic should be done if its successfully working in extended-mode and then switched to mirror.

Does mirror-mode work for other (apple, hp) non-UDL USBPD alt-mode dongles?
Still reproducible in Chrome OS 9000.58.0, 56.0.2924.58. 

It's not reproducible in Chell via Apple type-C. 
@12, kevin is tested via apple type-c multiple port adapter. 
See also http://crosbug.com/p/61875

...also note that the cros ec errors seem possibly unrelated and benign.  See http://crosbug.com/p/61910

Doing bisect in partner bug--see there for latest updates.

Comment 16 by son...@google.com, Jan 18 2017

Still able to reproduce this issue on build 9000.66.0
Owner: dbasehore@chromium.org
@16: that's expected since no fixes have gone in.

...all work discussing this is happening in the partner bug, which is owned by Derek.
This is marked as fixed in partner bug.
Status: Fixed (was: Untriaged)
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-56; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-56 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD Merge-Merged
It's been merged, too.

Comment 22 by son...@google.com, Jan 25 2017

Status: Verified (was: Fixed)
Verified on build 9202.4.0

Sign in to add a comment