Created attachment 101553 [details] dmesg ==System Environment== -------------------------- Regression: Yes. Good commit on -next-queued: 27b6c122512ca30399bb1b39cc42eda83901f304 Non-working platforms: BDW ==kernel== -------------------------- origin/drm-intel-nightly: 78f31a2d50183db12c0532eadcf486b9ebfa5f6d(fails) drm-intel-nightly: 2014y-06m-19d-21h-00m-17s integration manifest origin/drm-intel-next-queued: 9c33baa6b3bbb01c1a88dceba986b20e6642cf31(fails) drivers/i915: Fix unnoticed failure of init_ring_common() origin/drm-intel-fixes: 4a11e398b39b018c7aa3b22267cfdf3b7fae3625(works) drm/i915: cache hw power well enabled state ==Bug detailed description== ----------------------------- igt/kms_flip/vblank-vs-modeset-suspend causes "WARNING: CPU: 2 PID: 1051 at drivers/gpu/drm/i915/i915_irq.c:267 intel_gen6_powersave_work+0xa49/0xf1e [i915]()" Output: root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip --run-subtest vblank-vs-modeset-suspend IGT-Version: 1.7-gfedb9b6 (x86_64) (Linux: 3.15.0-rc8_drm-intel-nightly_78f31a_20140623+ x86_64) Using monotonic timestamps Beginning vblank-vs-modeset-suspend on crtc 6, connector 17 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sat Jan 13 21:11:13 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sat Jan 13 21:11:45 2001 vblank-vs-modeset-suspend on crtc 6, connector 17: PASSED Beginning vblank-vs-modeset-suspend on crtc 10, connector 17 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 Test assertion failure function wait_for_events, file kms_flip.c:1174: Last errno: 0, Success Failed assertion: ret > 0 select timed out or error (ret 0) Subtest vblank-vs-modeset-suspend: FAIL Dmesg shows: [ 216.231742] WARNING: CPU: 2 PID: 1051 at drivers/gpu/drm/i915/i915_irq.c:267 intel_gen6_powersave_work+0xa49/0xf1e [i915]() [ 216.231754] Modules linked in: dm_mod snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support ppdev pcspkr snd_hda_intel i2c_i801 snd_hda_controller snd_hda_codec snd_hwdep snd_pcm lpc_ich mfd_core snd_timer snd soundcore battery parport_pc parport ac acpi_cpufreq i915 video button drm_kms_helper drm [ 216.231757] CPU: 2 PID: 1051 Comm: kworker/2:1 Tainted: G W 3.15.0-rc8_drm-intel-nightly_78f31a_20140623+ #3826 [ 216.231766] Workqueue: events intel_gen6_powersave_work [i915] [ 216.231769] 0000000000000000 0000000000000009 ffffffff81772bca 0000000000000000 [ 216.231770] ffffffff81036e54 ffff880002f00000 ffffffffa0070883 ffff880002f00000 [ 216.231772] ffff880002f00000 ffff880145349000 ffff880002f00000 ffff880002f08238 [ 216.231773] Call Trace: [ 216.231778] [<ffffffff81772bca>] ? dump_stack+0x41/0x51 [ 216.231781] [<ffffffff81036e54>] ? warn_slowpath_common+0x78/0x90 [ 216.231790] [<ffffffffa0070883>] ? intel_gen6_powersave_work+0xa49/0xf1e [i915] [ 216.231798] [<ffffffffa0070883>] ? intel_gen6_powersave_work+0xa49/0xf1e [i915] [ 216.231801] [<ffffffff8104aade>] ? process_one_work+0x1e2/0x363 [ 216.231804] [<ffffffff8104ac77>] ? process_scheduled_works+0x18/0x25 [ 216.231807] [<ffffffff8104b39f>] ? worker_thread+0x1e1/0x2bc [ 216.231809] [<ffffffff8104b1be>] ? manage_workers.isra.23+0x1b5/0x1b5 [ 216.231811] [<ffffffff8104fb32>] ? kthread+0xc5/0xcd [ 216.231814] [<ffffffff8104fa6d>] ? kthread_freezable_should_stop+0x40/0x40 [ 216.231816] [<ffffffff8177e9bc>] ? ret_from_fork+0x7c/0xb0 [ 216.231818] [<ffffffff8104fa6d>] ? kthread_freezable_should_stop+0x40/0x40 ==Reproduce steps== ---------------------------- 1. ./kms_flip --run-subtest vblank-vs-modeset-suspend
If this is a regression, which one is the bad commit?
Created attachment 101644 [details] dmesg The similar failure found on SNB Dmesg shows: [ 38.969312] WARNING: CPU: 1 PID: 3819 at drivers/gpu/drm/i915/i915_irq.c:154 ironlake_disable_vblank+0x38/0x45 [i915]() [ 38.969320] Modules linked in: dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support ppdev dcdbas serio_raw pcspkr snd_hda_intel i2c_i801 snd_hda_controller snd_hda_codec snd_hwdep snd_pcm lpc_ich mfd_core snd_timer snd soundcore tpm_tis parport_pc parport tpm acpi_cpufreq i915 video button drm_kms_helper drm [ 38.969322] CPU: 1 PID: 3819 Comm: kworker/u16:12 Not tainted 3.16.0-rc2_drm-intel-nightly_794975_20140624+ #3850 [ 38.969322] Hardware name: Dell Inc. OptiPlex 990/0DXWW6, BIOS A02 02/26/2011 [ 38.969325] Workqueue: events_unbound async_run_entry_fn [ 38.969328] c1a92d70 c16f4ae7 00000000 c10311b0 f81d4e82 00000080 f4f20000 f4f23ac8 [ 38.969329] 00000002 c10311d0 00000009 00000000 f81d4e82 00000000 f4ca9000 00000000 [ 38.969331] 00000000 f80928ca 00000286 00000286 00000000 00000000 f4ca9000 f4ca90ec [ 38.969331] Call Trace: [ 38.969335] [<c16f4ae7>] ? dump_stack+0x3e/0x4e [ 38.969337] [<c10311b0>] ? warn_slowpath_common+0x65/0x78 [ 38.969345] [<f81d4e82>] ? ironlake_disable_vblank+0x38/0x45 [i915] [ 38.969346] [<c10311d0>] ? warn_slowpath_null+0xd/0x10 [ 38.969353] [<f81d4e82>] ? ironlake_disable_vblank+0x38/0x45 [i915] [ 38.969358] [<f80928ca>] ? vblank_disable_and_save+0x2b/0x156 [drm] [ 38.969367] [<f81ea26b>] ? intel_mark_fb_busy.part.34+0x29/0x52 [i915] [ 38.969371] [<f8092fac>] ? drm_vblank_off+0x27/0x10d [drm] [ 38.969381] [<f81f20c8>] ? ironlake_crtc_disable+0x30/0x6ef [i915] [ 38.969384] [<f80a217c>] ? drm_modeset_lock+0x2a/0x78 [drm] [ 38.969390] [<f81b320a>] ? i915_drm_freeze+0xae/0x12c [i915] [ 38.969392] [<c12f0ed3>] ? pci_pm_suspend+0x64/0xd3 [ 38.969393] [<c12f0e6f>] ? pci_pm_freeze+0x88/0x88 [ 38.969396] [<c136e102>] ? dpm_run_callback+0x43/0xa8 [ 38.969398] [<c136ec8f>] ? __device_suspend+0x186/0x1e3 [ 38.969399] [<c136ed00>] ? async_suspend+0x14/0x6b [ 38.969400] [<c1049da4>] ? async_run_entry_fn+0x56/0xfd [ 38.969402] [<c1041dc7>] ? process_one_work+0x191/0x2ea [ 38.969404] [<c104fac6>] ? try_to_wake_up+0x1e7/0x1f1 [ 38.969405] [<c10424a1>] ? worker_thread+0x29d/0x384 [ 38.969407] [<c1042204>] ? pool_mayday_timeout+0xb1/0xb1 [ 38.969408] [<c1045dbe>] ? kthread+0xa1/0xa6 [ 38.969410] [<c16f9921>] ? ret_from_kernel_thread+0x21/0x30 [ 38.969411] [<c1045d1d>] ? kthread_freezable_should_stop+0x3b/0x3b [ 38.969412] ---[ end trace bb5e729c616aa520 ]--- [ 38.969416] ------------[ cut here ]------------ [ 38.969424] WARNING: CPU: 1 PID: 3819 at drivers/gpu/drm/i915/i915_irq.c:423 intel_set_pch_fifo_underrun_reporting+0xc7/0x124 [i915]() [ 38.969431] Modules linked in: dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support ppdev dcdbas serio_raw pcspkr snd_hda_intel i2c_i801 snd_hda_controller snd_hda_codec snd_hwdep snd_pcm lpc_ich mfd_core snd_timer snd soundcore tpm_tis parport_pc parport tpm acpi_cpufreq i915 video button drm_kms_helper drm [ 38.969432] CPU: 1 PID: 3819 Comm: kworker/u16:12 Tainted: G W 3.16.0-rc2_drm-intel-nightly_794975_20140624+ #3850 [ 38.969433] Hardware name: Dell Inc. OptiPlex 990/0DXWW6, BIOS A02 02/26/2011 [ 38.969434] Workqueue: events_unbound async_run_entry_fn [ 38.969435] c1a92d70 c16f4ae7 00000000 c10311b0 f81d6835 f4f20000 00000000 00000001 [ 38.969437] f4ca9000 c10311d0 00000009 00000000 f81d6835 00000200 f4f23ac8 00000282 [ 38.969439] f4f20000 f4ca91e4 f582d000 f4ca91e0 f81f2112 f80a217c f582f000 f4ef4880 [ 38.969439] Call Trace: [ 38.969440] [<c16f4ae7>] ? dump_stack+0x3e/0x4e [ 38.969441] [<c10311b0>] ? warn_slowpath_common+0x65/0x78 [ 38.969448] [<f81d6835>] ? intel_set_pch_fifo_underrun_reporting+0xc7/0x124 [i915] [ 38.969449] [<c10311d0>] ? warn_slowpath_null+0xd/0x10 [ 38.969456] [<f81d6835>] ? intel_set_pch_fifo_underrun_reporting+0xc7/0x124 [i915] [ 38.969464] [<f81f2112>] ? ironlake_crtc_disable+0x7a/0x6ef [i915] [ 38.969467] [<f80a217c>] ? drm_modeset_lock+0x2a/0x78 [drm] [ 38.969473] [<f81b320a>] ? i915_drm_freeze+0xae/0x12c [i915] [ 38.969474] [<c12f0ed3>] ? pci_pm_suspend+0x64/0xd3 [ 38.969475] [<c12f0e6f>] ? pci_pm_freeze+0x88/0x88 [ 38.969476] [<c136e102>] ? dpm_run_callback+0x43/0xa8 [ 38.969477] [<c136ec8f>] ? __device_suspend+0x186/0x1e3 [ 38.969479] [<c136ed00>] ? async_suspend+0x14/0x6b [ 38.969480] [<c1049da4>] ? async_run_entry_fn+0x56/0xfd [ 38.969481] [<c1041dc7>] ? process_one_work+0x191/0x2ea [ 38.969482] [<c104fac6>] ? try_to_wake_up+0x1e7/0x1f1 [ 38.969484] [<c10424a1>] ? worker_thread+0x29d/0x384 [ 38.969485] [<c1042204>] ? pool_mayday_timeout+0xb1/0xb1 [ 38.969486] [<c1045dbe>] ? kthread+0xa1/0xa6 [ 38.969487] [<c16f9921>] ? ret_from_kernel_thread+0x21/0x30 [ 38.969488] [<c1045d1d>] ? kthread_freezable_should_stop+0x3b/0x3b [ 38.969489] ---[ end trace bb5e729c616aa521 ]---
Created attachment 101646 [details] [review] [PATCH v3] drm/i915: Leave interrupts enabled while disabling crtcs I think it must be caused by this: commit e11aa362308f5de467ce355a2a2471321b15a35c Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed Jun 18 09:52:55 2014 -0700 drm/i915: use runtime irq suspend/resume in freeze/thaw This patch should fix it. I've been trying to sneak it in for a long time already but so far it's not made it.
basing on latest testing (ac710a93740e609759fa75dacdc96f1dfc34b5c5), I found this Call Trace [ 2431.640836] ---[ end trace 214e6bb4fbf3a91a ]--- [ 2431.640849] ------------[ cut here ]------------ [ 2431.640863] WARNING: CPU: 5 PID: 4182 at drivers/gpu/drm/i915/i915_irq.c:423 ibx_display_interrupt_update+0x52/0x7d [i915]() [ 2431.640872] Modules linked in: dm_mod iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi dcdbas snd_hda_codec_realtek snd_hda_codec_generic serio_raw pcspkr i2c_i801 snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm ppdev snd_timer lpc_ich mfd_core snd soundcore tpm_tis parport_pc tpm parport acpi_cpufreq i915 video button drm_kms_helper drm [ 2431.640874] CPU: 5 PID: 4182 Comm: kworker/u16:24 Tainted: G W 3.15.0-rc8_drm-intel-testing_ac710a_20140621_+ #60 [ 2431.640874] Hardware name: Dell Inc. OptiPlex 990/0DXWW6, BIOS A02 02/26/2011 [ 2431.640876] Workqueue: events_unbound async_run_entry_fn [ 2431.640879] 00000046 00000000 f0a25d88 c176d89d 00000000 f0a25da0 c1032878 f81ffeb8 [ 2431.640881] c2c28000 00010000 00010000 f0a25db0 c10328a3 00000009 00000000 f0a25dc4 [ 2431.640883] f81ffeb8 c2c28000 00000000 f532c800 f0a25de8 f82015be 00000000 00000282 [ 2431.640884] Call Trace: [ 2431.640885] [<c176d89d>] dump_stack+0x41/0x52 [ 2431.640886] [<c1032878>] warn_slowpath_common+0x66/0x7d [ 2431.640898] [<f81ffeb8>] ? ibx_display_interrupt_update+0x52/0x7d [i915] [ 2431.640899] [<c10328a3>] warn_slowpath_null+0x14/0x18 [ 2431.640909] [<f81ffeb8>] ibx_display_interrupt_update+0x52/0x7d [i915] [ 2431.640920] [<f82015be>] intel_set_pch_fifo_underrun_reporting+0xd2/0x131 [i915] [ 2431.640934] [<f821e9de>] ironlake_crtc_disable+0x83/0x73b [i915] [ 2431.640944] [<f80a87c0>] ? drm_modeset_lock_all_crtcs+0x28/0x40 [drm] [ 2431.640952] [<f81db255>] i915_drm_freeze+0xbb/0x13d [i915] [ 2431.640961] [<f81db365>] i915_pm_suspend+0x42/0x47 [i915] [ 2431.640963] [<c132aae4>] pci_pm_suspend+0x75/0xe7 [ 2431.640964] [<c132aa6f>] ? pci_pm_freeze+0x94/0x94 [ 2431.640966] [<c13b0624>] dpm_run_callback+0x2a/0x5f [ 2431.640967] [<c13b1191>] __device_suspend+0x19f/0x212 [ 2431.640968] [<c13b1220>] async_suspend+0x1c/0x78 [ 2431.640970] [<c104f008>] async_run_entry_fn+0x5d/0xfd [ 2431.640972] [<c1045b95>] process_one_work+0x21c/0x3d4 [ 2431.640973] [<c1046283>] ? worker_thread+0x2d/0x285 [ 2431.640974] [<c10463f7>] worker_thread+0x1a1/0x285 [ 2431.640976] [<c1046256>] ? manage_workers.isra.23+0x199/0x199 [ 2431.640977] [<c104a952>] kthread+0xa4/0xa9 [ 2431.640978] [<c1773a0e>] ? _raw_spin_unlock_irq+0x27/0x2b [ 2431.640980] [<c1060000>] ? prio_changed_rt+0x20/0x4e [ 2431.640982] [<c1779d61>] ret_from_kernel_thread+0x21/0x30 [ 2431.640983] [<c104a8ae>] ? __init_kthread_worker+0x47/0x47 [ 2431.640984] ---[ end trace 214e6bb4fbf3a91b ]---
(In reply to comment #3) > Created attachment 101646 [details] [review] [review] > [PATCH v3] drm/i915: Leave interrupts enabled while disabling crtcs > > I think it must be caused by this: > > commit e11aa362308f5de467ce355a2a2471321b15a35c > Author: Jesse Barnes <jbarnes@virtuousgeek.org> > Date: Wed Jun 18 09:52:55 2014 -0700 > > drm/i915: use runtime irq suspend/resume in freeze/thaw > > > This patch should fix it. I've been trying to sneak it in for a long time > already but so far it's not made it. The CallTrace unable to reproduce on latest -nightly(1087d4bf01e79523898c6c31615bf0c369e0039a), but the test still failed. Output: [root@x-sgb3 tests]# ./kms_flip --run-subtest vblank-vs-modeset-suspend IGT-Version: 1.7-g7ef5372 (x86_64) (Linux: 3.16.0-rc2_drm-intel-nightly_1087d4_20140626+ x86_64) Using monotonic timestamps Test assertion failure function run_test, file kms_flip.c:1400: Last errno: 0, Success Failed assertion: modes Subtest vblank-vs-modeset-suspend: FAIL [root@x-sgb3 tests]# dmesg|grep Call [root@x-sgb3 tests]#
Can you still reproduce this with the current drm-intel-nightly tree?
Created attachment 102731 [details] dmesg (In reply to comment #6) > Can you still reproduce this with the current drm-intel-nightly tree? Dmesg fail unable to reproduce on latest nightly, but the test was failed. Should I report a new bug tho track this? Output: root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip --run-subtest vblank-vs-modeset-suspend IGT-Version: 1.7-ge74dd22 (x86_64) (Linux: 3.16.0-rc4_drm-intel-nightly_271bff_20140713+ x86_64) Using monotonic timestamps Beginning vblank-vs-modeset-suspend on crtc 7, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:07 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:12 2001 vblank-vs-modeset-suspend on crtc 7, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 11, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:17 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:23 2001 vblank-vs-modeset-suspend on crtc 11, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 15, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:28 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Sun Jan 7 20:25:33 2001 vblank-vs-modeset-suspend on crtc 15, connector 18: PASSED Subtest vblank-vs-modeset-suspend: SUCCESS Test assertion failure function igt_install_exit_handler, file igt_core.c:1084: Failed assertion: exit_handler_count < MAX_EXIT_HANDLERS kms_flip: igt_core.c:655: igt_fail: Assertion `!test_with_subtests || in_fixture' failed. Aborted root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $? 134 root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg|grep Call root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests#
Presumably fixed by one or both of these: commit 0e32b39ceed665bfa4a77a4bc307b6652b991632 Author: Dave Airlie <airlied@redhat.com> Date: Fri May 2 14:02:48 2014 +1000 drm/i915: add DP 1.2 MST support (v0.7) commit 09b64267c1f72f2670fcde9f11e5453ce365ca23 Author: Dave Airlie <airlied@redhat.com> Date: Wed Jul 23 14:25:24 2014 +1000 drm/i915: don't suspend gt until after we disable irqs and display (v2) The 'Failed assertion: exit_handler_count < MAX_EXIT_HANDLERS' would seem like a bug in igt, so please file a separate bug for it.
Verified on latest -nightly(ddbc288690cd888dd6f5629ccba9a2691a70b7b0) root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip --run-subtest vblank-vs-modeset-suspend IGT-Version: 1.7-gde1e877 (x86_64) (Linux: 3.16.0-rc6_drm-intel-nightly_ddbc28_20140801+ x86_64) Using monotonic timestamps Beginning vblank-vs-modeset-suspend on crtc 7, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:08:50 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:09:22 2001 vblank-vs-modeset-suspend on crtc 7, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 11, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:09:54 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:10:26 2001 vblank-vs-modeset-suspend on crtc 11, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 15, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:10:58 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Jan 26 00:11:30 2001 vblank-vs-modeset-suspend on crtc 15, connector 18: PASSED Subtest vblank-vs-modeset-suspend: SUCCESS root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg |grep WARNING [ 192.612451] WARNING: CPU: 1 PID: 4354 at drivers/pnp/pnpacpi/core.c:76 pnpacpi_set_resources+0x88/0x12e()
I tested it on the latest drm-intel-nightly(8980a4380b606860ba0165ed0156a64e79109677) commit 8980a4380b606860ba0165ed0156a64e79109677 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Mon Aug 4 17:24:12 2014 +0200 drm-intel-nightly: 2014y-08m-04d-17h-23m-47s integration manifest root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_flip --run- subtest vblank-vs-modeset-suspend IGT-Version: 1.7-gac31f19 (x86_64) (Linux: 3.16.0-rc6_drm-intel-nightly_8980a4_2 0140805+ x86_64) Using monotonic timestamps Beginning vblank-vs-modeset-suspend on crtc 7, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:15:15 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:15:47 2001 vblank-vs-modeset-suspend on crtc 7, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 11, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:16:19 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:16:51 2001 vblank-vs-modeset-suspend on crtc 11, connector 18: PASSED Beginning vblank-vs-modeset-suspend on crtc 15, connector 18 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:17:23 2001 .rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 30 03:17:55 2001 vblank-vs-modeset-suspend on crtc 15, connector 18: PASSED Subtest vblank-vs-modeset-suspend: SUCCESS root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg | grep WARNING [ 531.798589] WARNING: CPU: 3 PID: 4466 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]() [ 531.805432] WARNING: CPU: 2 PID: 4451 at drivers/pnp/pnpacpi/core.c:76 pnpacpi_s et_resources+0x88/0x12e() [ 533.704906] WARNING: CPU: 0 PID: 4461 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]() [ 535.626471] WARNING: CPU: 3 PID: 4471 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]() [ 537.556136] WARNING: CPU: 3 PID: 4477 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]() [ 539.501702] WARNING: CPU: 1 PID: 4465 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]() [ 541.446326] WARNING: CPU: 2 PID: 4501 at drivers/gpu/drm/i915/intel_uncore.c:528 hsw_unclaimed_reg_debug.isra.11+0x62/0x72 [i915]()
Closing (>2 years) old 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.