From owner-freebsd-bluetooth@FreeBSD.ORG Fri May 12 22:33:10 2006 Return-Path: X-Original-To: bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 964B316A573 for ; Fri, 12 May 2006 22:33:10 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4208D43D46 for ; Fri, 12 May 2006 22:33:10 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 4E6693BE39; Fri, 12 May 2006 17:33:09 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20631-01-27; Fri, 12 May 2006 17:33:09 -0500 (CDT) Received: from [10.254.186.111] (sntc04ep01.savvis.net [64.14.1.106]) by mailgate1b.savvis.net (Postfix) with ESMTP id A59303BE2A; Fri, 12 May 2006 17:33:08 -0500 (CDT) Message-ID: <44650D23.9030507@savvis.net> Date: Fri, 12 May 2006 15:33:07 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean McNeil References: <1147468433.92729.0.camel@triton.mcneil.com> In-Reply-To: <1147468433.92729.0.camel@triton.mcneil.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: bluetooth@freebsd.org Subject: Re: hcsecd: Received unexpected HCI event X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2006 22:33:11 -0000 Sean McNeil wrote: > I get a ton of these. How can I fix it? > > hcsecd[846]: Received unexpected HCI event, event=0xff please provide more information, i.e. 'uname -a', bluetooth device information and what are you trying to do. in theory, you should never get any of these, because hcsecd sets filter to only look for few events (and 0xff, i.e. vendor event is not included in the filter) max