==System Environment== -------------------------- Regression: not sure Non-working platforms: BYT(N2810 @ 2.00GHz) ==kernel== -------------------------- drm-intel-nightly/07d0c831d9207c937595f081c8fddbddbf53756f commit 07d0c831d9207c937595f081c8fddbddbf53756f Author: Jani Nikula <jani.nikula@intel.com> Date: Tue Dec 30 15:02:01 2014 +0200 drm-intel-nightly: 2014y-12m-30d-13h-01m-34s UTC integration manifest ==Bug detailed description== ----------------------------- It only happens on single machine. Test drm-intel-fixes, drm-intel-nightly and drm-intel-next-queued kernel, they all have this issue. Test on earlier kernel, it also has this issue. output: Interrupts masked dmesg: [ 117.519273] netpoll: netconsole: remote ethernet address 00:10:60:31:90:99 [ 117.519409] netpoll: netconsole: local IP 10.239.156.137 [ 117.519553] console [netcon0] enabled [ 117.519604] netconsole: network logging started [ 117.524861] console [netcon0] disabled [ 117.542277] netpoll: netconsole: remote port 6666 [ 117.542337] netpoll: netconsole: remote IPv4 address 10.239.156.112 [ 117.542419] netpoll: netconsole: remote ethernet address 00:10:60:31:90:99 [ 117.542520] netpoll: netconsole: local IP 10.239.156.137 [ 117.542654] console [netcon0] enabled [ 117.542707] netconsole: network logging started [ 130.948896] [drm:i915_error_state_write] Resetting error state [ 130.951557] [drm:i915_ring_test_irq_set] Masking interrupts on rings 0x0000000f [ 130.979957] gem_exec_blt: executing [ 130.980164] gem_exec_blt: starting subtest normal [ 130.980275] [drm:i915_gem_open] [ 134.999697] [drm] Fake missed irq on bsd ring [ 134.999882] [drm:i915_gem_open] [ 139.007468] [drm] Fake missed irq on blitter ring [ 139.155455] gem_exec_blt: starting subtest dumb-buf [ 139.155574] [drm:i915_gem_open] [ 139.248026] [drm:intel_crtc_set_config] [CRTC:19] [FB:46] #connectors=1 (x y) (0 0) [ 139.250939] [drm:intel_set_config_compute_mode_changes] computed changes for [CRTC:19], mode_changed=0, fb_changed=0 ==Reproduce steps== ---------------------------- 1. ./drv_missed_irq_hang
Dunno what this test is doing, but it doesn't hang: [root@jbarnes-byt tests]$ ./drv_missed_irq_hang Interrupts masked gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30877 Aborted $SOURCE_DIR/gem_exec_blt 16384 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30880 Aborted $SOURCE_DIR/gem_exec_blt 65536 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30882 Aborted $SOURCE_DIR/gem_exec_blt 262144 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30887 Aborted $SOURCE_DIR/gem_exec_blt 16384 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30889 Aborted $SOURCE_DIR/gem_exec_blt 65536 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30891 Aborted $SOURCE_DIR/gem_exec_blt 262144 Interrupts unmasked gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30896 Aborted $SOURCE_DIR/gem_exec_blt 16384 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30898 Aborted $SOURCE_DIR/gem_exec_blt 65536 gem_exec_blt: igt_core.c:443: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed. ./drv_missed_irq_hang: line 13: 30901 Aborted $SOURCE_DIR/gem_exec_blt 262144 Cleared missed interrupts Looks like gem_exec_blt needs fixes to be run under drv_missed_interrupt these days.
commit e8457edba6c41c4d44758e28adabf864be764c00 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Apr 2 20:14:07 2015 +0100 igt/gem_exec_blt: Prevent assertion failure when running as a test load gem_exec_blt is used by other scripts to provide a background load, for example by drv_missed_irq. This mode doesn't act like a normal test and igt complains bitterly about it. Let's just ignore igt here. References: https://bugs.freedesktop.org/show_bug.cgi?id=88041 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Verfied it on the latest nightly kernel(333cf6) and igt(e8457e).
Closing old verified.
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.