[Bug 93440] New: [BYT,BSW] RPM wakelock ref not held during HW access (intel_pre_plane_update->intel_set_memory_cxsr)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 18 07:10:00 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=93440

            Bug ID: 93440
           Summary: [BYT,BSW] RPM wakelock ref not held during HW access
                    (intel_pre_plane_update->intel_set_memory_cxsr)
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: imre.deak at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

The WARN below started to appear after adding stricter RPM wakeref assert
checks. The testcases that triggered it during CI runs; probably not an exact
list since we suppress errors after the first one by using WARN_ONCE, and I'm
not sure how this can be related to GEM tests:

BYT:
  igt at gem_mmap@basic
  igt at kms_flip@basic-flip-vs-wf_vblank
BSW:
  igt at gem_mmap_gtt@basic-write
  igt at kms_pipe_crc_basic@read-crc-pipe-c-frame-sequence

[  112.225567] ------------[ cut here ]------------
[  112.225612] WARNING: CPU: 0 PID: 6638 at
drivers/gpu/drm/i915/intel_drv.h:1446 gen6_write32+0x18a/0x220 [i915]()
[  112.225616] RPM wakelock ref not held during HW access
[  112.225619] Modules linked in:
[  112.225622]  i915 intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul
lpc_ich i2c_hid i2c_designware_platform i2c_designware_core r8169 mii
sdhci_acpi sdhci mmc_core
[  112.225647] CPU: 0 PID: 6638 Comm: kms_flip Tainted: G     U         
4.4.0-rc5-gfxbench+ #1
[  112.225651] Hardware name: DN2820FYK, BIOS FYBYT10H.86A.0038.2014.0717.1455
07/17/2014
[  112.225654]  ffffffffa02138a0 ffff880074317ac0 ffffffff813e000c
ffff880074317b08
[  112.225662]  ffff880074317af8 ffffffff810746a1 0000000000186500
0000000000000000
[  112.225669]  ffff880073400000 0000000000000000 ffff8800734a5d88
ffff880074317b58
[  112.225677] Call Trace:
[  112.225686]  [<ffffffff813e000c>] dump_stack+0x4e/0x82
[  112.225692]  [<ffffffff810746a1>] warn_slowpath_common+0x81/0xc0
[  112.225696]  [<ffffffff81074727>] warn_slowpath_fmt+0x47/0x50
[  112.225723]  [<ffffffffa01873ba>] gen6_write32+0x18a/0x220 [i915]
[  112.225742]  [<ffffffffa0139627>] intel_set_memory_cxsr+0x77/0x1a0 [i915]
[  112.225770]  [<ffffffffa01a67c4>] intel_pre_plane_update+0x84/0xb0 [i915]
[  112.225874]  [<ffffffffa01a6f8f>] intel_atomic_commit+0x38f/0x17f0 [i915]
[  112.225884]  [<ffffffff8150e142>] ? drm_atomic_check_only+0x142/0x600
[  112.225892]  [<ffffffff8150e7ab>] ?
drm_atomic_set_crtc_for_connector+0x1b/0x90
[  112.225900]  [<ffffffff8150e632>] drm_atomic_commit+0x32/0x50
[  112.225910]  [<ffffffff814eb705>] drm_atomic_helper_set_config+0x75/0xb0
[  112.225918]  [<ffffffff814fd640>] drm_mode_set_config_internal+0x60/0x110
[  112.225926]  [<ffffffff815023d6>] drm_mode_setcrtc+0x186/0x4f0
[  112.225935]  [<ffffffff814f450d>] drm_ioctl+0x13d/0x590
[  112.225942]  [<ffffffff81502250>] ? drm_mode_setplane+0x1b0/0x1b0
[  112.225952]  [<ffffffff811d53ec>] do_vfs_ioctl+0x2fc/0x550
[  112.225961]  [<ffffffff8179a5e6>] ? int_ret_from_sys_call+0x52/0x9f
[  112.225968]  [<ffffffff811e0e5a>] ? __fget_light+0x6a/0x90
[  112.225975]  [<ffffffff811d567c>] SyS_ioctl+0x3c/0x70
[  112.225982]  [<ffffffff8179a45b>] entry_SYSCALL_64_fastpath+0x16/0x73
[  112.227738] ---[ end trace 6b624dc5633bbae2 ]---

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151218/5f59e12b/attachment.html>


More information about the intel-gfx-bugs mailing list