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

Issue 644796 link

Starred by 0 users
Status: Verified
Owner:
derat@chromium.org
Closed: Sep 2016
Cc:
dnicoara@chromium.org
steve...@chromium.org
mcasas@chromium.org
█ marc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Spammy DRM warnings at boot

Project Member Reported by derat@chromium.org, Sep 7 2016 
I'm seeing a few warning messages get logged by Chrome's DRM code when I boot a ToT lumpy image (ignore the VLOG(1)s; I'm including them for context):

[956:956:0907/112812:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s)
[956:956:0907/112812:WARNING:drm_util.cc(199)] Unable to get cursor width capability: Invalid argument
...
[956:956:0907/112812:VERBOSE1:drm_display_host_manager.cc(244)] Got display event ADD for /dev/dri/card0
[956:956:0907/112812:VERBOSE1:drm_display_host_manager.cc(244)] Got display event ADD for /dev/dri/card1
[956:1792:0907/112812:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card1 in 0 ms with 1 attempt(s)
...
[1811:1832:0907/112813:WARNING:drm_device_manager.cc(53)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[1811:1832:0907/112813:WARNING:drm_util.cc(199)] Unable to get cursor width capability: Invalid argument
...
[1811:1832:0907/112813:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=19 connector=24 origin=0,0 size=1280x800
[1811:1832:0907/112813:WARNING:drm_util.cc(199)] Unable to get cursor width capability: Invalid argument

Daniel, does "Unable to get cursor width capability: Invalid argument" indicate an actual problem? What about "Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1" -- do we expect to be able to initialize all devices?

If these are harmless and no one is working to prevent them, I'll switch them to VLOG(1).

Comment 1 by dnicoara@chromium.org, Sep 7 2016 

No for both questions (there is no problem). As background:
 - For cursor, a default size is defined in the calling code (64x64). On certain platforms (ie: link, samus) the cursor plane is larger, so we can take advantage of that.
 - For the DRM device warning, that is expected since VGEM is not a modesetting device, so it can't be used to display anything.

Comment 2 by derat@chromium.org, Sep 7 2016

Owner: derat@chromium.org
Status: Started (was: Untriaged)
Project Member

Comment 3 by bugdroid1@chromium.org, Sep 7 2016 

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

commit 38ca32d4cedc600a047bb34ff5f556ad491779fa
Author: derat <derat@chromium.org>
Date: Wed Sep 07 21:39:30 2016

ozone: Switch some DRM-related warnings to VLOG(1).

Avoid logging "Unable to get cursor width capability:
Invalid argument" and "Could not initialize DRM device"
warnings, as these are expected conditions on some systems.

BUG= 644796 

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

[modify] https://crrev.com/38ca32d4cedc600a047bb34ff5f556ad491779fa/ui/ozone/platform/drm/common/drm_util.cc
[modify] https://crrev.com/38ca32d4cedc600a047bb34ff5f556ad491779fa/ui/ozone/platform/drm/gpu/drm_device_manager.cc

Comment 4 by derat@chromium.org, Sep 7 2016

Status: Fixed (was: Started)

Comment 5 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 6 by helenzhang@google.com, Nov 9 2016

Status: Verified (was: Fixed)
Verified in 8970.0.0 / 56.0.2910.0
►

Sign in to add a comment