<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [BAT] [GLK-DSI only] igt@gem_* - Failed assertion: !"GPU hung" - and its aftermath"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103514#c36">Comment # 36</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [BAT] [GLK-DSI only] igt@gem_* - Failed assertion: !"GPU hung" - and its aftermath"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103514">bug 103514</a>
from <span class="vcard"><a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> <span class="fn">Marta Löfstedt</span></a>
</span></b>
<pre>ON CI_DRM_3606:
First test with dmesg warn:
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3606/fi-glk-dsi/igt@gem_exec_flush@basic-batch-kernel-default-uc.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3606/fi-glk-dsi/igt@gem_exec_flush@basic-batch-kernel-default-uc.html</a>
then a lot of the following following igt@gem_exec_* tests are hit with
dmesg-warn.
It started here:
<4>[ 120.453872] WARNING: CPU: 3 PID: 0 at kernel/sched/core.c:3459
schedule_idle+0x2c/0x30
<4>[ 120.453878] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp i915
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec
snd_hwdep snd_hda_core snd_pcm mei_me r8169 mii mei prime_numbers i2c_hid
pinctrl_geminilake pinctrl_intel
<4>[ 120.453969] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G U
4.15.0-rc7-CI-CI_DRM_3606+ #1
<4>[ 120.453973] Hardware name: Intel Corp. Geminilake/GLK RVP2 LP4SD (07),
BIOS GELKRVPA.X64.0062.B30.1708222146 08/22/2017
<4>[ 120.453979] RIP: 0010:schedule_idle+0x2c/0x30
<4>[ 120.453983] RSP: 0018:ffffc900000d3ee8 EFLAGS: 00010286
<4>[ 120.453991] RAX: ee000000fe000000 RBX: 0000000000000003 RCX:
0000000000000001
<4>[ 120.453995] RDX: 0000000000000000 RSI: ffffffff820ab24f RDI:
ffffffff820b8d9d
<4>[ 120.453998] RBP: ffff88017a942740 R08: 0000000000000000 R09:
0000000000000001
<4>[ 120.454002] R10: 0000000000000000 R11: 0000000000000000 R12:
ffffffff8233caf0
<4>[ 120.454006] R13: ffff88017a942740 R14: ffff88017fdab550 R15:
ffffffff82293980
<4>[ 120.454010] FS: 0000000000000000(0000) GS:ffff88017fd80000(0000)
knlGS:0000000000000000
<4>[ 120.454014] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[ 120.454018] CR2: 00007f8fab777000 CR3: 000000016f6fc000 CR4:
0000000000340ee0
<4>[ 120.454022] Call Trace:
<4>[ 120.454031] do_idle+0x14b/0x1d0
<4>[ 120.454042] cpu_startup_entry+0x14/0x20
<4>[ 120.454049] start_secondary+0x129/0x160
<4>[ 120.454057] secondary_startup_64+0xa5/0xb0
<4>[ 120.454076] Code: 48 8b 04 25 80 4e 01 00 53 48 8b 40 08 48 85 c0 75 19
65 48 8b 1c 25 80 4e 01 00 31 ff e8 cd f0 ff ff 48 8b 03 a8 08 75 f2 5b c3 <0f>
ff eb e3 bf 01 00 00 00 e8 e6 e8 7e ff e8 a1 fb ff ff bf 01
Then there is ~170Mb of various WARNs from: kernel/locking/lockdep.c</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>