From: Bastian Bittorf <bb-j3O8QLukP0Q@public•gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public•gmane.org>
Cc: Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public•gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public•gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>
Subject: Re: 'iw events' stops receiving events after a while on 4.9 + hacks
Date: Wed, 31 May 2017 10:18:36 +0200 [thread overview]
Message-ID: <20170531081836.GC2849@medion.lan> (raw)
In-Reply-To: <1496150322.3327.9.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
* Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public•gmane.org> [31.05.2017 10:09]:
> > Is there any way to dump out the socket information if we reproduce
> > the problem?
>
> I have no idea, sorry.
>
> If you or Bastian can tell me how to reproduce the problem, I can try
> to investigate it.
there was an interesting fix regarding the shell-builtin 'read' in
busybox[1]. I will retest again and report if this changes anything.
bye, bastian
PS: @ben: are you also using 'iw event | while read -r LINE ...'?
[1]
https://git.busybox.net/busybox/commit/?id=f5470419404d643070db99d058405b714695b817
next prev parent reply other threads:[~2017-05-31 8:18 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
[not found] ` <d82d191e-8ede-68c6-c9e0-c381dc874d36-my8/4N5VtI7c+919tysfdA@public.gmane.org>
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
[not found] ` <1496150322.3327.9.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-05-31 8:18 ` Bastian Bittorf [this message]
2017-05-31 13:46 ` Ben Greear
2017-05-17 18:34 ` Bastian Bittorf
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=20170531081836.GC2849@medion.lan \
--to=bb-j3o8qlukp0q@public$(echo .)gmane.org \
--cc=greearb-my8/4N5VtI7c+919tysfdA@public$(echo .)gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public$(echo .)gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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