From owner-freebsd-usb@FreeBSD.ORG Wed May 25 08:51:56 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E766106564A for ; Wed, 25 May 2011 08:51:56 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id B51348FC1A for ; Wed, 25 May 2011 08:51:55 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4P8Pi9G047019 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 25 May 2011 01:25:46 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DDCBD0C.2060002@freebsd.org> Date: Wed, 25 May 2011 01:25:48 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Daniel O'Connor" References: <91D613ED-CA0F-41BF-AD53-2FD42529DCF8@gsoft.com.au> <201105250933.13255.hselasky@c2i.net> <99FAD844-DDC8-4C3D-8117-0887CB893728@gsoft.com.au> <201105250951.53498.hselasky@c2i.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org Subject: Re: USB driver locking X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 08:51:56 -0000 On 5/25/11 12:54 AM, Daniel O'Connor wrote: > On 25/05/2011, at 9:51, Hans Petter Selasky wrote: >>>> current. There is also a new utility called usbdump, which can be used to >>>> figure out what is going on. >>> I am running 9-current (in production for my sins..) >>> >>> usbdump is useful but consumes too much CPU at my data rate :( >> You probably need an USB analyzer to figure out the real problem. Have you >> tried to start usbdump only once the problem happens? > I'll try and cook something up to run it when the problem happens. hans and Daniel, I suggest you put some KTR points into the driver and trace some crucial information using that. it is capable of keeping up with very fast stuff with small disturbance. Just the basic info.. you get 5 x 64 bit arguments. (or is it 6?) which is enough space for quite a bit of stuff to be logged. > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" >