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

Issue 821480 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[veyron-mickey] Primary display remains black after resume from idle with two displays connected

Project Member Reported by matthewjoseph@chromium.org, Mar 13 2018

Issue description

CHROMEOS_RELEASE_BUILD_TYPE=Official Build 
CHROMEOS_RELEASE_CHROME_MILESTONE=66 
CHROMEOS_RELEASE_DESCRIPTION=10452.9.0 (Official Build) dev-channel veyron_mickey 


What steps will reproduce the problem?
(1) Recover mickey device with R-66 10452.9.0
(2) Connect the devices listed in 'Setup' below
(3) Allow the device to turn off the displays due to inactivity
(4) Wake the device
(5) Observe

What is the expected result?
Device should wake and render content on the connected displays

What happens instead?
Primary display is black and the secondary display is active 

Notes*
When this issue occurs, the below is also observed:
1) The mouse pointer tracking is extremely erratic
2) Device cannot be recovered via unplugging / re-plugging chromebit from primary, only a reboot will resolve the issue
3) After roughly 5 minutes, the device will completely hang, nothing responds, and disconnecting power is the only option to get out of this state
4) Device is extremely hot to the touch

Setup*
1) veyron-mickey plugged into Lenovo ThinkVision X1 4K display (primary)
2) STRONGR R USB-C Dock (Model: DS-UG39DK8W) via USB Type-A to mickey's only USB port with the following attached:
    a) Acer USB keyboard
    b) USB Mouse
    c) HP 24" ZR24W display connected via HDMI (Secondary)




 
dmesg shows this after the issue occurs:

[  +0.000020] evdi: [D] evdi_painter_mode_changed_notify:488 pixel format 875713112
[  +0.009838] evdi: [D] evdi_painter_crtc_state_notify:468 (dev=2) Notifying crtc state: 0
[  +0.059544] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.236323] evdi: [D] evdi_painter_mode_changed_notify:487 (dev=2) Notifying mode changed: 1920x1200@60; bpp 32; 
[  +0.000025] evdi: [D] evdi_painter_mode_changed_notify:488 pixel format 875713112
[  +0.000035] evdi: [D] evdi_painter_crtc_state_notify:468 (dev=2) Notifying crtc state: 0
[ +11.206012] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.152047] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.136920] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.000309] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.020783] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.068079] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.000396] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.058146] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.020796] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.007452] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.011525] rockchip-drm display-subsystem.4: Failed to lookup GEM object
[  +0.172179] rockchip-drm display-subsystem.4: Failed to lookup GEM object

From powerd logs:
[0313/092542:INFO:activity_logger.cc(20)] User activity stopped; last reported 20 sec ago
[0313/093222:INFO:state_controller.cc(89)] Dimming screen after 7m
[0313/093222:INFO:display_power_setter.cc(67)] Asking DisplayService to dim the display in software
[0313/093252:INFO:state_controller.cc(89)] Turning screen off after 7m30s
[0313/093252:INFO:display_power_setter.cc(81)] Asking DisplayService to turn all displays off
[0313/093252:INFO:daemon.cc(1419)] Chrome is using normal display mode
[0313/093308:INFO:daemon.cc(1419)] Chrome is using normal display mode
[0313/093530:INFO:daemon.cc(1541)] Update operation is UPDATE_STATUS_CHECKING_FOR_UPDATE
[0313/093530:INFO:daemon.cc(1541)] Update operation is UPDATE_STATUS_IDLE
[0313/094051:INFO:activity_logger.cc(20)] User activity reported
[0313/094051:INFO:state_controller.cc(96)] Undimming screen
[0313/094051:INFO:display_power_setter.cc(67)] Asking DisplayService to undim the display in software
[0313/094051:INFO:state_controller.cc(96)] Turning screen on
[0313/094051:INFO:display_power_setter.cc(81)] Asking DisplayService to turn all displays on
[0313/094052:INFO:daemon.cc(1419)] Chrome is using normal display mode
[0313/094054:INFO:daemon.cc(1419)] Chrome is using normal display mode
[0313/094057:INFO:daemon.cc(1419)] Chrome is using normal display mode
[0313/094145:INFO:daemon.cc(1419)] Chrome is using normal display mode

Comment 3 by ka...@chromium.org, Mar 13 2018

