From owner-freebsd-current@FreeBSD.ORG Mon Feb 22 17:45:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 869BA106566B for ; Mon, 22 Feb 2010 17:45:11 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from smtp3.enta.net (smtp3.enta.net [87.127.246.178]) by mx1.freebsd.org (Postfix) with ESMTP id 43E578FC14 for ; Mon, 22 Feb 2010 17:45:10 +0000 (UTC) Received: from mail.chrishedley.com (unknown [78.32.138.135]) by smtp3.enta.net (Postfix) with ESMTP id AD91AB57D1A for ; Mon, 22 Feb 2010 17:45:09 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id C51247D0EB; Mon, 22 Feb 2010 17:45:08 +0000 (GMT) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nD1BpobBfQxP; Mon, 22 Feb 2010 17:45:04 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id A8EB87D0CF; Mon, 22 Feb 2010 17:45:04 +0000 (GMT) Date: Mon, 22 Feb 2010 17:45:04 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: Hans Petter Selasky In-Reply-To: <201002221806.27139.hselasky@c2i.net> Message-ID: References: <201002221712.38449.hselasky@c2i.net> <201002221806.27139.hselasky@c2i.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: ums fails to initialise correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2010 17:45:11 -0000 On Mon, 22 Feb 2010, Hans Petter Selasky wrote: > On Monday 22 February 2010 17:52:25 Chris Hedley wrote: >> On Mon, 22 Feb 2010, Hans Petter Selasky wrote: >>> Hi, >>> >>> What is printed to dmesg when you enable debugging? >>> >>> sysctl hw.usb.ums.debug=15 >> >> Is the attached information okay? I tried it twice, first after a switch >> using the KVM (where the mouse didn't work) and second when unplugging the >> receiver and plugging it back in. Both traces are identical except for >> the sc=0xf... etc bit. >> >> Do you want me to get the boot-time messages too, or is this okay for now? >> > > What is printed when you move the mouse? When I disconnect & reconnect it, I get lots of stuff like this as the pointer moves about the screen: ums_intr_callback: sc=0xffffff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 ff ff 00 00 ums_intr_callback: x:0 y:1 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback: sc=0xffffff00015ae800 actlen=8 ums_intr_callback: data = 00 00 00 00 fc ff 00 00 ums_intr_callback: x:0 y:4 z:0 t:0 w:0 buttons:0x00000000 ums_intr_callback: sc=0xffffff00015ae800 actlen=8 ums_intr_callback: data = 00 00 ec ff d5 ff 00 00 ums_intr_callback: x:-20 y:43 z:0 t:0 w:0 buttons:0x00000000 But nothing at all when it hasn't initialised properly.