This seems like a pretty nasty regression which occurred sometime after the 1.26 release. Is anyone else experiencing this? Any tips from developers on how we can figure out what's going on here and fix it?
On 5 January 2015 at 14:14, Mike O'Driscoll < modrisc...@clearpathrobotics.com> wrote: > I've compiled both at master and at tag 1.26. > Master still shows this issue and 1.26 does not. > > This seems be be added in post 1.26 tag in the git repo. > > Running with "#connmand -n -d" the following line is constantly run over: > > https://git.kernel.org/cgit/network/connman/connman.git/tree/src/dhcpv6.c#n1687 > > I'm happy to provide a full debug log if needed. > > > -- > Mike O'Driscoll > > On Mon, Jan 5, 2015 at 12:16 PM, Mike Purvis < > mpur...@clearpathrobotics.com> wrote: > >> We're presently experiencing 100% CPU in connmand when tethering is >> enabled, using version 1.27 (PPA >> <https://launchpad.net/~mikepurvis/+archive/ubuntu/network>) on Ubuntu >> Trusty, with kernel 3.16. The problem appears in virtualbox connected to a >> USB dongle as well as on a physical J1900 motherboard with an Intel 6235 >> adapter. >> >> Now building from source to investigat for a cause, and also checking if >> this is a regression from 1.26. >> >> Mike >> > > _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman