Bug 100045

Summary:	[BAT][ILK] igt@drv_module_reload@basic-reload ERROR PCH transcoder B FIFO underrun
Product:	DRI	Reporter:	Ander Conselvan de Oliveira <conselvan2>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:	ILK	i915 features:

Description Ander Conselvan de Oliveira 2017-03-03 10:18:54 UTC

[  527.851156] Setting dangerous option inject_load_failure - tainting kernel
[  528.047289] snd_hda_intel 0000:00:1b.0: can't derive routing for PCI INT A
[  528.047302] snd_hda_intel 0000:00:1b.0: PCI INT A: no GSI
[  528.049917] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun
[  530.865745] Setting dangerous option inject_load_failure - tainting kernel
[  530.900617] snd_hda_intel 0000:00:1b.0: can't derive routing for PCI INT A
[  530.900621] snd_hda_intel 0000:00:1b.0: PCI INT A: no GSI
[  531.566495] Setting dangerous option inject_load_failure - tainting kernel
[  531.611492] snd_hda_intel 0000:00:1b.0: can't derive routing for PCI INT A
[  531.611498] snd_hda_intel 0000:00:1b.0: PCI INT A: no GSI
[  532.314293] Setting dangerous option inject_load_failure - tainting kernel
[  532.379038] snd_hda_intel 0000:00:1b.0: can't derive routing for PCI INT A
[  532.379044] snd_hda_intel 0000:00:1b.0: PCI INT A: no GSI


https://intel-gfx-ci.01.org/CI/CI_DRM_2274/fi-ilk-650/igt@drv_module_reload@basic-reload.html

Also:

https://intel-gfx-ci.01.org/CI/Patchwork_4034/fi-ilk-650/igt@drv_module_reload@basic-reload-inject.html

https://intel-gfx-ci.01.org/CI/Patchwork_4034/fi-ilk-650/igt@drv_module_reload@basic-reload-final.html

Comment 1 Jani Saarinen 2017-03-28 07:03:17 UTC

Failure seen last time on 3rd of Mar 2017

Statistics for all of these 3: Failure rate 7/152 run(s) (4%-5%)
Whitelisting for CI

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.