From: Tamas Papp <tkpapp@gmail.com>
To: linux-pm@vger.kernel.org
Subject: STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350
Date: Wed, 02 Mar 2016 10:51:05 +0100 [thread overview]
Message-ID: <87h9gpp5rt.fsf@gmail.com> (raw)
Hi,
I have a Dell XPS 13 (Skylake, 2016) and wanted to get STI working, so I
followed the instructions at [1]. I found that the Broadcom wireless
chip is waking the machine up from STI / freeze.
A workaround is
INTERFACE=wlp58s0
ifconfig $INTERFACE down
modprobe -r brcmfmac && echo freeze > /sys/power/state && modprobe brcmfmac
ifconfig $INTERFACE up
I thought I would ask whether I should report this as a bug, and if yes,
where.
Best,
Tamas
[1] https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
Hardware info (lspci -v):
3a:00.0 Network controller: Broadcom Corporation BCM4350 802.11ac Wireless Network Adapter (rev 08)
Subsystem: Dell BCM4350 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 283
Memory at dc400000 (64-bit, non-prefetchable) [size=32K]
Memory at dc000000 (64-bit, non-prefetchable) [size=4M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-28-ff-ff-77-c8-ff
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] #15
Capabilities: [240] L1 PM Substates
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac
next reply other threads:[~2016-03-02 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 9:51 Tamas Papp [this message]
2016-03-02 13:08 ` STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350 yu chen
2016-03-02 14:13 ` Tamas Papp
2016-03-02 14:44 ` yu chen
2016-03-03 7:16 ` Tamas Papp
2016-03-04 1:41 ` yu chen
2016-03-04 7:30 ` yu chen
2016-03-04 7:36 ` Tamas Papp
2016-03-04 7:49 ` yu chen
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=87h9gpp5rt.fsf@gmail.com \
--to=tkpapp@gmail.com \
--cc=linux-pm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).