From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andi Kleen <andi@firstfloor.org>,
Stefan Lippers-Hollmann <s.L-H@gmx.de>,
linux-wireless@vger.kernel.org, Tim Blechmann <tim@klingt.org>,
rjw@sisk.pl, IvDoorn@gmail.com, linville@tuxdriver.com
Subject: Re: regression: rt2561 frequent "Arrived at non-free entry" errors in 2.6.32
Date: Tue, 08 Dec 2009 23:49:30 +0100 [thread overview]
Message-ID: <4B1ED7FA.3070803@gmail.com> (raw)
In-Reply-To: <1260309607.32227.4.camel@johannes.local>
On 12/08/09 23:00, Johannes Berg wrote:
> On Tue, 2009-12-08 at 22:56 +0100, Gertjan van Wingerde wrote:
>
>> Well, this is a test patch, to validate my theory that this is where the problem is.
>> If that is confirmed, then I can start working out a proper solution.
>
> Well but this patch won't help you test that theory, because it'll just
> disable PS completely if there were packets pending when mac80211 asked
> you to enable PS, afaict.
I don't think so, but that can be because of a big misunderstanding on my side on PS.
We just do not go to sleep when being asked to by mac80211, and thus are saving less
power. But awake would still work.
When quickly testing the patch I did see multiple requests for enabling PS come in
which were denied because of this patch. So I don't think that anything is disabled
with respect to PS.
>
>> How does mac80211 look at these things anyway. How does it expect the driver to handle
>> the cases where mac80211 asks the driver to go to sleep because of power saving, and
>> the driver can't because its queues haven't drained yet?
>
> mac80211 does expect you to be able to transmit while asleep. Same
> happens when PS-polling, where it actually expects you to wait for the
> response frame too. I think. I haven't looked at this in a while.
OK. If that is the case then it may very well be that the PS implementation of rt2x00
is completely broken, as I cannot find any code to wake up if any TX frames come in.
Maybe the safest thing to do would be to disable powersaving from the driver until
we have figured out what the proper implementation of it is for rt2x00.
---
Gertjan.
next prev parent reply other threads:[~2009-12-08 22:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 23:32 regression: rt2561 frequent "Arrived at non-free entry" errors in 2.6.32 Andi Kleen
2009-12-06 13:40 ` Gertjan van Wingerde
2009-12-06 17:04 ` Andi Kleen
2009-12-06 17:20 ` Johannes Berg
2009-12-06 17:32 ` Andi Kleen
2009-12-07 9:31 ` Tim Blechmann
2009-12-07 21:58 ` Gertjan van Wingerde
2009-12-09 22:59 ` Tim Blechmann
2009-12-09 23:23 ` Gertjan van Wingerde
2009-12-09 23:49 ` Tim Blechmann
2009-12-07 23:06 ` Stefan Lippers-Hollmann
2009-12-08 9:57 ` Andi Kleen
2009-12-08 10:19 ` Gertjan van Wingerde
2009-12-08 21:42 ` Gertjan van Wingerde
2009-12-08 21:44 ` Johannes Berg
2009-12-08 21:56 ` Gertjan van Wingerde
2009-12-08 22:00 ` Johannes Berg
2009-12-08 22:49 ` Gertjan van Wingerde [this message]
2009-12-08 22:39 ` Stefan Lippers-Hollmann
2009-12-08 22:40 ` Johannes Berg
2009-12-08 22:44 ` Gertjan van Wingerde
2009-12-08 23:53 ` Stefan Lippers-Hollmann
2009-12-09 6:58 ` Gertjan van Wingerde
2009-12-09 8:24 ` Johannes Berg
2009-12-10 0:46 ` Stefan Lippers-Hollmann
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=4B1ED7FA.3070803@gmail.com \
--to=gwingerde@gmail.com \
--cc=IvDoorn@gmail.com \
--cc=andi@firstfloor.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
--cc=s.L-H@gmx.de \
--cc=tim@klingt.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).