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: Fri, 24 Feb 2017 13:11:17 +0100 [thread overview]
Message-ID: <1487938277.2540.13.camel@sipsolutions.net> (raw)
In-Reply-To: <cc035655-0869-f7d7-bdb4-61e7a38b7fc8@googlemail.com> (sfid-20170221_224703_956817_094A0B1B)
> I have been trying to get basic WoWLAN to work with the following
> configuration:
> - Intel Corporation Wireless 7260 (rev 73) with in-tree iwlwifi
> driver
So I just tried on 4.9 with a 6205 NIC and it works there. The
difference must be somewhere in mvm/d3.c then, I guess. I got a lot of
warnings at resume time though, not sure why.
> However, when trying to suspend to RAM ( echo mem > /sys/power/state
> ), I get:
> [46656.403767] dpm_run_callback(): wiphy_suspend+0x0/0x97 [cfg80211]
> returns -16
> [46656.403769] PM: Device phy0 failed to suspend async: error -16
>
However, I don't see EBUSY anywhere there in the driver.
Can you recompile the kernel and run a quick experiment?
Open drivers/net/wireless/intel/iwlwifi/mvm/mvm.h and put something
like this after the includes:
#undef EBUSY
#define EBUSY ({ WARN_ON(1); 16; })
that should trigger a warning at the place where the EBUSY came from,
assuming it did in fact come from the driver. You could repeat it for
net/mac80211/ieee80211_i.h if that doesn't trigger.
> https://bugzilla.kernel.org/show_bug.cgi?id=109591#c25
That device is like mine, afaict, so this seems to be a different bug.
johannes
next prev parent reply other threads:[~2017-02-24 12:53 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 [this message]
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
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=1487938277.2540.13.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.