https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5449/fi-byt-squawks/igt@i915_selftest@live_contexts.html <4> [472.283986] ------------[ cut here ]------------ <4> [472.284062] Unclaimed read from register 0x2074 <4> [472.284216] WARNING: CPU: 0 PID: 153 at drivers/gpu/drm/i915/intel_uncore.c:1093 __unclaimed_reg_debug+0x40/0x50 [i915] <4> [472.284221] Modules linked in: i915(+) amdgpu chash gpu_sched ttm vgem snd_hda_codec_hdmi btusb coretemp btrtl btbcm crct10dif_pclmul btintel crc32_pclmul ghash_clmulni_intel bluetooth cdc_ether usbnet r8152 ecdh_generic mii snd_hda_codec snd_hwdep snd_hda_core snd_pcm prime_numbers lpc_ich [last unloaded: i915] <4> [472.284261] CPU: 0 PID: 153 Comm: kworker/0:2 Tainted: G U 5.0.0-rc2-CI-CI_DRM_5449+ #1 <4> [472.284266] Hardware name: GOOGLE Squawks/Squawks, BIOS MrChromebox 02/04/2018 <4> [472.284365] Workqueue: events_long i915_hangcheck_elapsed [i915] <4> [472.284465] RIP: 0010:__unclaimed_reg_debug+0x40/0x50 [i915] <4> [472.284472] Code: 74 05 5b 5d 41 5c c3 45 84 e4 48 c7 c0 b6 38 75 a0 48 c7 c6 ac 38 75 a0 48 0f 44 f0 89 ea 48 c7 c7 bf 38 75 a0 e8 a0 f9 a3 e0 <0f> 0b 83 2d 27 2c 1a 00 01 5b 5d 41 5c c3 66 90 41 56 41 55 41 89 <4> [472.284477] RSP: 0018:ffffc900009dfd00 EFLAGS: 00010086 <4> [472.284483] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 <4> [472.284488] RDX: 0000000000000007 RSI: ffffffff820cb6f9 RDI: 00000000ffffffff <4> [472.284492] RBP: 0000000000002074 R08: 0000000000000000 R09: 0000000000000001 <4> [472.284497] R10: ffffc900009dfcc8 R11: 0000000000000000 R12: 0000000000000001 <4> [472.284502] R13: 0000000000000001 R14: 00000000044089a8 R15: 0000000000000202 <4> [472.284507] FS: 0000000000000000(0000) GS:ffff888077800000(0000) knlGS:0000000000000000 <4> [472.284512] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [472.284517] CR2: 00007fd937ea55a0 CR3: 0000000072e54000 CR4: 00000000001006f0 <4> [472.284522] Call Trace: <4> [472.284627] fwtable_read32+0x1e8/0x250 [i915] <4> [472.284730] intel_engine_get_active_head+0xbe/0xd0 [i915] <4> [472.284833] i915_hangcheck_elapsed+0x17a/0x4d0 [i915] <4> [472.284853] ? lock_acquire+0xa6/0x1c0 <4> [472.284872] process_one_work+0x245/0x610 <4> [472.284890] worker_thread+0x37/0x380 <4> [472.284901] ? process_one_work+0x610/0x610 <4> [472.284907] kthread+0x119/0x130 <4> [472.284914] ? kthread_park+0x80/0x80 <4> [472.284926] ret_from_fork+0x3a/0x50 <4> [472.284949] irq event stamp: 2360500 <4> [472.284956] hardirqs last enabled at (2360499): [<ffffffff8197cb74>] _raw_spin_unlock_irq+0x24/0x50 <4> [472.284962] hardirqs last disabled at (2360500): [<ffffffff8197c9ad>] _raw_spin_lock_irqsave+0xd/0x50 <4> [472.284968] softirqs last enabled at (2360350): [<ffffffff81c0033a>] __do_softirq+0x33a/0x4b9 <4> [472.284976] softirqs last disabled at (2360343): [<ffffffff810b5081>] irq_exit+0xd1/0xe0 <4> [472.285074] WARNING: CPU: 0 PID: 153 at drivers/gpu/drm/i915/intel_uncore.c:1093 __unclaimed_reg_debug+0x40/0x50 [i915] <4> [472.285079] ---[ end trace 1cd981e094570460 ]---
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT: igt@i915_selftest@live_contexts - dmesg-warn - Unclaimed read from register 0x2074 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5449/fi-byt-squawks/igt@i915_selftest@live_contexts.html
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT: igt@runner@aborted - fail - Previous test: i915_selftest (live_contexts) - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5449/fi-byt-squawks/igt@runner@aborted.html
Something else dropped the forcewake and/or runtime pm. There is a runtime_pm_get just prior to that in the code.
Looking at http://gfx-ci.fi.intel.com/cibuglog-ng/ fdo#109387 is showing Never Seen with 0/197. Does this mean that we haven't seen this again? And if so, can we just close this? Sorry if I'm reading this wrong. Thank you! Don
(In reply to Don Hiatt from comment #4) > Looking at http://gfx-ci.fi.intel.com/cibuglog-ng/ fdo#109387 is showing > Never Seen with 0/197. > > Does this mean that we haven't seen this again? And if so, can we just close > this? > > Sorry if I'm reading this wrong. > > Thank you! > > Don This issue occurred only once CI_DRM_5449 (3 weeks, 6 days / 689 runs ago), but not seen later. Since this is a BAT failure, we keep monitor this issue. If this issue doesn't occur for the next 3 months we can close this issue, otherwise we need necessary justification to close this issue.
This bug has not occurred in over 3 months, closing as invalid.
The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore.
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.