From: Bastian Bittorf <bb@npl.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ben Greear <greearb@candelatech.com>,
netdev <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 'iw events' stops receiving events after a while on 4.9 + hacks
Date: Wed, 17 May 2017 20:34:31 +0200 [thread overview]
Message-ID: <20170517183431.GG2849@medion.lan> (raw)
In-Reply-To: <1495027835.2442.13.camel@sipsolutions.net>
* Johannes Berg <johannes@sipsolutions.net> [17.05.2017 20:18]:
> On Wed, 2017-05-17 at 12:08 +0200, Bastian Bittorf wrote:
> > * Ben Greear <greearb@candelatech.com> [17.05.2017 11:51]:
[...]
> > > kernels, but when testing on 4.9 overnight, I notice that 'iw
> > > events' is not showing any input. 'strace' shows
> > > that it is waiting on recvmsg. If I start a second 'iw events'
> > > then it will get
> > > wifi events as expected.
> >
> > me too, also seen on 4.4 - i'am happy for debug ideas.
>
> I've never seen this.
>
> Does it happen when it's very long-running? Or when there are lots of
> events?
only a couple of hours. hard to say which is the culprit. here
i run it like:
#!/bin/sh
iw event | while read -r LINE; do
case "$LINE" in
*': new station '*) ... ;;
*': del station '*) ... ;;
esac
done
The script marks new stations with "touch /tmp/$mac"
and removes this file during 'del station'.
What is interesting: i can recognize, that sometimes and
somehow i have stations in 'iw dev wlanX station dump' which
the script has not seen. When debugging this, the script
does not get any new events. A new started 'iw event' can
see further events without problems.
Hard to say where the error happens. I'am on busybox here.
bye, Bastian
prev parent reply other threads:[~2017-05-17 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:12 'iw events' stops receiving events after a while on 4.9 + hacks Ben Greear
2017-05-17 10:08 ` Bastian Bittorf
2017-05-17 13:30 ` Johannes Berg
2017-05-17 15:22 ` Ben Greear
2017-05-30 13:18 ` Johannes Berg
2017-05-31 8:18 ` Bastian Bittorf
2017-05-31 13:46 ` Ben Greear
2017-05-17 18:34 ` Bastian Bittorf [this message]
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=20170517183431.GG2849@medion.lan \
--to=bb@npl.de \
--cc=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).