From owner-freebsd-usb@FreeBSD.ORG Sat Sep 28 12:24:02 2013 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D26833F4 for ; Sat, 28 Sep 2013 12:24:02 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 5F1B0296D for ; Sat, 28 Sep 2013 12:24:02 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id 88C1C7A06E; Sat, 28 Sep 2013 14:24:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 042588F482F; Sat, 28 Sep 2013 14:24:22 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssp3MazYWmwq; Sat, 28 Sep 2013 14:24:21 +0200 (CEST) Received: from mail.lockless.no (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 24A5D8F4826; Sat, 28 Sep 2013 14:24:21 +0200 (CEST) Subject: RE: randomly losing mouse From: =?utf-8?Q?Hans_Petter_Selasky?= To: =?utf-8?Q?Eitan_Adler?= , =?utf-8?Q?usb=40freebsd=2Eorg?= Date: Sat, 28 Sep 2013 14:24:21 +0200 Mime-Version: 1.0 In-Reply-To: References: X-Priority: 3 (Normal) X-Mailer: Zarafa 7.1.4-41394 Message-Id: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Sep 2013 12:24:02 -0000 Hi,=0D=0A=0D=0ALooks like a problem with the XHCI controller.=0D=0A=0D=0A= Can you try SVN r255768 or newer=3F=20=0D=0A=0D=0AIt might fix the proble= m. Else let me know.=0D=0A=0D=0A--HPS=20=0D=0A=20=0D=0A-----Original mess= age-----=0D=0A> From:Eitan Adler >=0D=0A> Sent: Saturday 28th September 2013 14:18=0D=0A> To: = usb@freebsd.org =20=0D=0A> Subject: randomly losi= ng mouse=0D=0A>=20=0D=0A> When I start my computer both my USB mouse and = trackpad are capable of=0D=0A> controlling the mouse via moused.=0D=0A>=20= =0D=0A> At some point the USB mouse dies and when I try to re-plug it in = I see:=0D=0A>=20=0D=0A> ugen0.3: at usbus0 (disconn= ected)=0D=0A> umass0: at uhub2, port 4, addr 7 (disconnected)=0D=0A> xhci= _do_command: Command timeout!=0D=0A> xhci_do_command: Command timeout!=0D= =0A> usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored)=0D= =0A>=20=0D=0A> in dmesg.=0D=0A>=20=0D=0A> [10017 eitan@gravity (98%) =CB=9C= ]%uname -a=0D=0A> FreeBSD gravity.local 10.0-CURRENT FreeBSD 10.0-CURREN= T #1 r255215:=0D=0A> Sat Sep 7 11:18:17 EDT 2013=0D=0A> eitan@gravity.lo= cal :/usr/obj/usr/src/sys/EADLER amd64=0D=0A= >=20=0D=0A>=20=0D=0A> How can I fix this=3F=0D=0A>=20=0D=0A>=20=0D=0A> --= =20=0D=0A> Eitan Adler=0D=0A> ___________________________________________= ____=0D=0A> freebsd-usb@freebsd.org mai= ling list=0D=0A> http://lists.freebsd.org/mailman/listinfo/freebsd-usb =20=0D=0A> To unsubs= cribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org "=0D=0A>=20=0D=0A=0D=0A From owner-freebsd-usb@FreeBSD.ORG Sat Sep 28 23:12:47 2013 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4768DF2E for ; Sat, 28 Sep 2013 23:12:47 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1DB2A287C for ; Sat, 28 Sep 2013 23:12:47 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id xb4so3966497pbc.8 for ; Sat, 28 Sep 2013 16:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=o+yOV/B9HX0KmYGONIdgjOJ18gJaoWXsJScWb4BAnzM=; b=EoMrUL21E/1zPmYdb8JmwuVfohB/XSePrqFy4MpM6PH+QwDxHkMSIfZ/lpLYCbhWz2 8KY9p+vahpejeh5qw752Mjv+SxvnqTf6AgBNXdbtGFiS3ApdNZSwgXZdxFX9ZKKCWFbR LT2KC8gwW1ljZ1ycDzldDmcogN+xhreUqwac0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=o+yOV/B9HX0KmYGONIdgjOJ18gJaoWXsJScWb4BAnzM=; b=K3Rn2Lhp51EMtIl9/7idQe0upGketCy5BYMSaWXBnjphAyTh5yoTNRJuZoma8gCmYK wW9vE2ZGWgPfObsr14pt82gQbWXCSKCyWhm6W6fbYuAtb/JIjBkfaGtKgLvnWNXvF/XE wV2Vgcgk9qV2S8OZzxHaP5ED/0bjrtozn6ntKOgLUmJI+wIz4iHHPwVuqmqiXRKPA6il 2d2oN4QDVyLZDLjpLQU5t9bxm3eEZQWEzQkUJXnGG4p9pzvpotTpBWvUg2jWD1SwOjjx JNEQaTqlOZ/kv0tZ3QGHsjjQ8IKfEx6zC/rVYbhGCoGA3GgmlhaD9LnoEAq57u7J0d0P YBaw== X-Gm-Message-State: ALoCoQnXwh9w4jVYkv7QWFH5+Dd6kSOf7M/UXbzxQXrbaqf08128BQK3Kc9zR7RK/DT6L9mVhlXb X-Received: by 10.66.150.41 with SMTP id uf9mr19679879pab.108.1380409966297; Sat, 28 Sep 2013 16:12:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.6.3 with HTTP; Sat, 28 Sep 2013 16:12:16 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Sat, 28 Sep 2013 19:12:16 -0400 Message-ID: Subject: Re: randomly losing mouse To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: "usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Sep 2013 23:12:47 -0000 On Sat, Sep 28, 2013 at 8:24 AM, Hans Petter Selasky wrote: > Hi, > > Looks like a problem with the XHCI controller. > > Can you try SVN r255768 or newer? I did notice this commit but I have been running r255215 for a few weeks without issue. > It might fix the problem. Else let me know. I just updated to r255924 and will let you know if I still see the problem -- Eitan Adler