[Bug 111772] [CI][DRMTIP] igt@* - dmesg-warn - Delta way too big!

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=111772

Matt Roper <matthew.d.roper at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|not set                     |low
           Severity|not set                     |minor
                 CC|                            |matthew.d.roper at intel.com

--- Comment #17 from Matt Roper <matthew.d.roper at intel.com> ---
(In reply to Lakshmi from comment #11)
> (In reply to Matt Roper from comment #10)
> > All of the warnings here seem to arise following suspend-resume, which is a
> > known system clock issue on some platforms.  The warning message itself
> > suggests a rememdy:
> > 
> >     If you just came from a suspend/resume,
> >     please switch to the trace global clock:
> >       echo global > /sys/kernel/debug/tracing/trace_clock
> >     or add trace_clock=global to the kernel command line
> > 
> > This isn't related to the graphics driver and is a platform-specific quirk,
> > so we should probably take the warning's advice and update the boot command
> > line for fi-cml-s to include the "trace_clock=global" to avoid hitting this.
> 
> @Matt, How about Bug 111883? Above comment is valid for bug 111883 as well?
> 
> @Tomi, Need your help in fixing this bug.

Yes, thanks for pointing that one out.  It looks like the same platform clock
problem is present on that snb platform.  I can't verify for sure that that
machine doesn't already have the trace_clock option on the kernel command line
since the boot.txt link over there is broken, but assuming it doesn't we should
also add it to that machine.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191005/4cbc3c9e/attachment.html>