On Wed, Apr 22, 2015 at 10:45 AM, Maksim Yevmenkin <maksim.yevmen...@gmail.com> wrote: > On Tue, Apr 21, 2015 at 10:34 PM, Waitman Gobble <gobble...@gmail.com> wrote: >> >> I notice that if bthidd is running, and bluetooth is not active, or >> the configured host is out of range, the client_rescan() function >> generates new vkbd devices every 20 seconds or so. I believe this will >> eventually lock up the machine. >> > > may be... usually devices will reconnect, i.e. reconnect_initiate > would be 1. however, this is a known problem. for whatever reason > "cloned" devices are not completely going away when closed. similar > problem exists with other "cloned" devices. its not bthidd or > bluetooth code specific. > > thanks > max
Thanks for the reply. Is there a better way to decide if a device is 'connectable'? It looks like a chicken-and-egg kind of problem, since the connect routine uses the established vkbd device. I am thinking that attempting to connect to the device on psm 1 is a way to verify that the host is connectable in the first place, before creating a new vkbd. Or, maybe the new vkbd can be destroyed on failure... but maybe this would cause other problems. I noticed this problem when I had the dongle unplugged, so there was no bluetooth available. But I had left bthidd set to start in rc.conf. Thank you, -- Waitman Gobble Los Altos California USA 510-830-7975 _______________________________________________ freebsd-bluetooth@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscr...@freebsd.org"
