From: Dominik Brodowski <linux@dominikbrodowski.net>
To: tomas.winkler@intel.com
Cc: alexander.usyskin@intel.com, linux-kernel@vger.kernel.org
Subject: MEI-related WARN_ON() triggered during resume-from-sleep on v4.12-rc2+
Date: Sun, 30 Jul 2017 10:59:08 +0200 [thread overview]
Message-ID: <20170730085908.GA2298@light.dominikbrodowski.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
Thomas,
on Linus' most recent kernel (v4.12-rc2, git head 0a07b238e5f48), I see the
following message on my Dell XPS13 when resuming from sleep. MEI is, AFAIK,
not being used on this system:
[ 192.940537] Restarting tasks ...
[ 192.940610] PGI is not set
[ 192.940619] ------------[ cut here ]------------
[ 192.940623] WARNING: CPU: 0 PID: 1661 at /home/brodo/local/kernel/git/linux/drivers/misc/mei/hw-me.c:653 mei_me_pg_exit_sync+0x351/0x360
[ 192.940624] Modules linked in:
[ 192.940627] CPU: 0 PID: 1661 Comm: kworker/0:3 Not tainted 4.13.0-rc2+ #2
[ 192.940628] Hardware name: Dell Inc. XPS 13 9343/0TM99H, BIOS A11 12/08/2016
[ 192.940630] Workqueue: pm pm_runtime_work
<snip>
[ 192.940642] Call Trace:
[ 192.940646] ? pci_pme_active+0x1de/0x1f0
[ 192.940649] ? pci_restore_standard_config+0x50/0x50
[ 192.940651] ? kfree+0x172/0x190
[ 192.940653] ? kfree+0x172/0x190
[ 192.940655] ? pci_restore_standard_config+0x50/0x50
[ 192.940663] mei_me_pm_runtime_resume+0x3f/0xc0
[ 192.940665] pci_pm_runtime_resume+0x7a/0xa0
[ 192.940667] __rpm_callback+0xb9/0x1e0
[ 192.940668] ? preempt_count_add+0x6d/0xc0
[ 192.940670] rpm_callback+0x24/0x90
[ 192.940672] ? pci_restore_standard_config+0x50/0x50
[ 192.940674] rpm_resume+0x4e8/0x800
[ 192.940676] pm_runtime_work+0x55/0xb0
[ 192.940678] process_one_work+0x184/0x3e0
[ 192.940680] worker_thread+0x4d/0x3a0
[ 192.940681] ? preempt_count_sub+0x9b/0x100
[ 192.940683] kthread+0x122/0x140
[ 192.940684] ? process_one_work+0x3e0/0x3e0
[ 192.940685] ? __kthread_create_on_node+0x1a0/0x1a0
[ 192.940688] ret_from_fork+0x27/0x40
[ 192.940690] Code: 96 3a 9e ff 48 8b 7d 98 e8 cd 21 58 00 83 bb bc 01 00 00 04 0f 85 40 fe ff ff e9 41 fe ff ff 48 c7 c7 5f 04 99 96 e8 93 6b 9f ff <0f> ff e9 5d fd ff ff e8 33 fe 99 ff 0f 1f 00 0f 1f 44 00 00 55
[ 192.940719] ---[ end trace a86955597774ead8 ]---
[ 192.942540] done.
This doesn't / didn't happen on v4.12.
Best,
Dominik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-07-30 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 8:59 Dominik Brodowski [this message]
2017-07-30 9:16 ` MEI-related WARN_ON() triggered during resume-from-sleep on v4.12-rc2+ Winkler, Tomas
2017-07-31 22:16 ` Issue with commit de3ef1eb1cd - PM / core: Drop run_wake flag from struct dev_pm_info [Was: MEI-related WARN_ON() triggered during resume-from-sleep on v4.13-rc2+] Dominik Brodowski
2017-07-31 23:55 ` Rafael J. Wysocki
2017-08-01 0:05 ` Rafael J. Wysocki
2017-08-01 5:25 ` Usyskin, Alexander
2017-08-01 6:36 ` Dominik Brodowski
2017-08-01 6:49 ` Winkler, Tomas
2017-08-01 11:51 ` Rafael J. Wysocki
2017-08-01 13:58 ` Winkler, Tomas
2017-08-01 15:32 ` Rafael J. Wysocki
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=20170730085908.GA2298@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox