Bug 156361 - Suspend fails & system is unusable after attempt (Dell XPS 13 9350 / Skylake)
Summary: Suspend fails & system is unusable after attempt (Dell XPS 13 9350 / Skylake)
Status: CLOSED MOVED
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: Intel Linux
: P1 high
Assignee: Chen Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-08 15:00 UTC by Victor Trac
Modified: 2016-09-12 10:48 UTC (History)
3 users (show)

See Also:
Kernel Version: 4.8.0-rc5-mainline
Subsystem:
Regression: No
Bisected commit-id:


Attachments
full dmesg (169.52 KB, text/plain)
2016-09-08 15:00 UTC, Victor Trac
Details
output from journalctl (159.76 KB, text/plain)
2016-09-08 15:01 UTC, Victor Trac
Details

Description Victor Trac 2016-09-08 15:00:18 UTC
Created attachment 232631 [details]
full dmesg

Description of problem:
When closing the lid to suspend my laptop, resuming does not work about 20% of the time. The laptop is then frozen and I have to switch it of (pressing the power button a longer time).

Version-Release number of selected component (if applicable):
4.8.0-rc5-mainline. Problem started with 4.8.

How reproducible:
Always

Steps to Reproduce:
1. Close lid. 
2. Open lid. 

Actual results:
When the lid is closed, the laptop tries to suspend. After waiting a few minutes, I can still hear the fan running and the laptop is still generating heat (found out by having it in a bag). If I open the lid, the laptop screen flashes a few times, and after a longer than expected time, GDM pops up and lets me login. However, everything seems a bit corrupted - I can open new terminals in gnome-terminal, but any 'sudo' command hangs forever (and ignores ctrl+c) and nothing (tabs, windows, etc) is clickable in chromium.  A 'reboot' command immediately shuts off the screen but hangs forever without actually rebooting.

Expected results:
Laptop suspends and resumes as previously in 4.7.x.
Comment 1 Victor Trac 2016-09-08 15:01:05 UTC
Created attachment 232641 [details]
output from journalctl
Comment 2 Chen Yu 2016-09-12 01:41:48 UTC
According to your log, this is a wifi driver brcmfmac issue, how about  disable this driver(rmmod) to have a try?
Sep 08 08:39:24 callisto kernel: Freezing user space processes ... 
Sep 08 08:39:24 callisto kernel: ACPI Error: 
Sep 08 08:39:24 callisto kernel: Cannot release Mutex [PATM], not acquired (20160422/exmutex-393)
Sep 08 08:39:24 callisto kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff88046e0def00), AE_AML_MUTEX_NOT_ACQUIRED (20160422/psparse-542)
Sep 08 08:39:24 callisto kernel: 
Sep 08 08:39:24 callisto kernel: Freezing of tasks failed after 20.005 seconds (11 tasks refusing to freeze, wq_busy=0):
Sep 08 08:39:24 callisto kernel: wpa_supplicant  D ffff88045a51b988     0  1887      1 0x00000004
Sep 08 08:39:24 callisto kernel:  ffff88045a51b988 0000000000000000 ffff8804261d2c40 ffff880460a0bb00
Sep 08 08:39:24 callisto kernel:  ffff88045a51b9b0 ffff88045a51c000 ffffffff818be3c4 ffff880460a0bb00
Sep 08 08:39:24 callisto kernel:  00000000ffffffff ffffffff818be3c8 ffff88045a51b9a0 ffffffff815ec5ec
Sep 08 08:39:24 callisto kernel: Call Trace:
Sep 08 08:39:24 callisto kernel:  [<ffffffff815ec5ec>] schedule+0x3c/0x90
Sep 08 08:39:24 callisto kernel:  [<ffffffff815ec995>] schedule_preempt_disabled+0x15/0x20
Sep 08 08:39:24 callisto kernel:  [<ffffffff815ede6b>] __mutex_lock_slowpath+0xcb/0x150
Sep 08 08:39:24 callisto kernel:  [<ffffffff815edf07>] mutex_lock+0x17/0x30
Sep 08 08:39:24 callisto kernel:  [<ffffffff814f0965>] rtnl_lock+0x15/0x20
Sep 08 08:39:24 callisto kernel:  [<ffffffffa08ad7c2>] brcmf_p2p_ifp_removed+0x32/0x50 [brcmfmac]
Sep 08 08:39:24 callisto kernel:  [<ffffffffa08af75b>] brcmf_remove_interface+0x16b/0x180 [brcmfmac]
Sep 08 08:39:24 callisto kernel:  [<ffffffffa08ad68e>] brcmf_p2p_del_vif+0xde/0x1e0 [brcmfmac]
Sep 08 08:39:24 callisto kernel:  [<ffffffffa08a3c98>] brcmf_cfg80211_del_iface+0x208/0x270 [brcmfmac]
Sep 08 08:39:24 callisto kernel:  [<ffffffffa080560e>] nl80211_del_interface+0x9e/0x220 [cfg80211]
Sep 08 08:39:24 callisto kernel:  [<ffffffff815176ff>] genl_family_rcv_msg+0x1df/0x3d0
Sep 08 08:39:24 callisto kernel:  [<ffffffff810b907d>] ? pick_next_task_fair+0x45d/0x4d0
Sep 08 08:39:24 callisto kernel:  [<ffffffff815178f0>] ? genl_family_rcv_msg+0x3d0/0x3d0
Sep 08 08:39:24 callisto kernel:  [<ffffffff81517977>] genl_rcv_msg+0x87/0xc0
Sep 08 08:39:24 callisto kernel:  [<ffffffff81516974>] netlink_rcv_skb+0xa4/0xc0
Sep 08 08:39:24 callisto kernel:  [<ffffffff81517508>] genl_rcv+0x28/0x40
Sep 08 08:39:24 callisto kernel:  [<ffffffff8151625c>] netlink_unicast+0x17c/0x240
Sep 08 08:39:24 callisto kernel:  [<ffffffff81516738>] netlink_sendmsg+0x348/0x3b0
Sep 08 08:39:24 callisto kernel:  [<ffffffff814c22f7>] sock_sendmsg+0x17/0x30
Sep 08 08:39:24 callisto kernel:  [<ffffffff814c2a45>] ___sys_sendmsg+0x295/0x2b0
Sep 08 08:39:24 callisto kernel:  [<ffffffff8121f69b>] ? destroy_inode+0x3b/0x60
Sep 08 08:39:24 callisto kernel:  [<ffffffff8121f7f2>] ? evict+0x132/0x190
Sep 08 08:39:24 callisto kernel:  [<ffffffff811debc0>] ? kmem_cache_free+0x1e0/0x210
Sep 08 08:39:24 callisto kernel:  [<ffffffff8121b4ae>] ? dentry_free+0x4e/0x80
Sep 08 08:39:24 callisto kernel:  [<ffffffff8121b5f4>] ? __dentry_kill+0x114/0x160
Sep 08 08:39:24 callisto kernel:  [<ffffffff8122486c>] ? mntput_no_expire+0x2c/0x1b0
Sep 08 08:39:24 callisto kernel:  [<ffffffff81224a14>] ? mntput+0x24/0x40
Sep 08 08:39:24 callisto kernel:  [<ffffffff81205dcd>] ? __fput+0x13d/0x1e0
Sep 08 08:39:24 callisto kernel:  [<ffffffff814c3ba4>] __sys_sendmsg+0x54/0x90
Sep 08 08:39:24 callisto kernel:  [<ffffffff814c3bf2>] SyS_sendmsg+0x12/0x20
Sep 08 08:39:24 callisto kernel:  [<ffffffff815f0572>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Comment 3 Victor Trac 2016-09-12 04:40:33 UTC
(In reply to Chen Yu from comment #2)
> According to your log, this is a wifi driver brcmfmac issue, how about 
> disable this driver(rmmod) to have a try?

Confirmed that rmmod of the brcmfmac module resolves the issue, and I'm able to suspend/resume as expected.
Comment 4 Zhang Rui 2016-09-12 10:48:14 UTC
Then please file another bug report to the brcmfmac driver people.
Bug closed.

Note You need to log in before you can comment on or make changes to this bug.