Issue metadata
Sign in to add a comment
|
Log spam from client_native_pixmap_dmabuf |
||||||||||||||||||||||
Issue descriptionVersion: 54.0.2837.0 OS: ChromeOS Panther Chrome log on my device has a lot of lines of the form: [16065:16257:0829/115912:ERROR:client_native_pixmap_dmabuf.cc(52)] Failed DMA_BUF_SYNC_END: Invalid argument These come in bursts, usually with 6-10 messages per second. Since these are logged as ERRORs, they presumably indicate something is actually wrong. Since they are logged very often they spam the log and make it harder to see whether others issues are causing problems. The DMA_BUF_SYNC_END log looks like issue 639165, which was marked P1 for M53.
,
Aug 30 2016
,
Sep 6 2016
this is P1 bug. anybody can take a look?
,
Sep 8 2016
device_status_collector is absolutely harmless, and not related to client_native_pixmap_dmabuf.
,
Sep 8 2016
Re #4: If it's absolutely harmless then why are we LOG(ERROR)ing it? What situation do the errors actually indicate is taking place?
,
Sep 26 2016
Anybody can pick this bug or resolve this bug appropriately? this is P1 bug but been stale for >2 weeks. thanks
,
Sep 28 2016
Dave do you have cycles to remove this?
,
Sep 28 2016
I'm ooo this week so I can't get to the bottom of these errors now but if we just want to stop spamming the log files with the messages in release builds then https://codereview.chromium.org/2382593002 will do that.
,
Oct 4 2016
,
Oct 6 2016
Dave, I believe that mtomasz@ comment was about device_status_collector logspam. I'd assume that DMA_BUF_SYNC_END: Invalid argument logging indicates that something is genuinely going wrong. Is there a better owner for this you can suggest?
,
Oct 6 2016
,
Oct 6 2016
Split the status collector logging out to 653593, since it is much more minor.
,
Oct 6 2016
ds, any idea why we're getting these DMA_BUF_SYNC_END errors? are these errors on intel devices a serious problem?
,
Oct 19 2016
Any update on this issue? We received similar reports from Chromebox for meetings users too, reporting system hang. Chrome version: 53.0.2785.144 ChromeOS version: 8530.93.0 ChromeOS Platform: ASUS Chromebox (Panther)
,
Oct 21 2016
,
Nov 7 2016
,
Nov 17 2016
Ping: This spam still repros at 56.0.2920.0. +gkihumba@ as M56 owner, in the hopes of getting this regression fixed. :)
,
Nov 17 2016
Dave can you drive this with intel?
,
Dec 5 2016
,
Dec 8 2016
,
Dec 8 2016
looks this is nothing to do with Platform>Apps>FileManager? removing the label for now.
,
Dec 8 2016
This should go away once https://chromium-review.googlesource.com/#/c/417519/ lands and just like with the oom errors it needs to be investigated before we can turn it back on.
,
Feb 23 2017
,
May 23 2017
Still seeing this logspam in M60 - most of the Chrome log is repeats of the message: [1:7:0523/085047.730875:ERROR:client_native_pixmap_dmabuf.cc(58)] Failed DMA_BUF_SYNC_END: Invalid argument Did we un-do the disabling in https://chromium-review.googlesource.com/#/c/417519/ recently, perhaps?
,
Aug 3
,
Aug 10
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by posciak@chromium.org
, Aug 30 2016Components: -OS>Kernel>Video OS>Kernel>Graphics