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

Issue 599256 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

[Samus] external monitor connected via Apple-C sometimes does not come up

Project Member Reported by helenzhang@google.com, Mar 30 2016

Issue description

Google Chrome : 50.0.2661.57 (Official Build) beta (64-bit)
Platform : 7978.36.0 (Official Build) beta-channel

What steps will reproduce the problem?
(1) Sign in 
(2) plug in external monitor cable to Apple-C on DUT   
(3) Unplug external cable on Apple-C 
(4) Plug external cable on Apple-C 

What is the expected output? 
External display works always 

What do you see instead?
External monitor does not come up after step 2 or 4  

Sometimes 
- once it got stuck, need to reboot or hotplug several times to make it work again. 
- Apple-C does not have consistent performance 

Feedback report:
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lRFilter=1&lReportSearch=user:helenztest&lROrder=2&lReport=7733103619
 

Comment 1 by tbroch@chromium.org, Mar 31 2016

Likely related to similar issues seen in 3.18 kernel with tracking short pulse HPD IRQ correctly and monitoring sink count changes.

https://code.google.com/p/chrome-os-partner/issues/detail?id=48007

Once sorted out on 3.18 we can look at feasibility to backporting to other kernels. 
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 3 2016

Labels: Hotlist-Google
Components: OS>Kernel>Display
Components: -OS>Kernel>Graphics
Status: Archived (was: Untriaged)

Comment 6 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 13 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by tbroch@chromium.org, Apr 13 2018

Status: WontFix (was: Untriaged)
There were some changes around HPD for samus_pd.  In particular

1157f5fe9 samus_pd: Increase HPD IRQ pulse to 2msec.

which may benefit this report.  

Please retest & re-open if you're still seeing failures.
Status: Fixed (was: WontFix)
Let's mark it fixed so it gets verified.

Sign in to add a comment