Created attachment 113040 [details] dmesg for igt/gem_evict_everything/minor-hang ==System Environment== -------------------------- Regression: yes Non-working platforms: IVB ==kernel== -------------------------- drm-intel-nightly/8b4216f91c7bf8d3459cadf9480116220bd6545e(2015-02-02) ==Bug detailed description== ----------------------------- igt/gem_evict_everything/minor-hang spend more than 10 minute to run. And there is abnormal output in dmesg. dmesg -r|egrep "<[1-4]>"|grep drm <4>[ 2.330357] WARNING: CPU: 0 PID: 1041 at drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x131/0x26b [i915]() <4>[ 2.330360] Modules linked in: i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea <4>[ 2.330361] CPU: 0 PID: 1041 Comm: kworker/u8:7 Not tainted 3.19.0-rc6_dr -intel-nightly_8b4216_20150202+ #126 <4>[ 2.330459] [<ffffffffa00181a1>] ? drm_mode_set_config_internal+0xa1/0xd2 [drm] <4>[ 2.330462] [<ffffffffa0065282>] ? restore_fbdev_mode+0xa8/0xc3 [drm_kms_helper] <4>[ 2.330463] [<ffffffffa006659f>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x1f/0x56 [drm_kms_helper] <4>[ 2.330465] [<ffffffffa0066604>] ? drm_fb_helper_set_par+0x2e/0x33 [drm_kms_helper] <4>[ 2.330513] [<ffffffffa006685b>] ? drm_fb_helper_initial_config+0x252/0x2ef [drm_kms_helper] <4>[ 132.661779] WARNING: CPU: 3 PID: 1041 at drivers/gpu/drm/i915/i915_irq.c:2615 i915_handle_error+0x58/0x5bd [i915]() <4>[ 132.661872] snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support dm_mod ppdev snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm pcspkr i2c_i801 snd_timer lpc_ich snd mfd_core soundcore battery parport_pc parport wmi acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea <4>[ 132.662071] CPU: 3 PID: 1041 Comm: kworker/u8:7 Tainted: G W 3.19.0-rc6_drm-intel-nightly_8b4216_20150202+ #126 ==Reproduce steps== ---------------------------- 1. ./gem_evict_everything --run-subtest minor-hang
b8d24a06568368076ebd5a858a011699a97bfa42 is the first bad commit. commit b8d24a06568368076ebd5a858a011699a97bfa42 Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> AuthorDate: Wed Jan 28 17:03:14 2015 +0200 Commit: Daniel Vetter <daniel.vetter@ffwll.ch> CommitDate: Thu Jan 29 18:03:07 2015 +0100 drm/i915: Remove nested work in gpu error handling Now when we declare gpu errors only through our own dedicated hangcheck workqueue there is no need to have a separate workqueue for handling the resetting and waking up the clients as the deadlock concerns are no more. The only exception is i915_debugfs::i915_set_wedged, which triggers error handling through process context. However as this is only used through test harness it is responsibility for test harness not to introduce hangs through both debug interface and through hangcheck mechanism at the same time. Remove gpu_error.work and let the hangcheck work do the tasks it used to. v2: Add a big warning sign into i915_debugfs::i915_set_wedged (Chris) Cc: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
*** This bug has been marked as a duplicate of bug 88928 ***
*** This bug has been marked as a duplicate of bug 88933 ***
Closing as Duplicate of Verified+Fixed.
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.