From owner-freebsd-usb@freebsd.org Sun Aug 28 08:12:00 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1A1EB78E10 for ; Sun, 28 Aug 2016 08:12:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 8A7D09F1 for ; Sun, 28 Aug 2016 08:12:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7S8C0nr054267 for ; Sun, 28 Aug 2016 08:12:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 170358] [ums] Wrong (duplicate) button numbers Date: Sun, 28 Aug 2016 08:12:00 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: t@tobik.me X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 08:12:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D170358 Tobias Kortkamp changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t@tobik.me --- Comment #6 from Tobias Kortkamp --- Created attachment 174152 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D174152&action= =3Dedit ums.diff This issue still exists 4 years later. Tomek's "fix" works for me too. I'm attaching a diff to make it easier to apply. In case it matters, my usbconfig -d 0.2 do_request 0x81 0x06 0x2200 1 0x100 output is identical as Tomek's. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sun Aug 28 11:35:48 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9966B785BA for ; Sun, 28 Aug 2016 11:35:48 +0000 (UTC) (envelope-from hps@selasky.org) 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 82403EFE for ; Sun, 28 Aug 2016 11:35:47 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 1818F1FE022; Sun, 28 Aug 2016 13:35:45 +0200 (CEST) Subject: Re: USB 3.0 devices negotiate to spd=HIGH for all ports To: Adam Stylinski References: <2a28aa4b-3256-b091-9a6e-c2a29f993d6c@selasky.org> Cc: freebsd-usb@freebsd.org From: Hans Petter Selasky Message-ID: <47b97f76-44bb-048e-e1ad-4969bc045ab5@selasky.org> Date: Sun, 28 Aug 2016 13:40:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 11:35:48 -0000 On 08/27/16 20:05, Adam Stylinski wrote: > The only quirk specific code I can find in Linux's kernel for XHCI is this: > http://lxr.free-electrons.com/source/drivers/usb/host/pci-quirks.c > > I believe I have one of the SBxxx AMD chipsets, though I can't recall which > one. I don't see anything in there referring to my PCI IDs, unless I'm > looking at the wrong outputs in pciconf -lv. I see one quirk in particular > regarding power management but that seems to be more about stability rather > than speed. I'm sure I'm missing something. > Hi, The Linux XHCI has the following quirks for ETRON: if (pdev->vendor == PCI_VENDOR_ID_ETRON && pdev->device == PCI_DEVICE_ID_EJ168) { xhci->quirks |= XHCI_RESET_ON_RESUME; xhci->quirks |= XHCI_TRUST_TX_LENGTH; xhci->quirks |= XHCI_BROKEN_STREAMS; } They don't apply to FreeBSD. There aren't any BIOS settings to enable/disable USB 3.0? --HPS From owner-freebsd-usb@freebsd.org Sun Aug 28 11:51:16 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30F71B78CE0 for ; Sun, 28 Aug 2016 11:51:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 20DBEA36 for ; Sun, 28 Aug 2016 11:51:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7SBpFSF013798 for ; Sun, 28 Aug 2016 11:51:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 170358] [ums] Wrong (duplicate) button numbers Date: Sun, 28 Aug 2016 11:51:16 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 11:51:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D170358 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org, | |thompsa@FreeBSD.org --- Comment #7 from Hans Petter Selasky --- Hi Andrew: In r208009 you added support for T-axis. Are you fine with the changes this patch proposes? https://svnweb.freebsd.org/base/head/sys/dev/usb/input/ums.c?r1=3D208008&r2= =3D208009& --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sun Aug 28 15:53:01 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2226B777E8 for ; Sun, 28 Aug 2016 15:53:01 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49FF4D8B for ; Sun, 28 Aug 2016 15:53:01 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id g62so85797727lfe.3 for ; Sun, 28 Aug 2016 08:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3HahTLErs79W+NjAQpegRVspxFWmS25zHoJ+/FIbNGM=; b=X3HVM4Sd4eq4yr3Vl69w2oycaHrfNAFLh122V2DpFyRDWFfDV5bCgpaCKkQHETrMUB KEPT0N6eYQozjUP/cCDmSbpKXCrSsXZ8RQ87mIDylpGw6T+Ab7hSoGcNXAOo0IfrRFIp 6V+UJthTkcdLQ8XZphoXoOhS8Dz4NPSj1mc6AZRRLUVZOUOU4T60OkfDHjdXohZjArmJ A/KtoCwIUbyG/xE5hKnW+yblpT0QwoOoxx+l0qiVF+NwSHlbFc1pXVv2h6M7lIoRTFRH LQb0WnIkRn+ktxQ6yxriPnFF08qz4wLOlg+Y+l8ViUicPQH6FCUBINHfQcQex2jQjODJ cxJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3HahTLErs79W+NjAQpegRVspxFWmS25zHoJ+/FIbNGM=; b=JVn41HA6oYF7kCpZI2Q0Q93ioiTN+LmYucTMvRTJxhQgYhL9m7n1qf4WfPFQnzD0bu QzlA6TDQd3AOKtDl+KaXDW3JfYcmRxtjGuwmI7TJpjo67hyOveZyyzWIFH8J9XCJDtnW s5EQiR1GBwl3xPcTJHH9s++0kgMV9MksIU6m6kunc1ZHtEHvH+2HTHxgsSRagmMVlKBw X1+jvaj7hpBfjOuXqXfenb9kNodPTkVGynV7pnBLGoze6kCIkojZxftjWekvamCRJwBc lqkMjAxrMfqqwrCsFK3b/O+XOG5zNBEDwlP4f2KEnySBkuHr0ER7/e77VrhI2XyyvjQ7 qwSw== X-Gm-Message-State: AE9vXwNvhp2NXmXEnwZ3rzzZMit66gnoo5N2t8TEllo8QgweREt4mfztXdYtntLXAob8mRFS5cr4+0NHS/nHMA== X-Received: by 10.25.80.212 with SMTP id e203mr4762545lfb.115.1472399578699; Sun, 28 Aug 2016 08:52:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.30.83 with HTTP; Sun, 28 Aug 2016 08:52:57 -0700 (PDT) In-Reply-To: References: <2a28aa4b-3256-b091-9a6e-c2a29f993d6c@selasky.org> From: Adam Stylinski Date: Sun, 28 Aug 2016 11:52:57 -0400 Message-ID: Subject: Re: USB 3.0 devices negotiate to spd=HIGH for all ports To: Hans Petter Selasky , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 15:53:02 -0000 On Sun, Aug 28, 2016 at 10:18 AM, Adam Stylinski wrote: > Looking at my motherboard's manual, this is what my BIOS exposes: > > USB 2.0 Controller Use this item to enable or disable the use of USB 2.0 > controller. USB 3.0 Controller Use this item to enable or disable the use > of USB 3.0 controller. Legacy USB Support Use this option to select legacy > support for USB devices. There are four con guration options: [Enabled], > [Disabled], [Auto] and [UEFI Setup Only]. The default value is [Enabled]. > Please refer to below descriptions for the details of these four options: > [Enabled] - Enables support for legacy USB. [Disabled] - USB devices are > not allowed to use under legacy OS and UEFI setup when [Disabled] is > selected. If you have USB compatibility issue, it is recommended to select > [Disabled] to enter OS. [Auto] - Enables legacy support if USB devices are > connected. [UEFI Setup Only] - USB devices are allowed to use only under > UEFI setup and Windows / Linux OS. Legacy USB 3.0 Support Use this option > to enable or disable legacy support for USB 3.0 devices. > > I believe 3.0 controller is enabled, or I wouldn't be able to use those > ports at all. Now the Legacy USB 3.0 option is a bit vaguely named, as it > could be taken to mean, use USB 3.0 ports in legacy mode. It could also > mean, "allow USB 2.0 devices with 3.0 ports". The default for that option > is disabled, but it may have been misconstrued and enabled at one point. > Getting to the BIOS unfortunately requires me installing a video card in > there that's not 15 years old, unfortunately, as it's one of those > sophisticated new BIOSes that work with a mouse and require fancier VGA > BIOSes than what this S3 Virge card provides. It's definitely worth a > look, though. > > On Sat, Aug 27, 2016 at 2:05 PM, Adam Stylinski > wrote: > >> The only quirk specific code I can find in Linux's kernel for XHCI is >> this: >> http://lxr.free-electrons.com/source/drivers/usb/host/pci-quirks.c >> >> I believe I have one of the SBxxx AMD chipsets, though I can't recall >> which one. I don't see anything in there referring to my PCI IDs, unless >> I'm looking at the wrong outputs in pciconf -lv. I see one quirk in >> particular regarding power management but that seems to be more about >> stability rather than speed. I'm sure I'm missing something. >> >> On Sat, Aug 27, 2016 at 1:43 PM, Hans Petter Selasky >> wrote: >> >>> On 08/27/16 18:41, Adam Stylinski wrote: >>> >>>> Hello, >>>> >>>> I definitely have a USB 3.0 controller that is being recognized by XHCI: >>>> >>>> [adam@nasbox ~]$ sudo usbconfig >>>> ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER >>>> (5.0Gbps) pwr=SAVE (0mA) >>>> ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) >>>> pwr=SAVE (0mA) >>>> ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER >>>> (5.0Gbps) pwr=SAVE (0mA) >>>> ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) >>>> pwr=SAVE (0mA) >>>> ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) >>>> pwr=SAVE (0mA) >>>> ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) >>>> pwr=SAVE (0mA) >>>> ugen7.1: at usbus7, cfg=0 md=HOST spd=FULL (12Mbps) >>>> pwr=SAVE (0mA) >>>> ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) >>>> pwr=SAVE (0mA) >>>> ugen8.1: at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) >>>> pwr=SAVE (0mA) >>>> ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) >>>> pwr=ON (200mA) >>>> >>>> >>>> xhci0@pci0:3:0:0: class=0x0c0330 card=0x70231849 chip=0x70231b6f >>>> rev=0x01 >>>> hdr=0x00 >>>> vendor = 'Etron Technology, Inc.' >>>> device = 'EJ168 USB 3.0 Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> xhci1@pci0:4:0:0: class=0x0c0330 card=0x70231849 chip=0x70231b6f >>>> rev=0x01 >>>> hdr=0x00 >>>> vendor = 'Etron Technology, Inc.' >>>> device = 'EJ168 USB 3.0 Host Controller' >>>> class = serial bus >>>> subclass = USB >>>> >>>> However, when I connect a USB 3.0 device into a USB 3.0 port, it only >>>> gives >>>> me spd=HIGH. This is a Sandisk CZ80, but I've other devices in the past >>>> and have had the same behavior. Plugging a device in with >>>> hw.usb.xhci.debug=1 doesn't appear to print too many useful things, at >>>> least not to an end user. I won't yet paste the full output, but it >>>> looks >>>> something like this: >>>> >>>> xhci_transfer_insert: qh_pos = 2 >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_check_transfer: TD is last >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_device_generic_enter: >>>> xhci_setup_generic_chain_sub: NTRB=1 >>>> xhci_setup_generic_chain_sub: LINK=0x241ff800 >>>> xhci_setup_generic_chain: first=0xfffff800241ff980 >>>> last=0xfffff800241ff980 >>>> xhci_device_generic_start: >>>> xhci_transfer_insert: qh_pos = 2 >>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_check_transfer: TD is last >>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_device_generic_enter: >>>> xhci_setup_generic_chain_sub: NTRB=1 >>>> xhci_setup_generic_chain_sub: LINK=0x55fc6a300 >>>> xhci_setup_generic_chain: first=0xfffff8055fc6a480 >>>> last=0xfffff8055fc6a480 >>>> xhci_device_generic_start: >>>> xhci_transfer_insert: qh_pos = 0 >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_check_transfer: TD is last >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_device_generic_enter: >>>> xhci_setup_generic_chain_sub: NTRB=1 >>>> xhci_setup_generic_chain_sub: LINK=0x3d958d000 >>>> xhci_setup_generic_chain: first=0xfffff803d958d180 >>>> last=0xfffff803d958d180 >>>> xhci_device_generic_start: >>>> xhci_transfer_insert: qh_pos = 1 >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_check_transfer: TD is last >>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_device_generic_enter: >>>> xhci_setup_generic_chain_sub: NTRB=1 >>>> xhci_setup_generic_chain_sub: LINK=0x7d676f000 >>>> xhci_setup_generic_chain: first=0xfffff807d676f180 >>>> last=0xfffff807d676f180 >>>> xhci_device_generic_start: >>>> xhci_transfer_insert: qh_pos = 0 >>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> xhci_check_transfer: TD is last >>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>> xhci_check_transfer: stream_id=0 >>>> >>>> What can I do to end this frustrating issue of USB 2.0 only-ness? >>>> >>> >>> Try to google the PCI IDs of your device and see if Linux has any quirks >>> for your card. Sometimes these cards need special register writes to enable >>> USB 3.0. >>> >>> --HPS >>> >>> >> > Alright, so I went through the crazy hurdles to actually get to the BIOS, and the USB legacy support for USB 3.0 was enabled. I disabled it, and it has no apparently effect, other than the fact that setting up the device takes a lot longer now: usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_TIMEOUT usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_TIMEOUT ugen0.2: at usbus0 (disconnected) uhub_reattach_port: could not allocate new device ugen0.2: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:14:0:-1: Attached to scbus14 da23 at umass-sim0 bus 0 scbus14 target 0 lun 0 da23: Removable Direct Access SPC-4 SCSI device da23: Serial Number [PROBABLY NOT IMPORTANT ENOUGH TO SCRUB, BUT DOING SO ANYWAY] da23: 40.000MB/s transfers da23: 59840MB (122552320 512 byte sectors) da23: quirks=0x2 [adam@nasbox ~]$ sudo usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen7.1: at usbus7, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen8.1: at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) Which steps are next? I apologize to the list for top-posting, it's been a while since I've been to a mailing list and I decided to do it through Gmail for whatever reason instead of mutt. From owner-freebsd-usb@freebsd.org Sun Aug 28 18:06:08 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE21EBC129D for ; Sun, 28 Aug 2016 18:06:08 +0000 (UTC) (envelope-from hps@selasky.org) 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 7EF4DA36 for ; Sun, 28 Aug 2016 18:06:08 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B598C1FE022; Sun, 28 Aug 2016 20:06:03 +0200 (CEST) Subject: Re: USB 3.0 devices negotiate to spd=HIGH for all ports To: Adam Stylinski , freebsd-usb@freebsd.org References: <2a28aa4b-3256-b091-9a6e-c2a29f993d6c@selasky.org> From: Hans Petter Selasky Message-ID: Date: Sun, 28 Aug 2016 20:10:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 18:06:08 -0000 On 08/28/16 17:52, Adam Stylinski wrote: > On Sun, Aug 28, 2016 at 10:18 AM, Adam Stylinski > wrote: > >> Looking at my motherboard's manual, this is what my BIOS exposes: >> >> USB 2.0 Controller Use this item to enable or disable the use of USB 2.0 >> controller. USB 3.0 Controller Use this item to enable or disable the use >> of USB 3.0 controller. Legacy USB Support Use this option to select legacy >> support for USB devices. There are four con guration options: [Enabled], >> [Disabled], [Auto] and [UEFI Setup Only]. The default value is [Enabled]. >> Please refer to below descriptions for the details of these four options: >> [Enabled] - Enables support for legacy USB. [Disabled] - USB devices are >> not allowed to use under legacy OS and UEFI setup when [Disabled] is >> selected. If you have USB compatibility issue, it is recommended to select >> [Disabled] to enter OS. [Auto] - Enables legacy support if USB devices are >> connected. [UEFI Setup Only] - USB devices are allowed to use only under >> UEFI setup and Windows / Linux OS. Legacy USB 3.0 Support Use this option >> to enable or disable legacy support for USB 3.0 devices. >> >> I believe 3.0 controller is enabled, or I wouldn't be able to use those >> ports at all. Now the Legacy USB 3.0 option is a bit vaguely named, as it >> could be taken to mean, use USB 3.0 ports in legacy mode. It could also >> mean, "allow USB 2.0 devices with 3.0 ports". The default for that option >> is disabled, but it may have been misconstrued and enabled at one point. >> Getting to the BIOS unfortunately requires me installing a video card in >> there that's not 15 years old, unfortunately, as it's one of those >> sophisticated new BIOSes that work with a mouse and require fancier VGA >> BIOSes than what this S3 Virge card provides. It's definitely worth a >> look, though. >> >> On Sat, Aug 27, 2016 at 2:05 PM, Adam Stylinski >> wrote: >> >>> The only quirk specific code I can find in Linux's kernel for XHCI is >>> this: >>> http://lxr.free-electrons.com/source/drivers/usb/host/pci-quirks.c >>> >>> I believe I have one of the SBxxx AMD chipsets, though I can't recall >>> which one. I don't see anything in there referring to my PCI IDs, unless >>> I'm looking at the wrong outputs in pciconf -lv. I see one quirk in >>> particular regarding power management but that seems to be more about >>> stability rather than speed. I'm sure I'm missing something. >>> >>> On Sat, Aug 27, 2016 at 1:43 PM, Hans Petter Selasky >>> wrote: >>> >>>> On 08/27/16 18:41, Adam Stylinski wrote: >>>> >>>>> Hello, >>>>> >>>>> I definitely have a USB 3.0 controller that is being recognized by XHCI: >>>>> >>>>> [adam@nasbox ~]$ sudo usbconfig >>>>> ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER >>>>> (5.0Gbps) pwr=SAVE (0mA) >>>>> ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER >>>>> (5.0Gbps) pwr=SAVE (0mA) >>>>> ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen7.1: at usbus7, cfg=0 md=HOST spd=FULL (12Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen8.1: at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) >>>>> pwr=SAVE (0mA) >>>>> ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) >>>>> pwr=ON (200mA) >>>>> >>>>> >>>>> xhci0@pci0:3:0:0: class=0x0c0330 card=0x70231849 chip=0x70231b6f >>>>> rev=0x01 >>>>> hdr=0x00 >>>>> vendor = 'Etron Technology, Inc.' >>>>> device = 'EJ168 USB 3.0 Host Controller' >>>>> class = serial bus >>>>> subclass = USB >>>>> xhci1@pci0:4:0:0: class=0x0c0330 card=0x70231849 chip=0x70231b6f >>>>> rev=0x01 >>>>> hdr=0x00 >>>>> vendor = 'Etron Technology, Inc.' >>>>> device = 'EJ168 USB 3.0 Host Controller' >>>>> class = serial bus >>>>> subclass = USB >>>>> >>>>> However, when I connect a USB 3.0 device into a USB 3.0 port, it only >>>>> gives >>>>> me spd=HIGH. This is a Sandisk CZ80, but I've other devices in the past >>>>> and have had the same behavior. Plugging a device in with >>>>> hw.usb.xhci.debug=1 doesn't appear to print too many useful things, at >>>>> least not to an end user. I won't yet paste the full output, but it >>>>> looks >>>>> something like this: >>>>> >>>>> xhci_transfer_insert: qh_pos = 2 >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_check_transfer: TD is last >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_device_generic_enter: >>>>> xhci_setup_generic_chain_sub: NTRB=1 >>>>> xhci_setup_generic_chain_sub: LINK=0x241ff800 >>>>> xhci_setup_generic_chain: first=0xfffff800241ff980 >>>>> last=0xfffff800241ff980 >>>>> xhci_device_generic_start: >>>>> xhci_transfer_insert: qh_pos = 2 >>>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_check_transfer: TD is last >>>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_device_generic_enter: >>>>> xhci_setup_generic_chain_sub: NTRB=1 >>>>> xhci_setup_generic_chain_sub: LINK=0x55fc6a300 >>>>> xhci_setup_generic_chain: first=0xfffff8055fc6a480 >>>>> last=0xfffff8055fc6a480 >>>>> xhci_device_generic_start: >>>>> xhci_transfer_insert: qh_pos = 0 >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_check_transfer: TD is last >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_device_generic_enter: >>>>> xhci_setup_generic_chain_sub: NTRB=1 >>>>> xhci_setup_generic_chain_sub: LINK=0x3d958d000 >>>>> xhci_setup_generic_chain: first=0xfffff803d958d180 >>>>> last=0xfffff803d958d180 >>>>> xhci_device_generic_start: >>>>> xhci_transfer_insert: qh_pos = 1 >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_check_transfer: TD is last >>>>> xhci_check_transfer: slot=1 epno=3 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_device_generic_enter: >>>>> xhci_setup_generic_chain_sub: NTRB=1 >>>>> xhci_setup_generic_chain_sub: LINK=0x7d676f000 >>>>> xhci_setup_generic_chain: first=0xfffff807d676f180 >>>>> last=0xfffff807d676f180 >>>>> xhci_device_generic_start: >>>>> xhci_transfer_insert: qh_pos = 0 >>>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> xhci_check_transfer: TD is last >>>>> xhci_check_transfer: slot=1 epno=4 stream=256 remainder=0 status=1 >>>>> xhci_check_transfer: stream_id=0 >>>>> >>>>> What can I do to end this frustrating issue of USB 2.0 only-ness? >>>>> >>>> >>>> Try to google the PCI IDs of your device and see if Linux has any quirks >>>> for your card. Sometimes these cards need special register writes to enable >>>> USB 3.0. >>>> >>>> --HPS >>>> >>>> >>> >> > Alright, so I went through the crazy hurdles to actually get to the BIOS, > and the USB legacy support for USB 3.0 was enabled. I disabled it, and it > has no apparently effect, other than the fact that setting up the device > takes a lot longer now: > > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT > usbd_setup_device_desc: getting device descriptor at addr 1 failed, > USB_ERR_TIMEOUT > ugen0.2: at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > ugen0.2: at usbus0 > umass0: on usbus0 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:14:0:-1: Attached to scbus14 > da23 at umass-sim0 bus 0 scbus14 target 0 lun 0 > da23: Removable Direct Access SPC-4 SCSI device > da23: Serial Number [PROBABLY NOT IMPORTANT ENOUGH TO SCRUB, BUT DOING SO > ANYWAY] > da23: 40.000MB/s transfers > da23: 59840MB (122552320 512 byte sectors) > da23: quirks=0x2 > > [adam@nasbox ~]$ sudo usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER > (5.0Gbps) pwr=SAVE (0mA) > ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=SAVE (0mA) > ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER > (5.0Gbps) pwr=SAVE (0mA) > ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=SAVE (0mA) > ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=SAVE (0mA) > ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=SAVE (0mA) > ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=SAVE (0mA) > ugen7.1: at usbus7, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=SAVE (0mA) > ugen8.1: at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=SAVE (0mA) > ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON (200mA) > > Which steps are next? I apologize to the list for top-posting, it's been a > while since I've been to a mailing list and I decided to do it through > Gmail for whatever reason instead of mutt. > Hi, Typically USB 3.0 replaces all the USB 2.0 ones, so you should only have USB 3.0 enabled. BTW: Can you apply and try these patches. Do they make any difference? Especially in the case of the USB_ERR_TIMEOUT's. https://svnweb.freebsd.org/changeset/base/304597 https://svnweb.freebsd.org/changeset/base/304629 --HPS From owner-freebsd-usb@freebsd.org Mon Aug 29 08:15:49 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D61CBB77B13 for ; Mon, 29 Aug 2016 08:15:49 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from kazanfieldhockey.ru (kazanfieldhockey.ru [78.138.152.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "kazanfieldhockey.ru", Issuer "kazanfieldhockey.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F8CF28C for ; Mon, 29 Aug 2016 08:15:48 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from asd.localdomain (host-175-22.static.telecet.ru [87.117.175.22]) (authenticated bits=0) by kazanfieldhockey.ru (8.14.3/8.14.3) with ESMTP id u7T85UgM036131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 29 Aug 2016 11:05:35 +0300 (MSK) (envelope-from anatoly@kazanfieldhockey.ru) Date: Mon, 29 Aug 2016 11:09:39 +0300 From: Anatoly To: freebsd-usb@freebsd.org Subject: Re: Digi Watchport/T temperature sensor as /dev/ttyU Message-ID: <20160829110939.0db7bc6f@asd.localdomain> In-Reply-To: <20160826195256.67a63dbd.ohartman@zedat.fu-berlin.de> References: <20160722183556.2fc39fd7.ohartman@zedat.fu-berlin.de> <1469206374.84197.14.camel@freebsd.org> <20160723220430.34ce02fe.ohartman@zedat.fu-berlin.de> <1469306951.84197.31.camel@freebsd.org> <20160724080330.3a27e875.ohartman@zedat.fu-berlin.de> <20160724083859.4c0dd392@ernst.home> <20160724105134.184f0b7f.ohartman@zedat.fu-berlin.de> <1469379334.84197.40.camel@freebsd.org> <1469387555.84197.48.camel@freebsd.org> <20160826153842.586a559b@freyja.zeit4.iv.bundesimmobilien.de> <36ca2c4c-bf9d-ed12-0b14-a2afc861c5f7@selasky.org> <20160826195256.67a63dbd.ohartman@zedat.fu-berlin.de> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; i386-portbld-freebsd7.3) Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (kazanfieldhockey.ru [192.168.13.2]); Mon, 29 Aug 2016 11:05:35 +0300 (MSK) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2016 08:15:49 -0000 В Fri, 26 Aug 2016 19:52:56 +0200 "O. Hartmann" пишет: > Am Fri, 26 Aug 2016 15:53:55 +0200 > Hans Petter Selasky schrieb: > > > On 08/26/16 15:38, O. Hartmann wrote: > > > It is a USB interface PCB with an AT90USB162 microcontroler chip. > > > Attached to a FreeBSD 12-CURRENT system, it reports itself as a > > > UHID device. there is also a software package available - for > > > Windows and Linux, but it doesn't work for FreeBSD, the package > > > compiles and produces a cmdline binary, but it fails reading the > > > sensor data - the uhid driver seems to be unloaded during the > > > call. I have no skills in writing low-level USB software, so my > > > explanation is slopy, sorry. But there is hope I can use this > > > one. > > > > Hi, > > > > Could you send a link to this Linux software? > > > > It should work basically! > > > > Is your libusb up-to-date? > > > > You can trace USB activity using "usbdump -i usbusX -f Y -s 65536 > > -vvv". > > > > Maybe some command failed. > > > > Did you try "usbhidaction" to decode the data received? > > > > --HPS > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > > Hello, > > I would already have, but the site was offline due to maintenance > cycles this noon. It is in German ;-) > > The software can be downloaded via > > http://www.led-genial.de/mediafiles//Sonstiges/TempSensorTester.zip > > Please do not misunderstand me: I just did a dirty test and it worked > half way, but never got values from the temperature sensor. > > Since the device is recognized by FreeBSD as a UHID device, I guess > there is a much more convenient and standardized way to look for the > device and pick up data for, say ICINGA-2 or other measurements. The > software provided works well on Linux. On FreeBSD, running the binary > as root, firt unloads the uhid kernel module. So I guess the > procedure is Linux'ish and needs to be rewritten for proper *BSD > usage. > > Anyway - this part is more bringing up my personal thoughts and > intentions and not so much related to the initial stuff I asked the > list for - this PCB in question is much to expensive for a simple > temp sensor via 1-wire protocol, so I'm looking for something much > cheaper. There are offerings for very small Arduino PCBs with USB > port and I2C or 1-wire connectors for approx. 3 - 5 EUR. For a > server-based USB attached DS18B20 sensor which could be simply > interrogated by some simple C code via tty/uhid or something high > level would be very nice. The digi Watchport provided this with Linux > - the access was done via Perl. > > Looking for a small and autonomous sensor station I stumbled over a > lot of useful Linux stuff realized via Raspberry Pi. There is very > little for FreeBSD and I hesitate buying a nice RaspberryPi 3 B or > ODROID-C2 for that purpose. For autonomous monitoring of a server > room we use very expensive (~300 EUR each) web based devices. It is a > little box with a DS18B20, I guess and fancy LEDs as well as a NIC. > attached to the network, you can configure the device and there is > some rrdtool-like graphical output. > > I think, with the fancy framework of FreeBSD it should be possible to > adapt NanoBSD with small nginx or reduced Apache to perform the > stuff ... > > So, sorry for listening to my little-boy's dreaming > > Kind regards, > > Oliver By the way, it is possible to use RS-232 port lines for bit banging, so you can attach DS18(B)20 to RS-232 port with very simple adaptor (no MCU): https://github.com/bcl/digitemp Once I succefully tried to compile and run that software (DigiTemp v3.6.0) under FreeBSD 9.0, but never tested it with sensor yet. From owner-freebsd-usb@freebsd.org Tue Aug 30 11:26:49 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E933EBC7BD8 for ; Tue, 30 Aug 2016 11:26:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 D9063861 for ; Tue, 30 Aug 2016 11:26:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7UBQn1T091831 for ; Tue, 30 Aug 2016 11:26:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 212256] xhci controllers cannot be used with ppt Date: Tue, 30 Aug 2016 11:26:50 +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: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mt@waldheinz.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org 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 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 11:26:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212256 Bug ID: 212256 Summary: xhci controllers cannot be used with ppt Product: Base System Version: 10.3-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: mt@waldheinz.de I can't pass XHCI controllers to bhyve guests because the PCI device is alw= ays grabbed by the xhci driver instead of the ppt driver. That this patch: > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D281499 Fixes the problem for me. I'm manually applying it after every kernel update since about a year. I stumbled upon that patch here: > https://lists.freebsd.org/pipermail/freebsd-virtualization/2015-April/003= 499.html It seems other people are affected by this problem as well, though the workaround presented here: > https://github.com/pr1ntf/iohyve/wiki/USB-3.0-PCI-Controller-Pass-through seems worse to me, because it completely disables the xhci driver. Basically I'd like to see the patch land in a released version at some poin= t. Because I lack any knowledge about the FreeBSD development model I'm unable= to determine that state of that patch -- maybe it's on the list already? After one year I just thought maybe it's time to ask. :-) Thanks, -Matthias --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Tue Aug 30 11:44:20 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E7F6BC7F02 for ; Tue, 30 Aug 2016 11:44:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 60BC5E10 for ; Tue, 30 Aug 2016 11:44:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7UBiKsL028645 for ; Tue, 30 Aug 2016 11:44:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 212256] xhci controllers cannot be used with ppt Date: Tue, 30 Aug 2016 11:44:20 +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: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 11:44:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212256 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hselasky@FreeBSD.org --- Comment #1 from Hans Petter Selasky --- Hi, To which branches do you need r281499 MFC'ed? Ask the author to MFC it! --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Tue Aug 30 19:22:10 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66157BC9E15; Tue, 30 Aug 2016 19:22:10 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2863ED8B; Tue, 30 Aug 2016 19:22:08 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id b199so21150450lfe.0; Tue, 30 Aug 2016 12:22:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=IN65yKxXs0nJm7JEwVYD7rNoRto1ArrGQvSZADVyPHk=; b=fiTgsyGLQ4mMu+GbrYdbZkhDFt9yx7SLxq+7WGLcNyASF+v1sW6f9ou2AcXASwyRmh ZuPpVZq/NmliQhi5UslJCQ2ABa08IOLYB+SOhj+ZuFHC54R1sO0HZBffh06kn+Pzbeqz BvUnBAoWrkjCV6TgGW3d3Ddy6lhuLiXoUZNBGBNvAO2PndNJLuG5zUfVNBcEUGNDk53V DFUq5RWTPYlpD8n+wLvjy+9tYmRZgKLlFIgJ/u0DUpF4Aj6SKidLNMSQlhd+gFnZiPzQ Vm8MH26PSQo3+P3aZTib9B1kN7C2b3yq+k4Wugg6qmgFRcU6/9lhq64e6K8qfdtHu94u Pc/g== X-Gm-Message-State: AE9vXwNUg/7Bhz+dtiQ42wHev7aoEx17JtXLlHryigU+pCc15U5f9MpLqEkXD+1ELPrxcw== X-Received: by 10.25.125.4 with SMTP id y4mr1513195lfc.75.1472584920599; Tue, 30 Aug 2016 12:22:00 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id 83sm7787855ljj.14.2016.08.30.12.21.59 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 30 Aug 2016 12:22:00 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-wireless@freebsd.org, =?utf-8?Q?Otac=C3=ADlio?= Subject: Re: urtwn instable on Beaglebone Black References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> Date: Tue, 30 Aug 2016 22:21:44 +0300 Cc: "freebsd-arm@freebsd.org" , freebsd-usb@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 19:22:10 -0000 Tue, 30 Aug 2016 21:33:28 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Otac=C3=ADlio = : I have no ideas here (it works (mostly) fine on x86 and I have no = possibility to check it with ARM). P.S. Other (ARM-specific?) issues: https://lists.freebsd.org/pipermail/freebsd-arm/2016-July/014382.html https://forums.freebsd.org/threads/57396 > Dears > > I'm using a beaglebone black to stream video over UDP. I wrote a = > software and have tested it using a urtwn device + webcam Logitech C92= 0. = > All is connected using a USB hub with external power source. So urtwn = = > and webcam, both are plugged in the same USB hub. When I plug the hub = = > and run my software on a old notebook intel centrino with FreeBSD = > 11.0-RC2 AMD64 all works fine. Last night the system stream video all = = > night. But, when I replace the notebook by beaglebone black running = > FreeBSD 11.0-RC1 with the same USB HUB, the same wrtwn device and same= = > camera, randomly after some time the beaglebone black network shutdown= = > and terminal shows this messages : > > > Network is down > % urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > > Then, I need to run > > /etc/rc.d/netif stop > > /etc/rc.d/netif start > > To enable network again. So, someone can give me a hit about what can = be = > this and how to fix? > > Thanks a lot > > []'s > > -Otacilio > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-usb@freebsd.org Tue Aug 30 23:32:54 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B33E8BC9C41; Tue, 30 Aug 2016 23:32:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D953869; Tue, 30 Aug 2016 23:32:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id l203so48304604oib.1; Tue, 30 Aug 2016 16:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dk0YSShG+hmpEv+wM2EeCELou4faoqef4eV2FPToa4U=; b=h5auOXtq7OCOYaO6HTJICxCALAC3oFsrGllLkafn57g4PE0Oljf8vpxMRq/DvM763u d+AOWtybEgyi8X7LmZ8lkHKXkDWjaa00kVoLbtvTgctEEoFu4pICv8XWkinujY1JSdMV b8R2ztsxFwE5TPLISfPDTxdV8MGmIpDM4tQHWIH8UbABzqdhoIxph9g09HIuECGyEpE0 ZP/2gQZC6QT3luFJHqFOLltdDVV1Ud8VyUHy4TspldzduSY+D4a7M+kBZun4jGgRZ5lz gURL7iXeUgD3bfw0NTiT/zQEzYDEzszwexKLW4oOOiruukciASKsnIXwv+AmLeJv2SJU GLbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dk0YSShG+hmpEv+wM2EeCELou4faoqef4eV2FPToa4U=; b=VP1Q6jV+e12j4+wNY5q2Shgbr1zyhzwnoNjMs+/T+DpzdBYm/OzzPB/14+U1ty0GUP RH58E3xysQWAWgH7Bk+GX281e5cXdwClGNPt3+ub78yLIFViWEwxaMDFyczpOEZJ0nqx XUT6qooukomjpVPVVCT/r4R4xAQZX1kwo08+P0MmB5YS8pzLOpudJ43vaYY20F80WUph vSYhcSZI4DvYmRtWwqjYSn2tx9WhzZcUOKlcLMghdNdfIWN4F+QA4RHom44n+j3VJbzG nhC5b+tBre2awDnvjMsLFbEqAgAFOTYEw5chl3t2v99OduQMVrTgyHNsCUtrTvHZ4V31 JVXg== X-Gm-Message-State: AE9vXwP3rqfhpAu6ON2iJI1HZA1hJQ27MyqJbqiXV+NVray+npCRGqRjfVHv6felkzWOheX25DuMCLkj8hCiHQ== X-Received: by 10.157.35.85 with SMTP id k21mr7249385otd.41.1472599973668; Tue, 30 Aug 2016 16:32:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Tue, 30 Aug 2016 16:32:50 -0700 (PDT) In-Reply-To: References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> From: Adrian Chadd Date: Tue, 30 Aug 2016 16:32:50 -0700 Message-ID: Subject: Re: urtwn instable on Beaglebone Black To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" , "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 23:32:54 -0000 hi, What's the signal level? (ifconfig -v wlan0 list sta) -a On 30 August 2016 at 12:21, Andriy Voskoboinyk wrote: > Tue, 30 Aug 2016 21:33:28 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Otac=C3=ADlio > : > > I have no ideas here (it works (mostly) fine on x86 and I have no > possibility > to check it with ARM). > > P.S. Other (ARM-specific?) issues: > https://lists.freebsd.org/pipermail/freebsd-arm/2016-July/014382.html > https://forums.freebsd.org/threads/57396 > > > >> Dears >> >> I'm using a beaglebone black to stream video over UDP. I wrote a softwar= e >> and have tested it using a urtwn device + webcam Logitech C920. All is >> connected using a USB hub with external power source. So urtwn and webca= m, >> both are plugged in the same USB hub. When I plug the hub and run my >> software on a old notebook intel centrino with FreeBSD 11.0-RC2 AMD64 al= l >> works fine. Last night the system stream video all night. But, when I >> replace the notebook by beaglebone black running FreeBSD 11.0-RC1 with t= he >> same USB HUB, the same wrtwn device and same camera, randomly after some >> time the beaglebone black network shutdown and terminal shows this messa= ges >> : >> >> >> Network is down >> % urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> urtwn0: ieee80211_crypto_encap returns NULL. >> >> Then, I need to run >> >> /etc/rc.d/netif stop >> >> /etc/rc.d/netif start >> >> To enable network again. So, someone can give me a hit about what can be >> this and how to fix? >> >> Thanks a lot >> >> []'s >> >> -Otacilio >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >> "freebsd-wireless-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-usb@freebsd.org Tue Aug 30 23:33:38 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64B17BC9D01; Tue, 30 Aug 2016 23:33:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CE8893C; Tue, 30 Aug 2016 23:33:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id e124so12806768ith.0; Tue, 30 Aug 2016 16:33:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bmHAv4CY1J62OaJVtLYitGhOluWfK4ilgDOgEa+9vlY=; b=CsBO0tE8JLd8l2h7eBnPBg3C/UfEq0ZLfj6/wFkzqoUbez9PQnFv9bMLWSL8RPQrv9 lBdzGGd+rKX47kYIVavCOHpGGATZDqieZ78aY6qkuOJEAPbhWvnYLj6Mzil0z9MkNv4K uXo3OftyEj9DWYm8MfgSibCNSFestqfS/tbgjxNCCi3SGEOF6nj/0cMHnGvdC8HgPAKM bB0QFGZeoTOx9ANgv+iG4K55uOZA1Rof9k1oYfNzwvuW3ETjahNGNagrQO78X3c67o20 /4YpianQE41/wezfgtgBQ1P2AcAjnDxSipEAmZnAUhuo0r5pR2vIhvCATaU/ewyvmmWk UjEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bmHAv4CY1J62OaJVtLYitGhOluWfK4ilgDOgEa+9vlY=; b=P/QgHr8G1qIEk080pgW3pAu4HHE45y+Gwykfvr7KKO32QWRIZkBSZDeBsLUOAxFsPn BmyhpUd9zePmzAOsQN6wOpW2DF7W4O17+I79v53U312kkNOEmscm+nYMpl2diU+r+KUM w1M4o/Vl0X/M+Ef2wpc5NAsK2SvtR+K10YLnMt6FB2ICr6F2V9ZZRObO8UmjgDI2d9iQ pMQ2gTie9NikF4IWuNchgGJHzgaBtaYvElWm1XQgwzIytXKbdFbMqrIdMRm4l10tUwPq 6slC2kEHPs9D6cALchTT1d1XXWBTgBu/XjQU7kEbXkawgyyEFS8JoxdwK82hpouI5CEi 53wA== X-Gm-Message-State: AE9vXwOmlr5rKal4Ix1bgqfB1tQiulJqlcajj/hsxZZHZm/BThEjc6U+WvXJlns5to2aYWIV2yu1v9ZfSIdUAw== X-Received: by 10.36.150.70 with SMTP id z67mr25915253itd.80.1472600017558; Tue, 30 Aug 2016 16:33:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Tue, 30 Aug 2016 16:33:36 -0700 (PDT) In-Reply-To: References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> From: Adrian Chadd Date: Tue, 30 Aug 2016 16:33:36 -0700 Message-ID: Subject: Re: urtwn instable on Beaglebone Black To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" , "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 23:33:38 -0000 .. and which chipset? (dmesg | grep urtwn) -a On 30 August 2016 at 16:32, Adrian Chadd wrote: > hi, > > What's the signal level? (ifconfig -v wlan0 list sta) > > > > -a > > > On 30 August 2016 at 12:21, Andriy Voskoboinyk wrote: >> Tue, 30 Aug 2016 21:33:28 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Otac=C3=ADlio >> : >> >> I have no ideas here (it works (mostly) fine on x86 and I have no >> possibility >> to check it with ARM). >> >> P.S. Other (ARM-specific?) issues: >> https://lists.freebsd.org/pipermail/freebsd-arm/2016-July/014382.html >> https://forums.freebsd.org/threads/57396 >> >> >> >>> Dears >>> >>> I'm using a beaglebone black to stream video over UDP. I wrote a softwa= re >>> and have tested it using a urtwn device + webcam Logitech C920. All is >>> connected using a USB hub with external power source. So urtwn and webc= am, >>> both are plugged in the same USB hub. When I plug the hub and run my >>> software on a old notebook intel centrino with FreeBSD 11.0-RC2 AMD64 a= ll >>> works fine. Last night the system stream video all night. But, when I >>> replace the notebook by beaglebone black running FreeBSD 11.0-RC1 with = the >>> same USB HUB, the same wrtwn device and same camera, randomly after som= e >>> time the beaglebone black network shutdown and terminal shows this mess= ages >>> : >>> >>> >>> Network is down >>> % urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> urtwn0: ieee80211_crypto_encap returns NULL. >>> >>> Then, I need to run >>> >>> /etc/rc.d/netif stop >>> >>> /etc/rc.d/netif start >>> >>> To enable network again. So, someone can give me a hit about what can b= e >>> this and how to fix? >>> >>> Thanks a lot >>> >>> []'s >>> >>> -Otacilio >>> >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to >>> "freebsd-wireless-unsubscribe@freebsd.org" >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.o= rg"