From owner-freebsd-current@FreeBSD.ORG Fri Mar 27 22:37:04 2009 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 C9CEC1065670 for ; Fri, 27 Mar 2009 22:37:04 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.tele2.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 3840C8FC14 for ; Fri, 27 Mar 2009 22:37:03 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=ERj7cZBQa3v3bfvKvZQA:9 a=kBMsYxOEac8_PifLK7UA:7 a=x5mgpbIrDNsL3FLWUpKANC0DwLQA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1044471653; Fri, 27 Mar 2009 23:37:02 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 27 Mar 2009 23:39:31 +0100 User-Agent: KMail/1.9.7 References: <49CD4AB4.8080006@fgznet.ch> In-Reply-To: <49CD4AB4.8080006@fgznet.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903272339.33763.hselasky@c2i.net> Cc: Andreas Tobler Subject: Re: usb issue Macbook Pro VM Fusion 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: Fri, 27 Mar 2009 22:37:05 -0000 On Friday 27 March 2009, Andreas Tobler wrote: > Hello, > > I run a fbsd current in a vm instance on my MacBook Pro. > > Today I did the upgrade to todays sources. > > Now I get some annoying warnings from the usb stack: > > ---- > FreeBSD 8.0-CURRENT #0 r190475M: Fri Mar 27 22:07:10 CET 2009 > > andreast@deuterium_fbsd.andreas.nets:/export/devel/obj/export/devel/src/sys >/ANDREAST_amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz (2496.15-MHz > K8-class CPU) > Origin = "GenuineIntel" Id = 0x10676 Stepping = 6 > > Features=0xfebfbff,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS> > Features2=0x80082201> > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant > usable memory = 2133323776 (2034 MB) > avail memory = 2060926976 (1965 MB) > > ... > uhci0: port 0x2080-0x209f irq > 18 at device 0.0 on pci2 > uhci0: [ITHREAD] > usbus0: on uhci0 > ... > usbus0: 12Mbps Full Speed USB v1.0 > ... > ugen0.1: at usbus0 > uhub0: on usbus0 > ... > uhub0: 2 ports with 2 removable, self powered > ... > Root mount waiting for: usbus1 usbus0 > Root mount waiting for: usbus1 usbus0 > uhub1: 6 ports with 6 removable, self powered > Root mount waiting for: usbus0 > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > Root mount waiting for: usbus0 > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > Root mount waiting for: usbus0 > Root mount waiting for: usbus0 > Root mount waiting for: usbus0 > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > uhub_reattach_port:413: could not allocate new device! > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > uhub_reattach_port:413: could not allocate new device! > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > > ---- > > The last lines above are repeating on the console. > > There is no 'known' usb device attached to the port. Means, I have > nothing attached to the usb ports externally. > > If you need the full log, let me know. > > What else can I provide to help debugging? Maybe the VM-ware accidentially reported a USB device and then it removed it. I don't know. There are some sysctl under hw.usb2 which you can turn on. sysctl hw.usb2 | grep debug uhub, uhci, and ehci is probably most interesting. --HPS