Bug 105599

Summary:	[CI] igt@gem_mocs_settings@mocs-rc6-bsd1 - incomplete - Softdog
Product:	DRI	Reporter:	Marta Löfstedt <marta.lofstedt>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
See Also:	https://bugs.freedesktop.org/show_bug.cgi?id=105600
Whiteboard:	ReadyForDev
i915 platform:	SKL	i915 features:	GEM/Other

Description Marta Löfstedt 2018-03-19 09:58:01 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-gvtdvm/igt@gem_mocs_settings@mocs-rc6-bsd1.html

run.log:
running: igt/gem_mocs_settings/mocs-rc6-bsd1

[00/97]  |                                  
owatch: TIMEOUT!
owatch: timeout for /dev/watchdog0 set to 10 (requested 10)
FATAL: command execution failed

This is all i dmesg:
<5>[   27.256437] owatch: Using watchdog device /dev/watchdog0
<5>[   27.258053] owatch: Watchdog /dev/watchdog0 is a software watchdog
<5>[   27.259669] owatch: timeout for /dev/watchdog0 set to 410 (requested 410)
<6>[   32.059979] perf: interrupt took too long (4262 > 4177), lowering kernel.perf_event_max_sample_rate to 46000
<7>[   38.796783] [IGT] gem_mocs_settings: executing
<6>[   41.130613] perf: interrupt took too long (5357 > 5327), lowering kernel.perf_event_max_sample_rate to 37000
<6>[   60.345342] perf: interrupt took too long (6724 > 6696), lowering kernel.perf_event_max_sample_rate to 29000
<6>[   91.627257] perf: interrupt took too long (8422 > 8405), lowering kernel.perf_event_max_sample_rate to 23000
<6>[  160.808578] perf: interrupt took too long (10576 > 10527), lowering kernel.perf_event_max_sample_rate to 18000

Comment 1 Marta Löfstedt 2018-03-20 06:29:28 UTC

First test softdog on fi-skl-gvtdvm appear to be a pattern I collect all occurrences in the same bug.

*** This bug has been marked as a duplicate of bug 105600 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.