From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: New "RPM wakelock ref not held during HW access" in 4.12-rc1 ?
Date: Tue, 16 May 2017 13:34:52 +0300 [thread overview]
Message-ID: <87y3txks37.fsf@intel.com> (raw)
In-Reply-To: <20170516095557.GR12629@intel.com>
On Tue, 16 May 2017, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> mn Tue, May 16, 2017 at 10:47:48AM +0300, Jani Nikula wrote:
>> On Mon, 15 May 2017, Hans de Goede <hdegoede@redhat.com> wrote:
>> > Hi,
>> >
>> > I'm seeing this on suspend/resume on a GPD-win,
>> > cherrytrail z8700 device:
>>
>> Ville, does
>>
>> commit 668e3b014afb66ab29e134bca7c258527273ac75
>> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Date: Thu Apr 27 19:02:20 2017 +0300
>>
>> drm/i915: Fix runtime PM for LPE audio
>>
>> in drm-intel-fixes address this?
>
> ebf5f921478b ("drm/i915: Stop pretending to mask/unmask LPE audio
> interrupts") is a more likely candidate.
Is that applicable to v4.12-rc1?
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>>
>>
>> >
>> > [ 75.514651] RPM wakelock ref not held during HW access
>> > [ 75.514827] ------------[ cut here ]------------
>> > [ 75.515025] WARNING: CPU: 2 PID: 1832 at drivers/gpu/drm/i915/intel_drv.h:1780 fwtable_write32+0x1d3/0x240 [i915]
>> > ...
>> > [ 75.515704] RIP: 0010:fwtable_write32+0x1d3/0x240 [i915]
>> > ...
>> > [ 75.515767] Call Trace:
>> > [ 75.515952] lpe_audio_irq_unmask+0x6a/0xc0 [i915]
>> > [ 75.515972] irq_enable+0x3a/0x50
>> > [ 75.515984] __enable_irq+0x34/0x60
>> > [ 75.515996] resume_irqs+0x8f/0xd0
>> > [ 75.516007] resume_device_irqs+0x10/0x20
>> > [ 75.516021] dpm_resume_noirq+0x23e/0x310
>> > [ 75.516041] suspend_devices_and_enter+0x2f3/0x7f0
>> > [ 75.516055] ? finish_wait+0x80/0x80
>> > [ 75.516067] pm_suspend+0x335/0x3a0
>> > [ 75.516078] state_store+0x85/0xf0
>> > [ 75.516095] kobj_attr_store+0xf/0x20
>> > [ 75.516108] sysfs_kf_write+0x37/0x40
>> > [ 75.516117] kernfs_fop_write+0x11c/0x1a0
>> > [ 75.516132] __vfs_write+0x37/0x160
>> > [ 75.516145] ? selinux_file_permission+0xfb/0x120
>> > [ 75.516158] ? security_file_permission+0x3b/0xc0
>> > [ 75.516169] vfs_write+0xb1/0x1a0
>> > [ 75.516180] SyS_write+0x55/0xc0
>> > [ 75.516197] entry_SYSCALL_64_fastpath+0x1a/0xa5
>> > ...
>> > [ 76.584235] PM: early resume of devices complete after 1067.477 msecs
>> >
>> > If someone has a fix for this they want me to try, let me know.
>> >
>> > Regards,
>> >
>> > Hans
>> > _______________________________________________
>> > Intel-gfx mailing list
>> > Intel-gfx@lists.freedesktop.org
>> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>
>> --
>> Jani Nikula, Intel Open Source Technology Center
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-16 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 18:13 New "RPM wakelock ref not held during HW access" in 4.12-rc1 ? Hans de Goede
2017-05-16 7:47 ` Jani Nikula
2017-05-16 9:55 ` Ville Syrjälä
2017-05-16 10:34 ` Jani Nikula [this message]
2017-05-18 13:59 ` Hans de Goede
2017-05-26 8:37 ` Hans de Goede
2017-05-26 8:55 ` Jani Nikula
2017-05-26 8:55 ` Hans de Goede
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=87y3txks37.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.