From owner-freebsd-current@FreeBSD.ORG Mon Jun 25 15:37:21 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BFE016A469 for ; Mon, 25 Jun 2007 15:37:21 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5031A13C4C7 for ; Mon, 25 Jun 2007 15:37:21 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l5PFakEX012179; Mon, 25 Jun 2007 09:36:49 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 25 Jun 2007 09:37:23 -0600 (MDT) Message-Id: <20070625.093723.-1844001713.imp@bsdimp.com> To: ianf@clue.co.za From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 25 Jun 2007 09:36:49 -0600 (MDT) Cc: current@freebsd.org Subject: Re: USB mouse works again in current!!! 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, 25 Jun 2007 15:37:21 -0000 In message: Ian FREISLICH writes: : Ian FREISLICH wrote: : > I also fixed the onboard wireless mouse controller which previously : : s/I/It/ : : > worked for about 10 minutes before a usb bus error broke the : > connection. : : Seems I spoke too soon. After running fine for about an hour the : wireless mouse died with the following error: : : Jun 25 09:00:53 apple kernel: usb3: host controller process error : Jun 25 09:00:53 apple kernel: usb3: host controller halted : : Is there any debugging knob I can turn to get more data about what : went wrong? I don't know. You can try configuring USBDEBUG in your kernel, then setting hw.ums.debug=1, but that tends to generate a lot of traffic in an hour. Warner