[Kevin/Bob] External monitor continuously flickering after changing resolution to 1440x900 |
|||||||||
Issue descriptionGoogle Chrome 66.0.3359.35 (Official Build) dev (32-bit) Revision 0 Platform 10452.14.0 (Official Build) dev-channel kevin Firmware Version Google_Kevin.8785.220.0 Customization ID SAMSUNG-KEVIN1\ Monitors Tested: HP Z27n, ASUS VE258 What steps will reproduce the problem? (1) Sign in to the device. (2) Plug external any monitor. (3) Change external monitor resolution to 1440x900 What is the expected result? Internal and external displays should not flicker. What happens instead? External monitor continuously flickering after changing resolution to 1440x900 display_Resolution.extended tests are failing with Result of 171315-1280x800: total 19598 wrong pixels (diff up to 121); Result of 171433-1440x900: total 25185 wrong pixels (diff up to 165) link:https://stainless.corp.google.com/search?view=matrix&row=build&col=test&first_date=2018-01-17&last_date=2018-03-16&suite=chameleon_hdmi_perbuild&board=kevin&exclude_cts=false&exclude_not_run=true&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
,
Mar 22 2018
,
Mar 22 2018
@sontis, did you try to test it with other Kevin device? I just want to be sure this is not a unit problem.
,
Mar 29 2018
Can you attach the output of modetest? It would tell us which pixel clock this is using.
,
Apr 17 2018
Sontis, can you update as per c#3?
,
Apr 17 2018
@tutankhamen, Able to reproduce this issue on all kevin devices ( Tested manually on 3 units and in lab 2 units.)
,
Apr 17 2018
Noticed same issue on Bob device.
,
Apr 17 2018
CCing rockchip people
,
Apr 18 2018
please cc zyw@rock-chips.com & nickey.yang@rock-chips.com, mark is no longer working at rockchip... we will try to repro it, and please help to share the logs at #1(we cannot access that link)
,
Apr 18 2018
The log in #1 is not really useful; it's basically a complicated way of saying "1440x900 doesn't work", which is confirmed by a manual test anyway... The interesting on is from #7 which shows the pixel clock/timings for the failing mode.
,
Apr 23 2018
sontis@ , can you also comment if this issue is seen with previous milestone releases?
,
Apr 24 2018
Able to reproduce this issue on M65_10323.75.0 build.
,
Apr 24 2018
Moving to M67 as per c#13, we can evaluate again for M66 if fix is available in time and safe to be merged
,
May 22 2018
Is this still an issue? Please provide updated status for M67.
,
May 24 2018
This is a board specific issue, not M67 regression and not receiving appropriate attention for a RBS issue. Removing the blocking tag, add it back with appropriate justification. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by sontis@chromium.org
, Mar 16 2018