New issue
Advanced search Search tips

Issue 772147 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Warning in ozone drm authentication logic

Project Member Reported by marc...@chromium.org, Oct 5 2017

Issue description

See in this log:
https://paste.googleplex.com/5440119469244416

On line 2, we successfully authenticate on card0.
On line 25, there is a drm event.
On line 30, we fail at authenticating on card0. But we are supposed to already be authenticated...

Daniele, is that a bug in the authentication logic? It seems like we are already authenticated and are trying again but failing? I can't quite make sense of that part.
 
Components: OS>Kernel>Graphics
Cc: posciak@chromium.org jkardatzke@chromium.org
What build is this? CC'ing Jeff and Pawel in case it's related to any recent DRM changes. 
It's possible there is a bug, that logic was refactored in https://codereview.chromium.org/1661783002/

I'm not too familiar with that part of Ozone, but looking at DrmDisplayHostManager::ProcessEvent it seems that we reopen the device if we get an "add" event and we can't find the device in the manager.

How do I reproduce that?
Status: Assigned (was: Untriaged)

Sign in to add a comment