From owner-freebsd-current@FreeBSD.ORG Mon Feb 22 17:49:23 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 75684106566B for ; Mon, 22 Feb 2010 17:49:23 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id CC96B8FC08 for ; Mon, 22 Feb 2010 17:49:22 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=WhTp6N8Rj_bYZ_v7fmAA:9 a=KqBtm_FIgGWFdHfR2u0A:7 a=PHw-nJEokHI5wwQDpyIKiqcoRMIA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1385339928; Mon, 22 Feb 2010 18:49:21 +0100 From: Hans Petter Selasky To: Chris Hedley Date: Mon, 22 Feb 2010 18:47:45 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; amd64; ; ) References: <201002221806.27139.hselasky@c2i.net> In-Reply-To: X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002221847.45617.hselasky@c2i.net> 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:49:23 -0000 On Monday 22 February 2010 18:45:04 Chris Hedley wrote: > 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. > Hi, If you get no "ums_intr_callback()" printouts at all in the failing case, and you are running 9-current, I guess that your KWM switch has some special requirements on the USB programming which I am not aware about. --HPS