From: Johannes Berg <johannes@sipsolutions.net>
To: Oliver Freyermuth <o.freyermuth@googlemail.com>,
linux-wireless@vger.kernel.org
Subject: Re: Usage of WoWLAN with iwlwifi driver (Device phy0 failed to suspend async: error -16)
Date: Thu, 02 Mar 2017 09:55:09 +0100 [thread overview]
Message-ID: <1488444909.8390.11.camel@sipsolutions.net> (raw)
In-Reply-To: <6337fa40-adcc-b889-1842-16e0f316ea3e@googlemail.com> (sfid-20170224_221653_742300_1279B3C9)
> > Oh. Can you see if you have CONFIG_IWLWIFI_PCIE_RTPM enabled in
> > your configuration? If you do, please turn it off and see if that
> > fixes it.
>
> Indeed, you got it!
> I had it on, and turning that off lets me suspend just fine after
> activating WoWLAN!
[snip]
> The problem is that it seems I cannot actually wake the machine
> anymore afterwards...
> While in the suspend procedure, I see:
> [12385.893568] iwlwifi 0000:0a:00.0: System wakeup enabled by ACPI
> as expected, I could neither get it to make a tcp connection in tcp-
> connection mode,
> nor could I wake the machine via magic packet in magic-packet mode.
>
> Could that be some hardware / system firmware limitation, e.g. if my
> UEFI does not support actually powering
> the WiFi hardware if I am in S3?
Yes. Does it print something to that effect at resume time? I think it
should.
> At least, the suspend problem seems to be clearly related to some
> path only used if CONFIG_IWLWIFI_PCIE_RTPM is on.
Would you mind filing a bug on bugzilla.kernel.org (and adding linuxwif
i@intel.com as the assignee or at least in Cc)? I think we really ought
to sort out the issues with the RTPM stuff.
johannes
next prev parent reply other threads:[~2017-03-02 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 21:46 Usage of WoWLAN with iwlwifi driver (Device phy0 failed to suspend async: error -16) Oliver Freyermuth
2017-02-24 12:11 ` Johannes Berg
2017-02-24 18:51 ` Oliver Freyermuth
2017-02-24 19:37 ` Johannes Berg
2017-02-24 21:16 ` Oliver Freyermuth
2017-03-02 8:55 ` Johannes Berg [this message]
2017-03-02 18:20 ` Oliver Freyermuth
2017-03-02 18:38 ` Johannes Berg
2017-03-05 15:12 ` Oliver Freyermuth
2017-03-06 8:11 ` Johannes Berg
2017-03-06 21:47 ` Oliver Freyermuth
2017-03-06 21:51 ` Johannes Berg
2017-03-06 22:25 ` Oliver Freyermuth
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=1488444909.8390.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=o.freyermuth@googlemail.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.