On 05/31/2017 01:18 AM, Bastian Bittorf wrote:
* Johannes Berg <johan...@sipsolutions.net> [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 ...'?
I'm using a perl script to read the output, and not using busybox.
I have not seen the problem again, so it is not easy for me to reproduce.
If you reproduce it, maybe check 'strace' on the 'iw' process to see if it is
hung on writing output to the pipe or reading input? In my case, it appeared
to be hung reading input from netlink, input that never arrived.
Thanks,
Ben
--
Ben Greear <gree...@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