Matt, can you try same setup on other veyron board like jerry or speedey? Same outcome?
This does not happen on Minnie or Speedy with the same setup
Labels: -Pri-1 Pri-2
Owner: marc...@chromium.org
Status: Assigned (was: Untriaged)
marcheu@ can you please take a look or triage?
Cc: displaylink@chromium.org
Owner: ----
Owner: marc...@chromium.org
[777:777:0313/081945.608694:VERBOSE1:user_session_manager.cc(551)] Starting user session.
[847:888:0313/082002.544269:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082002.591234:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/082002.592465:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
[1:16:0313/082017.875530:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
[847:888:0313/082723.867556:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082723.867842:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082723.868983:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=0x0
[847:888:0313/082723.890162:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=0x0
[847:888:0313/082739.593503:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082739.593791:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082739.594833:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=0x0
[847:888:0313/082739.595321:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=0x0
[847:888:0313/082927.930170:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082927.930598:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082927.932501:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/082928.017147:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
[847:888:0313/082930.635793:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082930.636757:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200
[847:888:0313/082932.818871:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/082932.820103:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/082932.905911:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
[847:888:0313/082932.971959:ERROR:crtc_controller.cc(168)] drmModeSetCursor: device /sys/devices/display-subsystem.4/drm/card1 crtc 21 handle 2 size 64x64: No such device or address (6)
[847:888:0313/083135.877328:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083135.877830:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083148.232612:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083148.232845:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083506.662147:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083506.666439:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200
[847:888:0313/083509.915104:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083509.916758:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/083510.099628:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
[847:888:0313/083535.126235:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083535.132542:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200
[847:888:0313/083621.688386:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083621.689977:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/083621.781495:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
[847:888:0313/083624.410902:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083624.412109:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,0 size=1920x1200
[847:888:0313/083626.590463:WARNING:screen_manager.cc(115)] Display controller (crtc=21) already present.
[847:888:0313/083626.592012:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/display-subsystem.4/drm/card1 crtc=21 connector=27 origin=0,0 size=1920x1200
[847:888:0313/083626.770924:VERBOSE1:drm_display.cc(105)] DRM configuring: device=/sys/devices/platform/evdi.0/drm/card2 crtc=21 connector=23 origin=0,1260 size=1920x1200
Status: pinged displaylink folks to look into it
I was able to reproduce issue using Chromebit, DL3 device, 4k Lenovo X1 monitor, 1200p monitor, CrOS version 66.0.3359.137 (Platform 10452.74.0). 

As well I was able to reproduce this issue when using UDL device.

The issue is only reproducible only when connecting Chromebit into 4k screen with secondary monitor which resolution match dropped resolution of 4k screen connected as primary and web browser is open. Primary monitor resolution is dropped because of the Mali-T764 GPU specification and desktop is stretched to whole screen.
In case of the Lenovo X1 monitor dropped resolution is 1200p. I have tested with another 4k monitor which dropped to 1080p and secondary 1080p monitor and issues reproduced.

Issue is not reproducible when using Lenovo X1 monitor with secondary 1080p monitor. 
Issue is not reproducible when using two 1200p or two 1080p monitors.
Issue is not reproducible when web browser is not open.

I have seen all issues mention under Notes section in this issue report. 

System information and metrics files are attached.
SystemInformation.mhtml
2.7 MB Download
metrics.mhtml
1.1 MB Download
I can reproduce this problem on ChromeOS as Kamil
described in comment 11. I've tried to reproduce it
on chromiumOS dev build to investigate it more.
I use '/usr/bin/set_short_powerd_timeouts' to make
screens go black faster (on ChromeOS it reproduces
isssue) but shortly after monitor turning black
OS crashed and restarts. There is OPS in kernel.

I had raised it separately as
https://bugs.chromium.org/p/chromium/issues/detail?id=845415

OPS is visible on veyron_minnie and veyron_mickey 
(those are the veyron_* devices I can test with).
The crash in the linked bug is related to WiFi, so disabling WiFi might help in preventing the oops. 

Removing the driver in the kernel config should certainly do the trick.
I was unable to reproduce it on Chromebit. 

 - Using stable ChromeOS channel (version 67.0.3396.99)
 - Using development ChromeOS channel (69.0.3497.21)
 - Using ToT of ChromiumOS (70.0.3505.0)

Last reproduction was on CrOS version 66.0.3359.137

Seems that this was already fixed. Maybe this was some flaw in userspace.


Status: Fixed (was: Assigned)
Per comment 14, presumed fixed.

Sign in to add a comment