From owner-freebsd-usb@FreeBSD.ORG Wed Nov 6 15:41:19 2013 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 891A65EB for ; Wed, 6 Nov 2013 15:41:19 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 1CC0F2852 for ; Wed, 6 Nov 2013 15:41:18 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id C2A7C7A14D; Wed, 6 Nov 2013 16:41:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 1BC6A8F1B97; Wed, 6 Nov 2013 16:41:41 +0100 (CET) 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 6qGwnNFxws2e; Wed, 6 Nov 2013 16:41:40 +0100 (CET) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) by mail.lockless.no (Postfix) with ESMTPSA id F17D88F1B95; Wed, 6 Nov 2013 16:41:39 +0100 (CET) Message-ID: <527A635D.6080200@bitfrost.no> Date: Wed, 06 Nov 2013 16:42:21 +0100 From: Hans Petter Selasky Organization: Bitfrost A/S User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Roland Behme , freebsd-usb@FreeBSD.org Subject: Re: usb/181159: Problem attaching USB device References: <201311061510.rA6FA3Sj093591@freefall.freebsd.org> In-Reply-To: <201311061510.rA6FA3Sj093591@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 06 Nov 2013 15:41:19 -0000 On 11/06/13 16:10, Roland Behme wrote: > The following reply was made to PR usb/181159; it has been noted by GNATS. > > From: Roland Behme > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: usb/181159: Problem attaching USB device > Date: Wed, 06 Nov 2013 16:02:10 +0100 > > I think I have a similar problem with an ASRock H87 Pro4 mainboard here. > First I tried with FreeBSD 9.2 RELEASE, then after I found this PR I > switched to 9.2 STABLE in order to try the patch mentioned above. > Unfortunately unlike for my fellow poster, it doesn't help in my case. > > When I enable the USB 3.0 feature in UEFI BIOS, the plugged in devices > are not attached. > > This is what I get from dmesg: > > xhci0: mem 0xf0420000-0xf042ffff > irq 16 at device 20.0 on pci0 > xhci0: 32 byte context size. > xhci0: Port routing mask set to 0xffffffff > usbus0 on xhci0 > [...] > usbus0: 5.0Gbps Super Speed USB v3.0 > ugen0.1: <0x8086> at usbus0 > uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > [...] > Root mount waiting for: usbus0 > uhub0: 21 ports with 21 removable, self powered > Root mount waiting for: usbus0 > xhci0: Port routing mask set to 0x00000000 > usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) > ugen0.2: at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > > > > At least I'm able to use my USB devices when I disable USB 3.0 in UEFI > BIOS. Then dmesg looks like this: > > ehci0: mem 0xf0424000-0xf04243ff irq > 16 at device 26.0 on pci0 > usbus0: EHCI version 1.0 > usbus0 on ehci0 > [...] > ehci1: mem 0xf0423000-0xf04233ff irq > 23 at device 29.0 on pci0 > usbus1: EHCI version 1.0 > usbus1 on ehci1 > [...] > usbus0: 480Mbps High Speed USB v2.0 > usbus1: 480Mbps High Speed USB v2.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > ugen1.1: at usbus1 > uhub1: on usbus1 > [...] > Root mount waiting for: usbus1 usbus0 > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > Root mount waiting for: usbus1 usbus0 > ugen0.2: at usbus0 > uhub2: > on usbus0 > ugen1.2: at usbus1 > uhub3: > on usbus1 > uhub2: 6 ports with 6 removable, self powered > uhub3: 8 ports with 8 removable, self powered > ugen1.3: at usbus1 > Root mount waiting for: usbus1 > ugen1.4: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x4101 > umass0:6:0:-1: Attached to scbus6 > > > So in EHCI mode everything is running, XHCI fails to attach the devices. > Any suggestions? Hi, Maybe you could try to get some information from the manufacturer, or look at how the ports are wired on the mainboard itself. I tested this a while back in a similar setup, and the command sequence in question can be successfully exercised by the XHCI if no device is connected to the port. I found the when a XHCI port is connected to a real device, some of the initial XHCI commands fail with the invalid parameter error code. This of course is not true, and I think the manufacturer has put some hidden magic there we need to figure out to get this working. --HPS