From owner-freebsd-current@FreeBSD.ORG Mon Feb 22 17:07:59 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 9CAAD106566B for ; Mon, 22 Feb 2010 17:07:59 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF558FC0C for ; Mon, 22 Feb 2010 17:07:58 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=FpDhRG4oO7ufK1I2r2UA:9 a=VgO3LsmMb1Kuzrdnv-UA:7 a=Z1tg312tQHkuD5BzkvAeSayJvZgA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1355110634; Mon, 22 Feb 2010 18:07:57 +0100 From: Hans Petter Selasky To: Chris Hedley Date: Mon, 22 Feb 2010 18:06:27 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; amd64; ; ) References: <201002221712.38449.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-15" Content-Transfer-Encoding: 7bit Message-Id: <201002221806.27139.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:07:59 -0000 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? --HPS