public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Imre Deak <imre.deak@intel.com>, David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] RPM wakelock ref not held during HW access
Date: Tue, 12 Jan 2016 16:32:52 +0100	[thread overview]
Message-ID: <20160112153252.GC19130@phenom.ffwll.local> (raw)
In-Reply-To: <20160112150607.GB670@swordfish>

On Wed, Jan 13, 2016 at 12:06:07AM +0900, Sergey Senozhatsky wrote:
> Hello,
> 
> -mmots 4.4.0-mm1-dbg-00602-g776bd09

Patch to shut this up (rpm is disabled by default for a reason still) on
it's way into 4.5/-next.

Thanks anyway for the report.
-Daniel
> 
> 
> [ 5331.509087] WARNING: CPU: 0 PID: 359 at drivers/gpu/drm/i915/intel_drv.h:1446 gen6_read32+0x7b/0x253 [i915]()
> [ 5331.509091] RPM wakelock ref not held during HW access
> [ 5331.509093] Modules linked in:
> [ 5331.509182] CPU: 0 PID: 359 Comm: Xorg Not tainted 4.4.0-mm1-dbg-00602-g776bd09-dirty #34
> [ 5331.509186]  0000000000000000 ffff88041bddfac0 ffffffff811eb860 ffff88041bddfb08
> [ 5331.509194]  ffff88041bddfaf8 ffffffff81040fc2 ffffffffa05442a9 ffff88041aab0000
> [ 5331.509200]  0000000000064000 ffff88041afcb001 0000000000000001 ffff88041bddfb60
> [ 5331.509207] Call Trace:
> [ 5331.509218]  [<ffffffff811eb860>] dump_stack+0x4b/0x63
> [ 5331.509227]  [<ffffffff81040fc2>] warn_slowpath_common+0x99/0xb2
> [ 5331.509277]  [<ffffffffa05442a9>] ? gen6_read32+0x7b/0x253 [i915]
> [ 5331.509283]  [<ffffffff81041023>] warn_slowpath_fmt+0x48/0x50
> [ 5331.509331]  [<ffffffffa05442a9>] gen6_read32+0x7b/0x253 [i915]
> [ 5331.509338]  [<ffffffff813b8ff6>] ? mutex_unlock+0xe/0x10
> [ 5331.509391]  [<ffffffffa057ae04>] intel_ddi_get_hw_state+0x5e/0x159 [i915]
> [ 5331.509443]  [<ffffffffa057cdd8>] intel_ddi_connector_get_hw_state+0x5c/0xdf [i915]
> [ 5331.509494]  [<ffffffffa056134b>] intel_atomic_commit+0x8e0/0x1250 [i915]
> [ 5331.509528]  [<ffffffffa03f7acb>] ? drm_atomic_check_only+0x293/0x564 [drm]
> [ 5331.509558]  [<ffffffffa03f7de9>] drm_atomic_commit+0x4d/0x52 [drm]
> [ 5331.509572]  [<ffffffffa04e193e>] drm_atomic_helper_connector_dpms+0x116/0x17e [drm_kms_helper]
> [ 5331.509599]  [<ffffffffa03ee56c>] drm_mode_obj_set_property_ioctl+0xef/0x17a [drm]
> [ 5331.509626]  [<ffffffffa03ee627>] drm_mode_connector_property_set_ioctl+0x30/0x32 [drm]
> [ 5331.509642]  [<ffffffffa03e10cb>] drm_ioctl+0x26d/0x3a8 [drm]
> [ 5331.509668]  [<ffffffffa03ee5f7>] ? drm_mode_obj_set_property_ioctl+0x17a/0x17a [drm]
> [ 5331.509675]  [<ffffffff81081c42>] ? lock_acquire+0x101/0x188
> [ 5331.509681]  [<ffffffff81165543>] ? __fget+0x5/0x19d
> [ 5331.509685]  [<ffffffff8107d59a>] ? __lock_is_held+0x3c/0x57
> [ 5331.509691]  [<ffffffff8115ae60>] vfs_ioctl+0x18/0x34
> [ 5331.509695]  [<ffffffff8115b489>] do_vfs_ioctl+0x572/0x5f1
> [ 5331.509699]  [<ffffffff81165764>] ? __fget_light+0x62/0x71
> [ 5331.509704]  [<ffffffff8115b54b>] SyS_ioctl+0x43/0x61
> [ 5331.509711]  [<ffffffff813bb017>] entry_SYSCALL_64_fastpath+0x12/0x6f
> [ 5331.509715] ---[ end trace 70d4fd86a0395d92 ]---
> 
> 	-ss
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2016-01-12 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 15:06 RPM wakelock ref not held during HW access Sergey Senozhatsky
2016-01-12 15:32 ` Daniel Vetter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160112153252.GC19130@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergey.senozhatsky@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox