Bug 109476 - [CI][BAT] igt@i915_selftest@live_requests - dmesg-fail - Missed interrupts on engines
Summary: [CI][BAT] igt@i915_selftest@live_requests - dmesg-fail - Missed interrupts on...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: highest normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-28 11:50 UTC by Martin Peres
Modified: 2019-03-06 18:44 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: GEM/Other


Attachments

Description Martin Peres 2019-01-28 11:50:16 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5490/shard-apl1/igt@i915_selftest@live_requests.html

<6> [962.425910] i915: Performing live selftests with st_random_seed=0x6b25751a st_timeout=1000
<7> [962.426155] [drm:intel_power_well_enable [i915]] enabling always-on
<7> [962.426344] [drm:intel_power_well_enable [i915]] enabling DC off
<7> [962.426767] [drm:gen9_set_dc_state [i915]] Setting DC state from 01 to 00
<6> [963.436839] Request latencies on rcs0: 1 = 5543759ns, 373 = 80591ns
<6> [964.460185] Request latencies on bcs0: 1 = 79607ns, 383 = 68962ns
<6> [965.462533] Request latencies on vcs0: 1 = 71978ns, 433 = 61056ns
<6> [966.483306] Request latencies on vecs0: 1 = 91005ns, 439 = 60644ns
<7> [966.488342] missed_breadcrumb vcs0 missed breadcrumb at intel_breadcrumbs_hangcheck+0x51/0x70 [i915]
<7> [966.488413] missed_breadcrumb 	current seqno 4015, last 4016, hangcheck 4014 [64 ms]
<7> [966.488417] missed_breadcrumb 	Reset count: 0 (global 0)
<7> [966.488422] missed_breadcrumb 	Requests:
<7> [966.488445] missed_breadcrumb 		first  4016! [50f:4015] prio=-4094 @ 2ms: (null)
<7> [966.488450] missed_breadcrumb 		last   4016! [50f:4015] prio=-4094 @ 2ms: (null)
<7> [966.488503] missed_breadcrumb 	RING_START: 0x00007000
<7> [966.488510] missed_breadcrumb 	RING_HEAD:  0x00000018
<7> [966.488517] missed_breadcrumb 	RING_TAIL:  0x00000018
<7> [966.488526] missed_breadcrumb 	RING_CTL:   0x00000000
<7> [966.488534] missed_breadcrumb 	RING_MODE:  0x00000200 [idle]
<7> [966.488540] missed_breadcrumb 	RING_IMR: fffffefe
<7> [966.488551] missed_breadcrumb 	ACTHD:  0x00000000_18200018
<7> [966.488562] missed_breadcrumb 	BBADDR: 0x00000000_00003004
<7> [966.488573] missed_breadcrumb 	DMA_FADDR: 0x00000000_00007018
<7> [966.488579] missed_breadcrumb 	IPEIR: 0x00000000
<7> [966.488585] missed_breadcrumb 	IPEHR: 0x04000001
<7> [966.488594] missed_breadcrumb 	Execlist status: 0x00000302 00000000
<7> [966.488601] missed_breadcrumb 	Execlist CSB read 1, write 3 [mmio:3], tasklet queued? yes (enabled)
<7> [966.488611] missed_breadcrumb 	Execlist CSB[2]: 0x00000001 [mmio:0x00000001], context: 0 [mmio:0]
<7> [966.488620] missed_breadcrumb 	Execlist CSB[3]: 0x00000018 [mmio:0x00000018], context: 0 [mmio:0]
<7> [966.488627] missed_breadcrumb 		ELSP[0] count=1, ring->start=00007000, rq: 4016! [50f:4015] prio=-4094 @ 2ms: signaled
<7> [966.489155] missed_breadcrumb 		ELSP[1] idle
<7> [966.489160] missed_breadcrumb 		HW active? 0x1
<7> [966.489214] missed_breadcrumb 		E 4016! [50f:4015] prio=-4094 @ 3ms: signaled
<7> [966.489280] missed_breadcrumb 		Queue priority: -2147483648
<7> [966.489319] missed_breadcrumb 	i915/signal:2 [8853:R] waiting for 4016
<7> [966.489380] missed_breadcrumb HWSP:
<7> [966.489387] missed_breadcrumb [0000] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [966.489390] missed_breadcrumb *
<7> [966.489396] missed_breadcrumb [0040] 00000001 00000000 00000018 00000000 00000001 00000000 00000018 00000000
<7> [966.489401] missed_breadcrumb [0060] 00000001 00000000 00000018 00000000 00000000 00000000 00000000 00000003
<7> [966.489406] missed_breadcrumb [0080] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [966.489409] missed_breadcrumb *
<7> [966.489414] missed_breadcrumb [00c0] 00004016 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [966.489419] missed_breadcrumb [00e0] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [966.489422] missed_breadcrumb *
<7> [966.489455] missed_breadcrumb Idle? yes
<3> [966.490102] live_sequential_engines(): Missed interrupts on engines 4
<3> [966.491589] i915/i915_request_live_selftests: live_sequential_engines failed with error -5
<7> [966.491795] [drm:intel_power_well_enable [i915]] enabling power well 2
<7> [966.491892] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [966.492989] [drm:intel_power_well_enable [i915]] enabling dpio-common-bc
<4> [966.712195] i915: probe of 0000:00:02.0 failed with error -5
<6> [966.826434] [IGT] i915_selftest: exiting, ret=99
Comment 1 CI Bug Log 2019-01-28 11:51:53 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* APL: igt@i915_selftest@live_requests - dmesg-fail - Missed interrupts on engines
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5490/shard-apl1/igt@i915_selftest@live_requests.html
Comment 2 Chris Wilson 2019-01-28 11:57:39 UTC
Weird. I'll pretend I never saw this as hopefully missed-irq will be gutted very soon.
Comment 3 Chris Wilson 2019-01-28 12:11:47 UTC
Fwiw, it does appear to be a false positive. Request was queued less than 2ms ago, and the signaler is R -- so has been woken.
Comment 4 Chris Wilson 2019-01-30 09:25:01 UTC
If you remove the check, it can't fail any more... We fundamentally reworked how fences are signaled, and threw this out as dead code.
Comment 5 Martin Peres 2019-03-06 18:44:48 UTC
(In reply to Chris Wilson from comment #4)
> If you remove the check, it can't fail any more... We fundamentally reworked
> how fences are signaled, and threw this out as dead code.

Thanks! Closing!
Comment 6 CI Bug Log 2019-03-06 18:44:58 UTC
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.