From owner-freebsd-bluetooth@FreeBSD.ORG  Wed Apr 22 17:45:06 2015
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 63757ADC
 for <freebsd-bluetooth@freebsd.org>; Wed, 22 Apr 2015 17:45:06 +0000 (UTC)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com
 [IPv6:2607:f8b0:4001:c05::232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2EBFC1E8F
 for <freebsd-bluetooth@freebsd.org>; Wed, 22 Apr 2015 17:45:06 +0000 (UTC)
Received: by igblo3 with SMTP id lo3so3106540igb.0
 for <freebsd-bluetooth@freebsd.org>; Wed, 22 Apr 2015 10:45:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=jmXUTELpqnAbZ6YBhktZzQ4T/vj9OoK4oj9/L2AaEMY=;
 b=tJfUHd7MSKrUFhHtxzc3lne/UZGaPw/TK0j+ww7X3fk1Sr+qHwVtNU5bs4f5OQfcaA
 L5dfIA4inQXsfqL7PoeZxRjZsgA1D2xAbDoNrxiEjZiJ442QNqwEBwoXZo+J17DCRz48
 8NZs+iaZoE3wTyYrSy6Eeq1s3XxKto568lEr7U1G5BWa+i4YNFQi9EVCfV+fGN0PtjUg
 ylv8wAg5fJ3Fpzg7XoEWp6/QKJE6YDRBslkzryiGmUJxxqjNkg9jJ9+06VGc07MgzRkJ
 ITTSMVT4F+ESP52uwRctc4/HcnJQZzRMteYf11WeqEW59CmdkxloowaWhtjmrs55j/El
 pdKQ==
MIME-Version: 1.0
X-Received: by 10.43.63.76 with SMTP id xd12mr11346815icb.11.1429724705515;
 Wed, 22 Apr 2015 10:45:05 -0700 (PDT)
Received: by 10.36.66.17 with HTTP; Wed, 22 Apr 2015 10:45:05 -0700 (PDT)
In-Reply-To: <CAFuo_fzVganO6M07neAWBVqda1vzV9VNWurU6EsP_3Mc78-dMA@mail.gmail.com>
References: <CAFuo_fzVganO6M07neAWBVqda1vzV9VNWurU6EsP_3Mc78-dMA@mail.gmail.com>
Date: Wed, 22 Apr 2015 10:45:05 -0700
Message-ID: <CAFPOs6oySELB+Fsf8nt92OAtizkEn425qeFmy-oc9NHdkFwUNA@mail.gmail.com>
Subject: Re: question about bthidd client.c
From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To: Waitman Gobble <gobble.wa@gmail.com>
Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
 <freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth/>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 17:45:06 -0000

On Tue, Apr 21, 2015 at 10:34 PM, Waitman Gobble <gobble.wa@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