From owner-freebsd-net@FreeBSD.ORG  Tue Jul 27 21:30:11 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EB3C6106568B;
	Tue, 27 Jul 2010 21:30:11 +0000 (UTC)
	(envelope-from emax@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id C3FDE8FC1F;
	Tue, 27 Jul 2010 21:30:11 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6RLUBrp040159;
	Tue, 27 Jul 2010 21:30:11 GMT
	(envelope-from emax@freefall.freebsd.org)
Received: (from emax@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6RLUBif040153;
	Tue, 27 Jul 2010 21:30:11 GMT (envelope-from emax)
Date: Tue, 27 Jul 2010 21:30:11 GMT
Message-Id: <201007272130.o6RLUBif040153@freefall.freebsd.org>
To: emax@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-bluetooth@FreeBSD.org
From: emax@FreeBSD.org
Cc: 
Subject: Re: kern/140590: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej
	warnings
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 21:30:12 -0000

Synopsis: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warnings

Responsible-Changed-From-To: freebsd-net->freebsd-bluetooth
Responsible-Changed-By: emax
Responsible-Changed-When: Tue Jul 27 21:26:59 UTC 2010
Responsible-Changed-Why: 
freebsd-bluetooth seems more appropriate here.
further analysis, however, is difficult without knowing what remote device
was used. ideally, full binary hci dump is needed


http://www.freebsd.org/cgi/query-pr.cgi?pr=140590