From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>, Bastian Bittorf <bb@npl.de>
Cc: 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: Tue, 30 May 2017 15:18:42 +0200 [thread overview]
Message-ID: <1496150322.3327.9.camel@sipsolutions.net> (raw)
In-Reply-To: <fa96dfad-8d1b-c48f-df3b-3df0d548a5c6@candelatech.com>
On Wed, 2017-05-17 at 08:22 -0700, Ben Greear wrote:
>
> I saw it exactly once so far, and it happened overnight,
> but we have not been doing a lot of work with the 4.9 kernel until
> recently.
>
> I don't think there were many messages on this system, and certainly
> others have run much longer on systems that should be generating many
> more events without trouble.
Ok.
> 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.
johannes
next prev parent reply other threads:[~2017-05-30 13: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 [this message]
[not found] ` <1496150322.3327.9.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-05-31 8:18 ` Bastian Bittorf
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=1496150322.3327.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bb@npl.de \
--cc=greearb@candelatech.com \
--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).