Issue 611583 link

Starred by 3 users

Issue metadata

Status:	Verified
Owner:	dnicoara@chromium.org
Closed:	Sep 2016
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
VerifyIn-55 VerifyIn-56 VerifyIn-57 VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Blocking:
issue 585504

ERROR: "Could not initialize DRM device"

Project Member Reported by steve...@chromium.org, May 12 2016

Issue description

We are seeing this error message on recent VMTest runs, e.g.

https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-tot-chromium-pfq-informational/builds/9163

Message:
[3071:3085:0512/141353:ERROR:drm_device_manager.cc(53)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1

This is causing confusion ERROR spam when tests fail for unrelated reasons.

Code:
https://code.google.com/p/chromium/codesearch#chromium/src/ui/ozone/platform/drm/gpu/drm_device_manager.cc&q=drm_device_manager.cc&sq=package:chromium&l=53

Introduced:
https://codereview.chromium.org/1100973002

Project Member

Comment 1 by bugdroid1@chromium.org, Sep 6 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d8bfddeec6daaf04c6d10b10282e9c9f5de09c6e

commit d8bfddeec6daaf04c6d10b10282e9c9f5de09c6e
Author: dnicoara <dnicoara@chromium.org>
Date: Tue Sep 06 23:10:27 2016

ozone-drm: Change log from error to warning

Log a warning rather than an error since some DRM devices (VGEM) are not
capable of modesetting, so we can't use them (so we can't really do
anything about it, but ignore the device).

BUG= 611583 
TEST=compiled

Review-Url: https://codereview.chromium.org/2312363002
Cr-Commit-Position: refs/heads/master@{#416755}

[modify] https://crrev.com/d8bfddeec6daaf04c6d10b10282e9c9f5de09c6e/ui/ozone/platform/drm/gpu/drm_device_manager.cc