From owner-freebsd-usb@FreeBSD.ORG Sun Sep 28 04:26:08 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC4F287C for ; Sun, 28 Sep 2014 04:26:08 +0000 (UTC) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FF4ED67 for ; Sun, 28 Sep 2014 04:26:08 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id gq15so16070068lab.25 for ; Sat, 27 Sep 2014 21:26:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=F0FdgfDBiJBXjcZ41JjC1X1Btq0W8qzp+LM/5te3pp0=; b=jBN09nOZcuQjryZ5mRrWlvlNu3jK2uxsLKBIZe3VKsGtI1n5zjw8Qf7/gdl4fZZoPU A38ETqf+rTsK2I3U85Qzd3JRyJZHHFz1AS6ipVH547DgEFGQgkygvxEwdaLEehX7xbvg 7A326eA+afO0RG819oqGKxnMD0hMbmRhfCIy9I4mpUNYmWdA0kDk0C1fpVVKFxtu3h4B sv6XMzOPnXwiHvDlPNW12qz4VNwueZ5aAk0ikqbsiHVFKKQPA6wVF5mDDIOeIAsnqXky Xv3frKcol8wPzF+oVt82Nb+VwY4MOp8vAwk4JIANWReP/yZtUchIaOYGKonMXLkQwa/0 8J2w== MIME-Version: 1.0 X-Received: by 10.112.159.169 with SMTP id xd9mr28984938lbb.71.1411878365116; Sat, 27 Sep 2014 21:26:05 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Sat, 27 Sep 2014 21:26:05 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <5427029B.3060502@selasky.org> References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> Date: Sun, 28 Sep 2014 12:26:05 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 04:26:08 -0000 No lucky. dmesg aslo no change, I could not found "Skipped". Cheers, Huang Wen Hui 2014-09-28 2:31 GMT+08:00 Hans Petter Selasky : > On 09/27/14 20:29, Hans Petter Selasky wrote: > >> Hi, >> >> Can you try the attached patch? >> >> --HPS >> > > === dev/pci/pci.c > ================================================================== > --- dev/pci/pci.c (revision 272064) > +++ dev/pci/pci.c (local) > @@ -3025,7 +3025,10 @@ > /* Update the config register if it changed. */ > if (irq != cfg->intline) { > cfg->intline = irq; > - pci_write_config(dev, PCIR_INTLINE, irq, 1); > + if (irq != 255) > + pci_write_config(dev, PCIR_INTLINE, irq, 1); > + else > + printf("Skipped\n"); > } > > /* Add this IRQ as rid 0 interrupt resource. */ > > From owner-freebsd-usb@FreeBSD.ORG Sun Sep 28 06:35:58 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE70C435 for ; Sun, 28 Sep 2014 06:35:58 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB43B9B5 for ; Sun, 28 Sep 2014 06:35:58 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5D4B71FE022; Sun, 28 Sep 2014 08:35:56 +0200 (CEST) Message-ID: <5427AC46.3040707@selasky.org> Date: Sun, 28 Sep 2014 08:35:50 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 06:35:59 -0000 On 09/28/14 06:26, Huang Wen Hui wrote: > No lucky. dmesg aslo no change, I could not found "Skipped". > > Cheers, > Huang Wen Hui Did you try searching if Linux users had such a problem already? --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Sep 28 07:35:13 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72A8B3F4 for ; Sun, 28 Sep 2014 07:35:13 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9B10E89 for ; Sun, 28 Sep 2014 07:35:12 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id gb8so6983110lab.30 for ; Sun, 28 Sep 2014 00:35:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uBBMHIeyu745TLsep0jXqhLByQOQFyWtN1lqg1r4mBA=; b=rBz42guy22DDmLJRBWqZ/YW71rj7RQpdAvs7TpnQsXaLK4d0ejo0tH4Q/vU1tKOT/y vplC7PatOX9FHPRObD8MbCKnG+XP+tbRxFyI8gGJEF+Y/eORs6428kKCV2MSy8woMyfQ SmKmP5oVfXLg6KgwF//rfdp13+Q+wmCN3QWlHaCsI6XtewnpLzc3YxTJxZQlyFsllbXP oT3zN/ZQq+KvLBn2Cr0ZaGfcB25EP3R8JO1b9ABKTCTPsuq6aNRXr0nmrCzPVBv6VMNs zbIylgCY0dxvE5/szqB0EiEMIyeVh31GqWHamuWNqMU2oWH3XTh6VTqIWkViZz4eiPKQ I3ZA== MIME-Version: 1.0 X-Received: by 10.152.4.165 with SMTP id l5mr31664816lal.49.1411889710794; Sun, 28 Sep 2014 00:35:10 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Sun, 28 Sep 2014 00:35:10 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <5427AC46.3040707@selasky.org> References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> <5427AC46.3040707@selasky.org> Date: Sun, 28 Sep 2014 15:35:10 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 07:35:13 -0000 I found some similar problem of Linux: https://bugzilla.kernel.org/show_bug.cgi?id=52591 https://lkml.org/lkml/2013/3/9/134 2014-09-28 14:35 GMT+08:00 Hans Petter Selasky : > On 09/28/14 06:26, Huang Wen Hui wrote: > >> No lucky. dmesg aslo no change, I could not found "Skipped". >> >> Cheers, >> Huang Wen Hui >> > > Did you try searching if Linux users had such a problem already? > > --HPS > > From owner-freebsd-usb@FreeBSD.ORG Mon Sep 29 11:13:27 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 106B3446 for ; Mon, 29 Sep 2014 11:13:27 +0000 (UTC) Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D399A954 for ; Mon, 29 Sep 2014 11:13:26 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id wo20so12408809obc.26 for ; Mon, 29 Sep 2014 04:13:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=/OuuqBHP8yauxzrE5I+8869m4l/6ftE+l/v9gZf/0eQ=; b=cIz5pzASI6kX8beruLFwr47QsNFjR0FCBNOYO1IdSzR/jsUqrmfxJeHTm7/IqMvmyX wEoULUdKdk03b3fsv9s2s2nh96UreU4u0l7wKQz/hif47ewYAk04LD+ZFEd/VJf56X/A CdYT4t8a1QCjumnnga8B3/Tv4ZXYn0E/50vSCZ0OTaRIYscV4EnGajEcKRdUlHFETvG8 CiGu7crErvKSFK3pEIC61fO4mlpGBQJ1e68kdl6Bgq2UqxWy32TyyZ5J+O/v+XKuAeNR lB2VBZxL5tmEFbzD9C3O7/1LoEdnlqarr1pYbOzg5F7Emx0CBPGxHwrq5rw640MHYsQl oKWA== MIME-Version: 1.0 X-Received: by 10.60.176.169 with SMTP id cj9mr31202864oec.21.1411989206139; Mon, 29 Sep 2014 04:13:26 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.202.58.196 with HTTP; Mon, 29 Sep 2014 04:13:26 -0700 (PDT) Date: Mon, 29 Sep 2014 13:13:26 +0200 X-Google-Sender-Auth: oNQgehEk-QWvI6ht9atd275wMZ4 Message-ID: Subject: USB EHCI Host/HUB problems on HP EliteBook 2740p From: CeDeROM To: "freebsd-usb@FreeBSD.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 11:13:27 -0000 Hello :-) I have found USB EHCI Controller / HUB on HP EliteBook 2740p to be problematic. First I was not able to boot the installer from USB memory - it hung at booloader stage / kernel load randomly. Now I have problem with Unitek 10/100 Ethernet adapter USB 2.0 - it seems to crash USB hub, but it works fine on other machines and when I connect via external USB 2.0 HUB. Please advise :-) Tomek --- Extract from DMESG --- FreeBSD 10.0-RELEASE-p9 #0: Tue Sep 23 17:43:02 CEST 2014 root@orion:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz (2527.07-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x20655 Family = 0x6 Model = 0x25 Stepping = 5 Features=0xbfebfbff Features2=0x29ae3ff AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8049582080 (7676 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: ... ehci0: mem 0xd4729000-0xd47293ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 ... ehci1: mem 0xd4728000-0xd47283ff irq 20 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 ... --- What happens if I attach this USB Ethernet adapter directly to the computer --- uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished uhub_reattach_port: giving up port reset - device vanished % usbconfig ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (98mA) ugen1.4: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA) --- What happens if I attach USB Ethernet adapter via USB 2.0 HUB --- ugen1.5: at usbus1 axe0: on usbus1 miibus0: on axe0 rgephy0: PHY 2 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow ue0: on axe0 ue0: Ethernet address: 00:23:54:5c:11:85 ue0: link state changed to DOWN % usbconfig ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (98mA) ugen1.4: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA) ugen1.5: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (250mA) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-usb@FreeBSD.ORG Mon Sep 29 17:49:10 2014 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43672147; Mon, 29 Sep 2014 17:49:10 +0000 (UTC) Received: from acme.spoerlein.net (unknown [IPv6:2a02:2528:fa:1000::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.spoerlein.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1767C8A; Mon, 29 Sep 2014 17:49:09 +0000 (UTC) Received: from localhost (coyote.spoerlein.net [IPv6:2001:1620:b6e::151]) by acme.spoerlein.net (8.14.9/8.14.9) with ESMTP id s8THn5L9041990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Sep 2014 19:49:06 +0200 (CEST) (envelope-from uqs@FreeBSD.org) Date: Mon, 29 Sep 2014 19:49:04 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: freebsd-usb@FreeBSD.org, hselasky@FreeBSD.org Subject: CEC device not attaching to xHCI port Message-ID: <20140929174904.GA15642@coyote.spoerlein.net> Mail-Followup-To: freebsd-usb@FreeBSD.org, hselasky@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 17:49:10 -0000 Hi, I got a CEC adapter using libCEC to bridge the gap between my XBMC and TV. The device works fine *if* I plug it into the front ports (which is a bit ugly, so I was wondering why this is not working on the other USB hub). Non-working: ugen0.2: at usbus0 (disconnected) root@coyote:~# usbconfig -u 0 -a 1 ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) Working: ugen1.4: at usbus1 ums0: on usbus1 ums0: 3 buttons and [XY] coordinates ID=0 umodem0: on usbus1 umodem0: data interface 1, has CM over data, has break root@coyote:~# usbconfig -u 1 -a 4 ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (10mA) The hubs: root@coyote:~# pciconf -l -v xhci0 xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x1e318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB root@coyote:~# pciconf -l -v ehci0 ehci0@pci0:0:26:0: class=0x0c0320 card=0x72708086 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB Enhanced Host Controller' class = serial bus subclass = USB This is on 10.1-BETA1 and I found this post and workaround, which seem to be relevant: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2013-02/msg00701.html But I haven't rebooted yet with hw.usb.xhci.xhci_port_route -1 Any more info you'd require on this? Should I file a PR to track this? Cheers, Uli From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 05:47:24 2014 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EFA3C18 for ; Tue, 30 Sep 2014 05:47:24 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1BFDDDB for ; Tue, 30 Sep 2014 05:47:23 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6ADF71FE022 for ; Tue, 30 Sep 2014 07:47:20 +0200 (CEST) Message-ID: <542A43E4.5020103@selasky.org> Date: Tue, 30 Sep 2014 07:47:16 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-usb@FreeBSD.org Subject: Re: CEC device not attaching to xHCI port References: <20140929174904.GA15642@coyote.spoerlein.net> In-Reply-To: <20140929174904.GA15642@coyote.spoerlein.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 05:47:24 -0000 On 09/29/14 19:49, Ulrich Spörlein wrote: > Hi, > > I got a CEC adapter using libCEC to bridge the gap between my XBMC and > TV. The device works fine *if* I plug it into the front ports (which is > a bit ugly, so I was wondering why this is not working on the other USB > hub). > > Non-working: > ugen0.2: at usbus0 (disconnected) > root@coyote:~# usbconfig -u 0 -a 1 > ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) Hi, Can you enable: hw.usb.uhub.debug=15 for the failing case? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 10:19:53 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43EE5E25 for ; Tue, 30 Sep 2014 10:19:53 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA83BDB for ; Tue, 30 Sep 2014 10:19:52 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id l4so306249lbv.38 for ; Tue, 30 Sep 2014 03:19:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VUEZg+9u9QE4XH2YR1eX0VAxwNsUkJbddgCMCIG2/TE=; b=aWJ6NUEGNxVU7/TIwjGqAnltP4VNFrwOUT9Igl3C3TX8+Jd072NaJmR9AfJiOunQ8v 18qR2n83WooxGNc0P883+kAYoF2q3sZrTTXzIS8En4lfcJmMnJC9K/vy7nCCKTLRK/N3 xyq18DGdsLKVLmdolSjN28/qwcswXiMr5+8ghMJ3b9fNFSe1e1PgGgBTz71mpNY2ohAz A/0blF/BEPDa9ohAnGz667eoIo3EqYWLM4UhZXVt6MSRSNh6TQEe8+J2eI6K6zEcfD/7 js51dUbwZCgxI8dqS4ypVXzEMKWowBJQVTqx6KS4GJWdEQGeiklGwyjyUdiUw8eJZ1Yn PE4g== MIME-Version: 1.0 X-Received: by 10.112.182.42 with SMTP id eb10mr44001163lbc.7.1412072390445; Tue, 30 Sep 2014 03:19:50 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Tue, 30 Sep 2014 03:19:50 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> <5427AC46.3040707@selasky.org> Date: Tue, 30 Sep 2014 18:19:50 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 10:19:53 -0000 Hi, I got the exactly same MBP 2013 11,3 from my colleague, also same time to buy it. USB driver works on this in UEFI mode. Both xhci and ehci found in this mac, and these dmesg only show in this mac: acpi_ec0: port 0x62,0x66 on acpi0 ACPI Error: No handler for Region [CMS0] (0xfffff80008948e00) [SystemCMOS] (20130823/evregion-178) ACPI Error: Region SystemCMOS (ID=5) has no handler (20130823/exfldio-320) ACPI Error: Method parse/execution failed [\134RUSB] (Node 0xfffff8000895db80), AE_NOT_EXIST (20130823/psparse-553) ACPI Error: Method parse/execution failed [\134_SB_._INI] (Node 0xfffff8000895e000), AE_NOT_EXIST (20130823/psparse-553) acpi0: Power Button (fixed) ... xhci0: mem 0xc1e00000-0xc1e0ffff at device 20.0 on pci0 xhci0: 32 byte context size. xhci0: Port routing mask set to 0xffffffff usbus0 on xhci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xc1e19400-0xc1e197ff at device 26.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 ... ehci1: mem 0xc1e19000-0xc1e193ff at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ... usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ... Timecounter "TSC-low" frequency 1297021897 Hz quality 1000 Root mount waiting for: usbus2 usbus1 usbus0 uhub1: 2 ports with 2 removable, self powered uhub0: 21 ports with 21 removable, self powered uhub2: 2 ports with 2 removable, self powered Root mount waiting for: usbus2 usbus1 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 ugen1.2: at usbus1 uhub3: on usbus1 ugen2.2: at usbus2 uhub4: on usbus2 uhub3: 6 ports with 6 removable, self powered Root mount waiting for: usbus2 usbus1 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 uhub4: 8 ports with 8 removable, self powered ugen1.3: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4101 umass0:1:0:-1: Attached to scbus1 da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: Removable Direct Access SCSI-4 device da0: Serial Number E0629276 da0: 40.000MB/s transfers da0: 3870MB (7925760 512 byte sectors: 255H 63S/T 493C) da0: quirks=0x2 ugen1.4: at usbus1 uhub5: on usbus1 Root mount waiting for: usbus1 uhub5: 3 ports with 0 removable, self powered ugen1.5: at usbus1 ukbd0: on usbus1 kbd1 at ukbd0 Root mount waiting for: usbus1 ugen1.6: at usbus1 ugen1.7: at usbus1 Root mount waiting for: usbus1 ugen1.8: at usbus1 ukbd1: on usbus1 Root mount waiting for: usbus1 kbd2 at ukbd1 Full dmesg is http://sw.gddsn.org.cn/freebsd/uefi-ehci-dmesg.txt 2014-09-28 15:35 GMT+08:00 Huang Wen Hui : > I found some similar problem of Linux: > https://bugzilla.kernel.org/show_bug.cgi?id=52591 > https://lkml.org/lkml/2013/3/9/134 > > > 2014-09-28 14:35 GMT+08:00 Hans Petter Selasky : > >> On 09/28/14 06:26, Huang Wen Hui wrote: >> >>> No lucky. dmesg aslo no change, I could not found "Skipped". >>> >>> Cheers, >>> Huang Wen Hui >>> >> >> Did you try searching if Linux users had such a problem already? >> >> --HPS >> >> > From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 11:23:35 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B27BCF4D for ; Tue, 30 Sep 2014 11:23:35 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71AB2A19 for ; Tue, 30 Sep 2014 11:23:34 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id EA0A51FE022; Tue, 30 Sep 2014 13:23:31 +0200 (CEST) Message-ID: <542A92AF.8040606@selasky.org> Date: Tue, 30 Sep 2014 13:23:27 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com, "freebsd-usb@freebsd.org" Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 11:23:35 -0000 Hi, Can you get output from "pciconf -lv" from the non-working MBP, in both UEFI and BIOS mode? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 12:25:36 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E73E9778 for ; Tue, 30 Sep 2014 12:25:36 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6FCF6174 for ; Tue, 30 Sep 2014 12:25:36 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id gb8so10261224lab.2 for ; Tue, 30 Sep 2014 05:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=E83jkB1w9gkSCFNn6ZqdqN58E7MDiii4b18BgtPB5vw=; b=vwlvJMEjP+IZ5qvjlwqU/vy86oT7T3MX3CU+jGR0xvC4vTkOAXPgYb9jHulYbTaQHv BWaiSQLTm0seYK/emOfTZLQSzhOeRB7cIa7fgpEP44bpjTNKzjPcu518UJSdnAnK9e6F Zx7qPm/lmEsh9LqvyZ75QL+W2dAFLtJgwK2LtBYd086doPSu8wsjXfr+1yru6v0jTDHI gdevYl20ikXVL+ZDQWYXs8f0Ght0zPiJXsubGZKV4yOvFVv1UOwEh1ObEyHhVe7kUfP7 /KhYhseu7u7Akb3K3O+1zHKYob/Ck/FfVfNogALYyJBhEjndfToWvvGP1EhhCQrHeJTm 3jWw== MIME-Version: 1.0 X-Received: by 10.112.25.65 with SMTP id a1mr44603998lbg.85.1412079933406; Tue, 30 Sep 2014 05:25:33 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Tue, 30 Sep 2014 05:25:33 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <542A92AF.8040606@selasky.org> References: <542A92AF.8040606@selasky.org> Date: Tue, 30 Sep 2014 20:25:33 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 12:25:37 -0000 Exactly same: http://sw.gddsn.org.cn/freebsd/non-working-mac-bios-pciconf.txt http://sw.gddsn.org.cn/freebsd/non-working-mac-uefi-pciconf.txt and working-mac: http://sw.gddsn.org.cn/freebsd/working-mac-bios-pciconf.txt http://sw.gddsn.org.cn/freebsd/working-mac-uefi-pciconf.txt 2014-09-30 19:23 GMT+08:00 Hans Petter Selasky : > Hi, > > Can you get output from "pciconf -lv" from the non-working MBP, in both > UEFI and BIOS mode? > > --HPS > From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 12:50:38 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D849EE4 for ; Tue, 30 Sep 2014 12:50:38 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF15F65E for ; Tue, 30 Sep 2014 12:50:37 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id DEDDF1FE022; Tue, 30 Sep 2014 14:50:34 +0200 (CEST) Message-ID: <542AA716.3070701@selasky.org> Date: Tue, 30 Sep 2014 14:50:30 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <542A92AF.8040606@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 12:50:38 -0000 On 09/30/14 14:25, Huang Wen Hui wrote: > Exactly same: > http://sw.gddsn.org.cn/freebsd/non-working-mac-bios-pciconf.txt > http://sw.gddsn.org.cn/freebsd/non-working-mac-uefi-pciconf.txt > > > and working-mac: > http://sw.gddsn.org.cn/freebsd/working-mac-bios-pciconf.txt > http://sw.gddsn.org.cn/freebsd/working-mac-uefi-pciconf.txt > > 2014-09-30 19:23 GMT+08:00 Hans Petter Selasky : > >> Hi, >> >> Can you get output from "pciconf -lv" from the non-working MBP, in both >> UEFI and BIOS mode? >> >> --HPS >> > Hi, It looks like you are missing an EHCI controller. What happens if you boot having: hw.pci.do_power_nodriver=1 In /boot/loader.conf ? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 13:10:45 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17EF848C for ; Tue, 30 Sep 2014 13:10:45 +0000 (UTC) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9348296A for ; Tue, 30 Sep 2014 13:10:44 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id gq15so186525lab.38 for ; Tue, 30 Sep 2014 06:10:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=BP21ud+BtYPCq6ufPoPg/X23oXOkwcE2X3E2xfkaCkU=; b=heVzyQKJAmQsoxwB6n2eOb/2M/7NJqPE5SNr3+E9DjCkhvnFxVRefusfTD8Xt8DL+l tm7K4Wyhn8McR3DWEjwqlH8OiuoDv5W+0LsmubXnpU84PyL5Fhuwgvdw8hwI0yvQQr07 gtPs+L02x4gmZnLrHztldWPYEp2tO3SIWcWIq2haTjd83v+BIRc4g5FyQ5rHnTwLWhvm /1AnGbK4FzLVYKRhstT1cglz1GlhUNAazHe7omxPbqGMQAdf7p7am4KQAKRwCbgfCb8H axg9CLLTJw3Gzcqab2HuTT4UFTBftDvYtdYq2OtlCPF9klWO0xAzI5BA67Ee6M0FgxlR Wv3g== MIME-Version: 1.0 X-Received: by 10.152.44.136 with SMTP id e8mr47640999lam.36.1412082642512; Tue, 30 Sep 2014 06:10:42 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Tue, 30 Sep 2014 06:10:42 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <542AA716.3070701@selasky.org> References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> Date: Tue, 30 Sep 2014 21:10:42 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 13:10:45 -0000 Hi, Both bios and uefi are same as before. I never see EHCI controller from dmesg when I got this MBP:( Thanks, Huang Wen Hui 2014-09-30 20:50 GMT+08:00 Hans Petter Selasky : > On 09/30/14 14:25, Huang Wen Hui wrote: > >> Exactly same: >> http://sw.gddsn.org.cn/freebsd/non-working-mac-bios-pciconf.txt >> http://sw.gddsn.org.cn/freebsd/non-working-mac-uefi-pciconf.txt >> >> >> and working-mac: >> http://sw.gddsn.org.cn/freebsd/working-mac-bios-pciconf.txt >> http://sw.gddsn.org.cn/freebsd/working-mac-uefi-pciconf.txt >> >> 2014-09-30 19:23 GMT+08:00 Hans Petter Selasky : >> >> Hi, >>> >>> Can you get output from "pciconf -lv" from the non-working MBP, in both >>> UEFI and BIOS mode? >>> >>> --HPS >>> >>> >> > Hi, > > It looks like you are missing an EHCI controller. > > What happens if you boot having: > > hw.pci.do_power_nodriver=1 > > In /boot/loader.conf ? > > --HPS > From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 13:23:53 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7745E9E3 for ; Tue, 30 Sep 2014 13:23:53 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 313B0AF0 for ; Tue, 30 Sep 2014 13:23:52 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id DD1711FE022; Tue, 30 Sep 2014 15:23:50 +0200 (CEST) Message-ID: <542AAEE2.70206@selasky.org> Date: Tue, 30 Sep 2014 15:23:46 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 13:23:53 -0000 On 09/30/14 15:10, Huang Wen Hui wrote: > Hi, > > Both bios and uefi are same as before. > > I never see EHCI controller from dmesg when I got this MBP:( > > Thanks, > > Huang Wen Hui Can you try the attached patch for xhci.c ? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 13:50:15 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D2586E5 for ; Tue, 30 Sep 2014 13:50:15 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8725CE0B for ; Tue, 30 Sep 2014 13:50:14 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id gi9so9898567lab.17 for ; Tue, 30 Sep 2014 06:50:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NfNURJ1sDIh7n6onx2cObVtzdh86AoAlKqxlkNplJuw=; b=QutJJfDbhwEL8j1zkBuxqPJDZ88T1H9cdgKZ0w9V5iIRPWq6dLkkPWB5jtoMBZj/4P 3p2ndxA0JinpVe2pz0k+bDmL8Z6t4MqS9z4ITAsk55g0juYQ9JZ+ftVjLsURnwV+GQup 3I9EG0Ui5cUlNy0V+C7sK6h/Bfcx8NtNtDVQd9uPWMdlHU+A0P1xD2N7vyMsDsMU4z08 YadBGC64pKiEAwA1h2CY9hG4X2kxU9CVvNoxOIPq9uteNrIQiKltAWFmxucN265l4P9M WnPHdIMb/og+LLg3hF1kieKbnndGT2WOTYvFNI3MJsIyHRWGsRJySv58yRnhDi5Uu1Gy rNjw== MIME-Version: 1.0 X-Received: by 10.112.142.104 with SMTP id rv8mr43352972lbb.59.1412085010196; Tue, 30 Sep 2014 06:50:10 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Tue, 30 Sep 2014 06:50:10 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <542AAEE2.70206@selasky.org> References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> Date: Tue, 30 Sep 2014 21:50:10 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 13:50:15 -0000 I manually patch on STABLE, Both bios and uefi still are same as before:( 2014-09-30 21:23 GMT+08:00 Hans Petter Selasky : > On 09/30/14 15:10, Huang Wen Hui wrote: > >> Hi, >> >> Both bios and uefi are same as before. >> >> I never see EHCI controller from dmesg when I got this MBP:( >> >> Thanks, >> >> Huang Wen Hui >> > > Can you try the attached patch for xhci.c ? > > --HPS > > From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 13:52:20 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F472827 for ; Tue, 30 Sep 2014 13:52:20 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09AB8E2C for ; Tue, 30 Sep 2014 13:52:20 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 7A7FF1FE022; Tue, 30 Sep 2014 15:52:17 +0200 (CEST) Message-ID: <542AB58D.9080602@selasky.org> Date: Tue, 30 Sep 2014 15:52:13 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 13:52:20 -0000 On 09/30/14 15:50, Huang Wen Hui wrote: > I manually patch on STABLE, Both bios and uefi still are same as before:( > Hi, Can you get verbose dmesg with patch, hw.usb.xhci.debug=16 in /boot/loader.conf ? Also set: hw.usb.xhci.use_polling=1 in /boot/loader.conf Thank you! --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Sep 30 14:12:58 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA13C494 for ; Tue, 30 Sep 2014 14:12:57 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F5B4101 for ; Tue, 30 Sep 2014 14:12:57 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id f15so6604482lbj.11 for ; Tue, 30 Sep 2014 07:12:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=B3MUUcXd1/TFVkRRY5eK7/ENabi27J98nyUz4PufQj8=; b=RfqwEZjIFRvO69Ikf7y0s1bvYTNK6Rn68GYhFxUJg1kZShNAJsKdFQE2TjZ/pGSvUv vQ7WbqbrdmQ26zdA/qSKfZS3ZgVEj26NmhrBAxAUB/caPKApY/KWoON+1z2Zyl9xdCQm XqyJJP3vubjYEvZ6FlD5XOCoQ8gb92l4h+RWo4kguGSMBVGZ3oqugT+gOVsuxjOk7SOR n2hyEh/8UI4bDWOx9le1MaNNi5rcR5pPDFqqs+3iNqOrdmlDhUlwmaIuRAfX+3U3qHA9 z8411FIGc+tqL/E5DV+EUw0OUwf+t6JTXqpK+32JbupKbQ2c2xNSJutNhGR5XIoqENj0 YXgQ== MIME-Version: 1.0 X-Received: by 10.152.170.167 with SMTP id an7mr11688931lac.94.1412086375449; Tue, 30 Sep 2014 07:12:55 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Tue, 30 Sep 2014 07:12:55 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <542AB58D.9080602@selasky.org> References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> <542AB58D.9080602@selasky.org> Date: Tue, 30 Sep 2014 22:12:55 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 14:12:58 -0000 http://sw.gddsn.org.cn/freebsd/hps-bios-message.txt http://sw.gddsn.org.cn/freebsd/hps-uefi-message.txt 2014-09-30 21:52 GMT+08:00 Hans Petter Selasky : > On 09/30/14 15:50, Huang Wen Hui wrote: > >> I manually patch on STABLE, Both bios and uefi still are same as before:( >> >> > Hi, > > Can you get verbose dmesg with patch, hw.usb.xhci.debug=16 in > /boot/loader.conf ? > > Also set: hw.usb.xhci.use_polling=1 in /boot/loader.conf > > Thank you! > > --HPS > > From owner-freebsd-usb@FreeBSD.ORG Wed Oct 1 06:34:18 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 641F481C for ; Wed, 1 Oct 2014 06:34:18 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E513D4E for ; Wed, 1 Oct 2014 06:34:18 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id EE5641FE023; Wed, 1 Oct 2014 08:34:15 +0200 (CEST) Message-ID: <542BA063.3060105@selasky.org> Date: Wed, 01 Oct 2014 08:34:11 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> <542AB58D.9080602@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 06:34:18 -0000 On 09/30/14 16:12, Huang Wen Hui wrote: > http://sw.gddsn.org.cn/freebsd/hps-bios-message.txt > http://sw.gddsn.org.cn/freebsd/hps-uefi-message.txt > Hi, Can you try the attached patch again, and send verbose dmesg including xhci debug on? --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Oct 1 07:24:07 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 366E58AA for ; Wed, 1 Oct 2014 07:24:07 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFC16327 for ; Wed, 1 Oct 2014 07:24:06 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id l4so202902lbv.24 for ; Wed, 01 Oct 2014 00:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=h+OdMthBUrziNkxo63OlmWmL2RkU4M1uJBYk8uw9a+4=; b=DUubcX4Rli0B/WS+4WwjlvnPYcvBVaOae8uNZEI/iqBl9AAem63R9c/pazH1eYVLI4 sZI/Pt6PTPLnWvXxnRnk/CoB8VAqOOeb+OP+f6r27+wdSExWYfeOIAoq0k9uFTwbFOvb A2gb9Vcxim4y/t9/D+c2L/gFSIE6aYFL1ak7fUyxuRhdUwTpN+iUKaJ8uzt/s2XEYwOe xS4BkCgyxevojuCMM0cJvqluMrr2RFVhTOa1uz/7R8vN417+ugin/MLn7Ctn//5iyZgs 7AZ7/73wsS25/uN1TPWaX7gWgIVaOUfbZvtPFHncbkYyD2ZezAPr5odcN4wuTVZ0kuII RTTw== MIME-Version: 1.0 X-Received: by 10.112.128.135 with SMTP id no7mr49564603lbb.74.1412148244645; Wed, 01 Oct 2014 00:24:04 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Wed, 1 Oct 2014 00:24:04 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: <542BA063.3060105@selasky.org> References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> <542AB58D.9080602@selasky.org> <542BA063.3060105@selasky.org> Date: Wed, 1 Oct 2014 15:24:04 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 07:24:07 -0000 verbose dmesg with patch, hw.usb.xhci.debug=16 and hw.usb.xhci.use_polling=1 http://sw.gddsn.org.cn/freebsd/hps-bios-message2.txt http://sw.gddsn.org.cn/freebsd/hps-uefi-message2.txt 2014-10-01 14:34 GMT+08:00 Hans Petter Selasky : > On 09/30/14 16:12, Huang Wen Hui wrote: > >> http://sw.gddsn.org.cn/freebsd/hps-bios-message.txt >> http://sw.gddsn.org.cn/freebsd/hps-uefi-message.txt >> >> > Hi, > > Can you try the attached patch again, and send verbose dmesg including > xhci debug on? > > --HPS > > From owner-freebsd-usb@FreeBSD.ORG Wed Oct 1 07:30:24 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A58C96C for ; Wed, 1 Oct 2014 07:30:24 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07E7D374 for ; Wed, 1 Oct 2014 07:30:24 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id F3B631FE023; Wed, 1 Oct 2014 09:30:21 +0200 (CEST) Message-ID: <542BAD89.60508@selasky.org> Date: Wed, 01 Oct 2014 09:30:17 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <542A92AF.8040606@selasky.org> <542AA716.3070701@selasky.org> <542AAEE2.70206@selasky.org> <542AB58D.9080602@selasky.org> <542BA063.3060105@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 07:30:24 -0000 On 10/01/14 09:24, Huang Wen Hui wrote: > verbose dmesg with patch, hw.usb.xhci.debug=16 and hw.usb.xhci.use_polling=1 > > http://sw.gddsn.org.cn/freebsd/hps-bios-message2.txt > http://sw.gddsn.org.cn/freebsd/hps-uefi-message2.txt > Hi, Can you join #bsdusb on EF-net? BTW: Why are the time-stamps so different in the two logs above? --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Oct 2 12:06:13 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11027B3E for ; Thu, 2 Oct 2014 12:06:13 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECB22802 for ; Thu, 2 Oct 2014 12:06:12 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s92C6Ck0091523 for ; Thu, 2 Oct 2014 12:06:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 194091] New: Add support for long range USB wireless adapter Alpha AWUS036NHRv2 Date: Thu, 02 Oct 2014 12:06:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: olivier@cochard.me X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 12:06:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194091 Bug ID: 194091 Summary: Add support for long range USB wireless adapter Alpha AWUS036NHRv2 Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: olivier@cochard.me Created attachment 147911 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147911&action=edit patch for AWUS036NHR v2 Here is the patch (simply new USB ID added and man page update). -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@FreeBSD.ORG Thu Oct 2 12:27:55 2014 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4576BB8 for ; Thu, 2 Oct 2014 12:27:55 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D37CA68 for ; Thu, 2 Oct 2014 12:27:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s92CRtVD010270 for ; Thu, 2 Oct 2014 12:27:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 194091] Add support for long range USB wireless adapter Alpha AWUS036NHRv2 Date: Thu, 02 Oct 2014 12:27:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 12:27:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194091 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: hselasky Date: Thu Oct 2 12:27:43 UTC 2014 New revision: 272410 URL: https://svnweb.freebsd.org/changeset/base/272410 Log: Add new USB ID. PR: 194091 MFC after: 3 days Changes: head/share/man/man4/urtwn.4 head/sys/dev/usb/usbdevs head/sys/dev/usb/wlan/if_urtwn.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 03:55:05 2014 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45933D29 for ; Fri, 3 Oct 2014 03:55:05 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC085DDD for ; Fri, 3 Oct 2014 03:55:04 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id p9so339813lbv.7 for ; Thu, 02 Oct 2014 20:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=G7sHnYKsv1XBXFnV1lYNCkQX9qWXw4+eK+br2dxNhy8=; b=MVoumei2Pp1bTaHIoFzDIsXfv1dhFGdvsTuKN4jRWOFpAHdjAtRB4G7RSE40vBBOHM KOvrYqc5ISanLgi+eejFcRlrTWndAchWOs0+gW0luRqwSkdgGzc97hPlsAsMD9l1hJBm BSP+nGGY93Io09fr2Tk1/SSD8W/2lUAbA6tQWlQFd2cWGIxRkxKhENeyAJW7OgnNZkXF oGiSA2R/kbTYiHqvwQN8QPS+qIs0NSrNW4xHbpXc3G3R/1w51siDF+tJGGei+lnd/wL+ JMCAB8amd32ZCecrhlM7VviAmo0sSbswTB2t+Q7iHvUf2u3SkF15J//NLYJ56k8MZDJy 6KJw== MIME-Version: 1.0 X-Received: by 10.112.55.7 with SMTP id n7mr2781379lbp.16.1412308502428; Thu, 02 Oct 2014 20:55:02 -0700 (PDT) Received: by 10.112.218.101 with HTTP; Thu, 2 Oct 2014 20:55:02 -0700 (PDT) Reply-To: huanghwh@gmail.com In-Reply-To: References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> <5427AC46.3040707@selasky.org> Date: Fri, 3 Oct 2014 11:55:02 +0800 Message-ID: Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 From: Huang Wen Hui To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 03:55:05 -0000 I found that how to connect EHCI controller, use "bless" command in MacOSX with --legacy option: 1. open MacOSX terminal, mkdir /Volumes/EFI 2. mount -t msdos /dev/disk0s1 /Volumes/EFI 3. bless --setBoot --mount /Volumes/EFI --legacy 4. reboot MacOSX, press "option" key, you can feel firmware start a little slow than without --legacy. I think firmware do some extra things:( 5. select both UEFI and BIOS boot FreeBSD, system can connect EHCI and XHCI controller. 6. I think BootCamp assistant also add --legacy option. Cheers, Huang Wen Hui 2014-09-30 18:19 GMT+08:00 Huang Wen Hui : > Hi, > I got the exactly same MBP 2013 11,3 from my colleague, also same time to > buy it. > USB driver works on this in UEFI mode. Both xhci and ehci found in this > mac, and these > dmesg only show in this mac: > > acpi_ec0: port 0x62,0x66 on acpi0 > ACPI Error: No handler for Region [CMS0] (0xfffff80008948e00) [SystemCMOS] > (20130823/evregion-178) > ACPI Error: Region SystemCMOS (ID=5) has no handler (20130823/exfldio-320) > ACPI Error: Method parse/execution failed [\134RUSB] (Node > 0xfffff8000895db80), AE_NOT_EXIST (20130823/psparse-553) > ACPI Error: Method parse/execution failed [\134_SB_._INI] (Node > 0xfffff8000895e000), AE_NOT_EXIST (20130823/psparse-553) > acpi0: Power Button (fixed) > ... > xhci0: mem 0xc1e00000-0xc1e0ffff at > device 20.0 on pci0 > xhci0: 32 byte context size. > xhci0: Port routing mask set to 0xffffffff > usbus0 on xhci0 > pci0: at device 22.0 (no driver attached) > ehci0: mem > 0xc1e19400-0xc1e197ff at device 26.0 on pci0 > usbus1: EHCI version 1.0 > usbus1 on ehci0 > ... > ehci1: mem > 0xc1e19000-0xc1e193ff at device 29.0 on pci0 > usbus2: EHCI version 1.0 > usbus2 on ehci1 > isab0: at device 31.0 on pci0 > isa0: on isab0 > ... > usbus0: 5.0Gbps Super Speed USB v3.0 > usbus1: 480Mbps High Speed USB v2.0 > usbus2: 480Mbps High Speed USB v2.0 > ugen0.1: <0x8086> at usbus0 > uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > ugen1.1: at usbus1 > uhub1: on usbus1 > ugen2.1: at usbus2 > uhub2: on usbus2 > ... > Timecounter "TSC-low" frequency 1297021897 Hz quality 1000 > Root mount waiting for: usbus2 usbus1 usbus0 > uhub1: 2 ports with 2 removable, self powered > uhub0: 21 ports with 21 removable, self powered > uhub2: 2 ports with 2 removable, self powered > Root mount waiting for: usbus2 usbus1 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 > ugen1.2: at usbus1 > uhub3: on > usbus1 > ugen2.2: at usbus2 > uhub4: on > usbus2 > uhub3: 6 ports with 6 removable, self powered > Root mount waiting for: usbus2 usbus1 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 > uhub4: 8 ports with 8 removable, self powered > ugen1.3: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x4101 > umass0:1:0:-1: Attached to scbus1 > da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 > da0: Removable Direct Access SCSI-4 device > da0: Serial Number E0629276 > da0: 40.000MB/s transfers > da0: 3870MB (7925760 512 byte sectors: 255H 63S/T 493C) > da0: quirks=0x2 > ugen1.4: at usbus1 > uhub5: on > usbus1 > Root mount waiting for: usbus1 > uhub5: 3 ports with 0 removable, self powered > ugen1.5: at usbus1 > ukbd0: on > usbus1 > kbd1 at ukbd0 > Root mount waiting for: usbus1 > ugen1.6: at usbus1 > ugen1.7: at usbus1 > Root mount waiting for: usbus1 > ugen1.8: at usbus1 > ukbd1: on usbus1 > Root mount waiting for: usbus1 > kbd2 at ukbd1 > > Full dmesg is http://sw.gddsn.org.cn/freebsd/uefi-ehci-dmesg.txt > > > > > 2014-09-28 15:35 GMT+08:00 Huang Wen Hui : > >> I found some similar problem of Linux: >> https://bugzilla.kernel.org/show_bug.cgi?id=52591 >> https://lkml.org/lkml/2013/3/9/134 >> >> >> 2014-09-28 14:35 GMT+08:00 Hans Petter Selasky : >> >>> On 09/28/14 06:26, Huang Wen Hui wrote: >>> >>>> No lucky. dmesg aslo no change, I could not found "Skipped". >>>> >>>> Cheers, >>>> Huang Wen Hui >>>> >>> >>> Did you try searching if Linux users had such a problem already? >>> >>> --HPS >>> >>> >> > From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 06:15:41 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00BC38BF for ; Fri, 3 Oct 2014 06:15:40 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA79FBE3 for ; Fri, 3 Oct 2014 06:15:39 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 355951FE023; Fri, 3 Oct 2014 08:15:36 +0200 (CEST) Message-ID: <542E3F02.4050401@selasky.org> Date: Fri, 03 Oct 2014 08:15:30 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: huanghwh@gmail.com Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> <5427AC46.3040707@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 06:15:41 -0000 On 10/03/14 05:55, Huang Wen Hui wrote: > I found that how to connect EHCI controller, use "bless" command in MacOSX > with --legacy option: > 1. open MacOSX terminal, mkdir /Volumes/EFI > 2. mount -t msdos /dev/disk0s1 /Volumes/EFI > 3. bless --setBoot --mount /Volumes/EFI --legacy > 4. reboot MacOSX, press "option" key, you can feel firmware start a little > slow than without --legacy. I think firmware do some extra things:( > 5. select both UEFI and BIOS boot FreeBSD, system can connect EHCI and XHCI > controller. > 6. I think BootCamp assistant also add --legacy option. > > Cheers, > Huang Wen Hui Hi, Sounds good! Thanks for figuring this out. At least I found one or two minors in the XHCI driver while debugging this :-) --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 06:44:10 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 098B3AEB for ; Fri, 3 Oct 2014 06:44:10 +0000 (UTC) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C9F2EE0A for ; Fri, 3 Oct 2014 06:44:09 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id fa1so1050250pad.33 for ; Thu, 02 Oct 2014 23:44:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=lxD3WwTdsmzAimNsp2IjKt397r5bKKqyvabj9k8VRxk=; b=X40LIoFiIqA1FTMk6QiwFgIbmIyBGLlGyeYCwXwrGOIEhG2jqlsdj4APQpiKO9nMcg epMHlmkay2v8GEV1HwRIJcwq8kETS9R/lmH7FNnxOYyh4KTOGqwNDqRiDWQB9pW2HKhK DRxXfKZCaUUf5zDZvtCuJ6Ot9Xvg3tHW99/ubClkOn3KWxfN+wNa5P12bp01/xGGJ2M9 oX3/S/AlYqXWiPEMtaIhiPBVsbgckMzIilzlwYAH15IvAnl0P/S/GB26f+npNMtqR8OS Xe7Powai7UHv2nwWb7RphK7qrMOyE0VE486OArjp3tXM9dyv40TuxTP7iZunTUKCQf53 l5kg== X-Received: by 10.70.9.129 with SMTP id z1mr784500pda.37.1412318649292; Thu, 02 Oct 2014 23:44:09 -0700 (PDT) Received: from [192.168.1.14] ([113.68.23.184]) by mx.google.com with ESMTPSA id bv5sm5737963pbc.20.2014.10.02.23.43.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 23:44:07 -0700 (PDT) References: <541FBD6F.2080507@selasky.org> <541FDDF0.90502@selasky.org> <542662BE.5050908@selasky.org> <542701FA.2000408@selasky.org> <5427029B.3060502@selasky.org> <5427AC46.3040707@selasky.org> <542E3F02.4050401@selasky.org> Mime-Version: 1.0 (1.0) In-Reply-To: <542E3F02.4050401@selasky.org> Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: quoted-printable Message-Id: <141592A3-A4CD-48F6-B26D-35BF10436012@gmail.com> X-Mailer: iPhone Mail (11D257) From: =?GB2312?Q?"=BB=C6=CE=C4=BB=D4=40Gmail"?= Subject: Re: xhci problem on UEFI boot MacBookPro 11,3 Date: Fri, 3 Oct 2014 14:43:26 +0800 To: Hans Petter Selasky Cc: "freebsd-usb@freebsd.org" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 06:44:10 -0000 But xhci should works under freebsd,like Linux without this trick. If you want to debug this further, ping me , I will be free after 2 hours;) Huang Wen Hui > =D4=DA 2014=C4=EA10=D4=C23=C8=D5=A3=AC14:15=A3=ACHans Petter Selasky =D0=B4=B5=C0=A3=BA >=20 >> On 10/03/14 05:55, Huang Wen Hui wrote: >> I found that how to connect EHCI controller, use "bless" command in MacOS= X >> with --legacy option: >> 1. open MacOSX terminal, mkdir /Volumes/EFI >> 2. mount -t msdos /dev/disk0s1 /Volumes/EFI >> 3. bless --setBoot --mount /Volumes/EFI --legacy >> 4. reboot MacOSX, press "option" key, you can feel firmware start a littl= e >> slow than without --legacy. I think firmware do some extra things:( >> 5. select both UEFI and BIOS boot FreeBSD, system can connect EHCI and XH= CI >> controller. >> 6. I think BootCamp assistant also add --legacy option. >>=20 >> Cheers, >> Huang Wen Hui >=20 > Hi, >=20 > Sounds good! >=20 > Thanks for figuring this out. At least I found one or two minors in the XH= CI driver while debugging this :-) >=20 > --HPS >=20 From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 11:38:47 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB8B38EA for ; Fri, 3 Oct 2014 11:38:47 +0000 (UTC) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A649EAB for ; Fri, 3 Oct 2014 11:38:46 +0000 (UTC) Received: from [10.0.2.95] (ppp118-210-223-248.lns20.adl6.internode.on.net [118.210.223.248]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id s93BJnhS048205 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Oct 2014 20:50:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Panic in usb_unref_device From: "Daniel O'Connor" Date: Fri, 3 Oct 2014 20:49:48 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <8B31CE4F-F310-49E7-8316-22D6170BF6C6@gsoft.com.au> To: freebsd-usb@freebsd.org X-Mailer: Apple Mail (2.1878.6) X-Spam-Score: 1.163 (*) BAYES_00,HELO_MISC_IP,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 11:38:47 -0000 Hi, I have a custom USB device based on the Cypress FX2 and we are finding = that with some older kernels it hangs - this was fixed in = https://svnweb.freebsd.org/base?view=3Drevision&revision=3D267240 but = now it panics with=85 #7 0xffffffff80745a07 in usb_unref_device (cpd=3D0xfffffe0004b30680, = crd=3D0xffffff812b6af860) at /usr/src/sys/dev/usb/usb_dev.c:348 #8 0xffffffff80748cbd in usb_ioctl (dev=3D, = cmd=3D3222040644, addr=3D0xfffffe0026380000 "\002", fflag=3D, td=3D0xffffffff81819850) at /usr/src/sys/dev/usb/usb_dev.c:1127 #9 0xffffffff807d05cb in devfs_ioctl_f (fp=3D0xfffffe0061d59190, = com=3D3222040644, data=3D, cred=3D, td=3D0xfffffe0004e37920) at /usr/src/sys/fs/devfs/devfs_vnops.c:758 #10 0xffffffff80938456 in kern_ioctl (td=3D0xfffffe0004e37920, fd=3D3, = com=3D3222040644, data=3D0xfffffe0026380000 "\002") at file.h:311 #11 0xffffffff8093869d in sys_ioctl (td=3D0xfffffe0004e37920, = uap=3D0xffffff812b6afa70) at /usr/src/sys/kern/sys_generic.c:696 And crd->rxfifo is NULL. I haven=92t looked very hard at this yet, but it is quite easy to = reproduce. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 11:49:02 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C052A57 for ; Fri, 3 Oct 2014 11:49:02 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5CF79FA0 for ; Fri, 3 Oct 2014 11:49:02 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 379D91FE023; Fri, 3 Oct 2014 13:49:00 +0200 (CEST) Message-ID: <542E8D27.2060505@selasky.org> Date: Fri, 03 Oct 2014 13:48:55 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Daniel O'Connor , freebsd-usb@freebsd.org Subject: Re: Panic in usb_unref_device References: <8B31CE4F-F310-49E7-8316-22D6170BF6C6@gsoft.com.au> In-Reply-To: <8B31CE4F-F310-49E7-8316-22D6170BF6C6@gsoft.com.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 11:49:02 -0000 On 10/03/14 13:19, Daniel O'Connor wrote: > Hi, > I have a custom USB device based on the Cypress FX2 and we are finding that with some older kernels it hangs - this was fixed in https://svnweb.freebsd.org/base?view=revision&revision=267240 but now it panics with… > Hi, There's a minor bug there. Can you test the attached patch? --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 16:10:52 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8928F215 for ; Fri, 3 Oct 2014 16:10:52 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491AD129 for ; Fri, 3 Oct 2014 16:10:51 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 119A91FE023; Fri, 3 Oct 2014 18:10:42 +0200 (CEST) Message-ID: <542ECA7D.8020207@selasky.org> Date: Fri, 03 Oct 2014 18:10:37 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Daniel O'Connor , freebsd-usb@freebsd.org Subject: Re: Panic in usb_unref_device References: <8B31CE4F-F310-49E7-8316-22D6170BF6C6@gsoft.com.au> <542E8D27.2060505@selasky.org> In-Reply-To: <542E8D27.2060505@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 16:10:52 -0000 On 10/03/14 13:48, Hans Petter Selasky wrote: > On 10/03/14 13:19, Daniel O'Connor wrote: >> Hi, >> I have a custom USB device based on the Cypress FX2 and we are finding >> that with some older kernels it hangs - this was fixed in >> https://svnweb.freebsd.org/base?view=revision&revision=267240 but now >> it panics with… >> > Hi, This commit should fix it: https://svnweb.freebsd.org/changeset/base/272480 If not, let me know. Thank you! --HPS From owner-freebsd-usb@FreeBSD.ORG Sat Oct 4 13:53:19 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C76203B8 for ; Sat, 4 Oct 2014 13:53:19 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 256976C2 for ; Sat, 4 Oct 2014 13:53:18 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id f15so2284208lbj.39 for ; Sat, 04 Oct 2014 06:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=PKOnjRVWfrZF/Cz4uY+TLFnMy4He1abbddxnqW8tJy0=; b=T51oO6piCDf7vc/swzSognh0dlxuQgCHV5NYUoTTY1q5teRh1gQryyetUwkIMxuCqE y6HP626vRp61Acw9APPSmxJxlyvVpTuIghqkp30eK82bMAU+iS8pk1Is4wKLpvzcnkbk 2g5vjCCvuSDHQjyIR5PpZGRQ1Bt933aQe7EDuNid7KUph7axDfqminAQadiu6BQkE/bE K6p8DFclvbUmJwaa/ya0u62RNiTaNMx3+ps29fcFu8Bb0dL1UHzRFEaq0UXzmeOoeR5I 2ZAB8w2JGQVN51fDORB0fuieiKPQt6FeNTDBrVo6aqzQbt9GQOZc6xLuDbclEax8H5yI 7EzQ== MIME-Version: 1.0 X-Received: by 10.112.180.137 with SMTP id do9mr11910290lbc.63.1412430796511; Sat, 04 Oct 2014 06:53:16 -0700 (PDT) Sender: uspoerlein@gmail.com Received: by 10.152.170.135 with HTTP; Sat, 4 Oct 2014 06:53:16 -0700 (PDT) In-Reply-To: <20140929174904.GA15642@coyote.spoerlein.net> References: <20140929174904.GA15642@coyote.spoerlein.net> Date: Sat, 4 Oct 2014 15:53:16 +0200 X-Google-Sender-Auth: RN7u4h_7HFYQAKk6Y4VC_5QqdbM Message-ID: Subject: Re: CEC device not attaching to xHCI port From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: freebsd-usb@freebsd.org, hps@selasky.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2014 13:53:19 -0000 2014-09-29 19:49 GMT+02:00 Ulrich Sp=C3=B6rlein : > Hi, > > I got a CEC adapter using libCEC to bridge the gap between my XBMC and > TV. The device works fine *if* I plug it into the front ports (which is > a bit ugly, so I was wondering why this is not working on the other USB > hub). > > Non-working: > ugen0.2: at usbus0 (disconnected) > root@coyote:~# usbconfig -u 0 -a 1 > ugen0.1: at usbus0, cfg=3D0 md=3DHOST spd=3DSUPER = (5.0Gbps) pwr=3DSAVE (0mA) > > Working: > ugen1.4: at usbus1 > ums0: on= usbus1 > ums0: 3 buttons and [XY] coordinates ID=3D0 > umodem0: = on usbus1 > umodem0: data interface 1, has CM over data, has break > root@coyote:~# usbconfig -u 1 -a 4 > ugen1.4: at usbus1, cfg=3D0 md=3DHOST spd= =3DFULL (12Mbps) pwr=3DON (10mA) > > The hubs: > root@coyote:~# pciconf -l -v xhci0 > xhci0@pci0:0:20:0: class=3D0x0c0330 card=3D0x72708086 chip=3D0x1e318= 086 rev=3D0x04 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '7 Series/C210 Series Chipset Family USB xHCI Host Con= troller' > class =3D serial bus > subclass =3D USB > root@coyote:~# pciconf -l -v ehci0 > ehci0@pci0:0:26:0: class=3D0x0c0320 card=3D0x72708086 chip=3D0x1e2d8= 086 rev=3D0x04 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '7 Series/C210 Series Chipset Family USB Enhanced Host= Controller' > class =3D serial bus > subclass =3D USB > > This is on 10.1-BETA1 and I found this post and workaround, which seem to= be relevant: > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2013-02/msg00701.= html > > But I haven't rebooted yet with hw.usb.xhci.xhci_port_route -1 > > Any more info you'd require on this? Should I file a PR to track this? > > Cheers, > Uli Sorry for the delay, I'm not subscribed to freebsd-usb, please keep me CC'ed on replies. The flag hw.usb.xhci.xhci_port_route does nothing for me, as it doesn't even exist yet. I had to recompile my kernel to get USB_DEBUG and there's quite a bunch of repetitive output when plugging in the device into the non-working hub. Here we go: Oct 4 15:41:12 coyote kernel: usb_needs_explore: Oct 4 15:41:12 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:12 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:12 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:12 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:12 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:12 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:12 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:12 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:12 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:12 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:12 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:13 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:14 coyote kernel: usb_needs_explore: Oct 4 15:41:14 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ab4528 Oct 4 15:41:14 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:14 coyote kernel: uhub_explore: udev=3D0xfffff800047e4000 addr= =3D1 Oct 4 15:41:14 coyote kernel: usb_needs_explore: Oct 4 15:41:14 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:14 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ad0cd8 Oct 4 15:41:14 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:14 coyote kernel: uhub_explore: udev=3D0xfffff800047e5000 addr= =3D1 Oct 4 15:41:14 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_explore: udev=3D0xfffff800048a9000 addr= =3D2 Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: usb_needs_explore: Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:16 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:16 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:16 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:16 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:16 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:16 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:17 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:18 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:18 coyote kernel: usb_needs_explore: Oct 4 15:41:18 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ab4528 Oct 4 15:41:18 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:18 coyote kernel: uhub_explore: udev=3D0xfffff800047e4000 addr= =3D1 Oct 4 15:41:18 coyote kernel: usb_needs_explore: Oct 4 15:41:18 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:18 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ad0cd8 Oct 4 15:41:18 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:18 coyote kernel: uhub_explore: udev=3D0xfffff800047e5000 addr= =3D1 Oct 4 15:41:18 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_explore: udev=3D0xfffff800048a9000 addr= =3D2 Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: usb_needs_explore: Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:20 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:20 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:20 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:20 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:20 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:21 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:22 coyote kernel: usb_needs_explore: Oct 4 15:41:22 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ab4528 Oct 4 15:41:22 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:22 coyote kernel: uhub_explore: udev=3D0xfffff800047e4000 addr= =3D1 Oct 4 15:41:22 coyote kernel: usb_needs_explore: Oct 4 15:41:22 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:22 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ad0cd8 Oct 4 15:41:22 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:22 coyote kernel: uhub_explore: udev=3D0xfffff800047e5000 addr= =3D1 Oct 4 15:41:22 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:22 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_explore: udev=3D0xfffff800048a9000 addr= =3D2 Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:23 coyote kernel: usb_needs_explore: Oct 4 15:41:23 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:24 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x07a0, wPortChange=3D0x0020, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:24 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:24 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ab4528 Oct 4 15:41:24 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:25 coyote kernel: usb_needs_explore: Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_explore: udev=3D0xfffff800047e4000 addr= =3D1 Oct 4 15:41:25 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x07a0, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x01e1, wPortChange=3D0x0001, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:25 coyote kernel: uhub_reattach_port: reattaching port 4 Oct 4 15:41:25 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x01e1, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_reattach_port: Port 4 is in Host Mode Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:25 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: usb_needs_explore: Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: usb_needs_explore: Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:26 coyote kernel: usb_needs_explore: Oct 4 15:41:26 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:26 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ad0cd8 Oct 4 15:41:27 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:27 coyote kernel: uhub_explore: udev=3D0xfffff800047e5000 addr= =3D1 Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_explore: udev=3D0xfffff800048a9000 addr= =3D2 Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:27 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:28 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:28 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:28 coyote kernel: usb_needs_explore: Oct 4 15:41:28 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:28 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:28 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:28 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:28 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:28 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:28 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:28 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:28 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:29 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:30 coyote kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Oct 4 15:41:30 coyote kernel: usb_needs_explore: Oct 4 15:41:30 coyote last message repeated 2 times Oct 4 15:41:30 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000ad0cd8 Oct 4 15:41:30 coyote kernel: uhub_explore: udev=3D0xfffff800047e5000 addr= =3D1 Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_explore: udev=3D0xfffff800048a9000 addr= =3D2 Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0103, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: usbd_req_re_enumerate: addr=3D3, set address failed! (USB_ERR_TIMEOUT, ignored) Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:31 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0500, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:32 coyote kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Oct 4 15:41:32 coyote kernel: usb_needs_explore: Oct 4 15:41:32 coyote kernel: usb_bus_powerd: bus=3D0xfffffe0000b54cd8 Oct 4 15:41:32 coyote kernel: usb_bus_powerd: Recomputing power masks Oct 4 15:41:32 coyote kernel: uhub_explore: udev=3D0xfffff800047e6000 addr= =3D1 Oct 4 15:41:32 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0503, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:32 coyote kernel: uhub_explore: udev=3D0xfffff800048b0000 addr= =3D2 Oct 4 15:41:32 coyote kernel: usbd_transfer_power_ref: Adding type 0 to power state Oct 4 15:41:32 coyote kernel: usbd_transfer_power_ref: needs power Oct 4 15:41:32 coyote kernel: uhub_read_port_status: port 1, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:32 coyote kernel: uhub_read_port_status: port 2, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: usb_needs_explore: Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 3, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 4, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 5, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 6, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 7, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:33 coyote kernel: uhub_read_port_status: port 8, wPortStatus=3D0x0100, wPortChange=3D0x0000, err=3DUSB_ERR_NORMAL_COMPLETION Oct 4 15:41:34 coyote kernel: usbd_req_re_enumerate: addr=3D3, set address failed! (USB_ERR_TIMEOUT, ignored) Oct 4 15:41:35 coyote kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Oct 4 15:41:36 coyote kernel: usbd_req_re_enumerate: addr=3D3, set address failed! (USB_ERR_TIMEOUT, ignored) Oct 4 15:41:36 coyote kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT Oct 4 15:41:38 coyote kernel: usbd_req_re_enumerate: addr=3D3, set address failed! (USB_ERR_TIMEOUT, ignored) Oct 4 15:41:39 coyote kernel: ugen0.2: at usbus0 (disconnected) Oct 4 15:41:39 coyote kernel: uhub_reattach_port: could not allocate new d= evice