From owner-freebsd-usb@freebsd.org Sun Aug 26 21:00:18 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F3561081F67 for ; Sun, 26 Aug 2018 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2F49C70D00 for ; Sun, 26 Aug 2018 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E235C1081F65; Sun, 26 Aug 2018 21:00:17 +0000 (UTC) Delivered-To: usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0F921081F62 for ; Sun, 26 Aug 2018 21:00:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76AA770CF8 for ; Sun, 26 Aug 2018 21:00:17 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C509FC168 for ; Sun, 26 Aug 2018 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7QL0GxD067738 for ; Sun, 26 Aug 2018 21:00:16 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7QL0GWV067737 for usb@FreeBSD.org; Sun, 26 Aug 2018 21:00:16 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201808262100.w7QL0GWV067737@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: usb@FreeBSD.org Subject: Problem reports for usb@FreeBSD.org that need special attention Date: Sun, 26 Aug 2018 21:00:16 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 21:00:18 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 213877 | xhci reset causes panic on SuperMicro A1SRi-2758F 1 problems total for which you should take action. From owner-freebsd-usb@freebsd.org Tue Aug 28 16:41:31 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A345110913CF for ; Tue, 28 Aug 2018 16:41:31 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 211818C44D for ; Tue, 28 Aug 2018 16:41:31 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id y2-v6so2589117wma.1 for ; Tue, 28 Aug 2018 09:41:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CyXePtNjxVL5rEctcUed+0arsqQbtPzSKwLwJP4YfBg=; b=NNfIKoUk7vucuv76AcfrvpRjCSuQ1YtyD0T2nDaLtRSWvBhZRvsoMO2s2FwuiTsrIB e+w3KDQpvAjTFxxtq9Mu2HSP2h/G7y4WooJwO9UnwtkqDP3R7pAzn0JTDmU2pcSdot35 hUv7R8MTgt6B6NvWq6iHoNjGkJkvX1/T1glqX2PDS/9Jdst/QqmweAa9K7xCf8Bxz5uS nWBZaSvZOsYPOS72adV/WM8l+paZWlfHhofCYgaVW5YhaMImZzu/ruM5gOcbsjSxgozt TJ14VM70aC+UH6QG6pJtb9NrcgN3vqX/pP5GMaQ3iQSYpCoI3twzTvSMoXDfcKxNBLgw vwxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CyXePtNjxVL5rEctcUed+0arsqQbtPzSKwLwJP4YfBg=; b=UQquu81Pm1MDhL8ch17bymaBpk1/gm5W5ZsT55SrPNTcTUluPkFVMwdgTdcx2QVOpc 1+dAEg0sUku093vziBXRAXXjkhACoE8G5rOGOrWMKqjMpvDIWHXO8wGutC6OyF9RQhUn qbfF8MDna6L2p37QTOckwwaX12GDmAPqXHoLV1Bgi43trcYAyX/ZDJNRxjFuFW/4bArd Gibkc0LUfR56B/F26lgNAwdjTwhDoL6eluUMErGKbuzscy7PxKG6y3ekSmlgujPuSqVG wTt/vadpWGZygFU0ZUpXd58TM2PK1XuXXD1Nq4lUUZJfMfi1fgjoFL6alKlBFIG3S/o1 SRcQ== X-Gm-Message-State: APzg51Cib4aIus9b5m9wf96VBlIEUJ3+KYC9QtLvxe+WICH+EpqX2Bcg dBZMtI5TsdTGGPoQ8CxPBARj0SJDJxES5L9WPnNa2PlM X-Google-Smtp-Source: ANB0VdbcpPcmBkhaTzQswZCL6mLdLzllIu1fnUKQY28OKNpFZdAUoSZmz8tNNhIvuZZ5ddJPeAPZB/T5ePXWbduKy9k= X-Received: by 2002:a1c:b709:: with SMTP id h9-v6mr1757477wmf.130.1535474490092; Tue, 28 Aug 2018 09:41:30 -0700 (PDT) MIME-Version: 1.0 References: <679a5fd9-a3ee-b4a6-8a0c-6a1a7b850154@selasky.org> <7683a29a-2323-69ec-8f98-094980de62e7@selasky.org> In-Reply-To: From: Rajesh Kumar Date: Tue, 28 Aug 2018 22:11:18 +0530 Message-ID: Subject: Re: Is FreeBSD-current XHCI 1.1 compliant? To: hps@selasky.org Cc: freebsd-usb@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 16:41:31 -0000 Hi Hans, We have tried using a SSD disk with a USB 3.1 gen 2 to SATA bridge device (XHCI 1.1). The disk is detected and usable. But seems it works in "Bulk-Only" mode. Is there any plans to support USB attached SCSI? I see a tunable "hw.usb.xhci.streams" to enable USB streams. But seems it does nothing much. On Thu, Aug 9, 2018 at 2:12 PM Rajesh Kumar wrote: > Ok Hans, I don't have any XHCI 1.1 device at this point. I raised the > question in general to know the state in FreeBSD. If I come across any > inputs, I will definitely update the group. > > Thanks. > > On Thu, Aug 9, 2018 at 1:59 PM Hans Petter Selasky > wrote: > >> On 08/09/18 10:25, Rajesh Kumar wrote: >> > No, I am not aware of any changes to be done specifically. But just >> wanted >> > to know whether the -CURRENT code is compliant to the latest standard. >> > >> > What I understand is, with XHCI 1.1, USB 3.1 is supported with speed of >> > upto 10Gbps. But freebsd xhci manpage says, it supports upto USB 3.0 >> with >> > speed upto 5Gbps. So, just wondering whether anything done in FreeBSD >> with >> > respect to XHCI 1.1 (or) any plans for the same? >> > >> > Anyway, Thanks for the quick turn-around. >> >> Hi, >> >> The FreeBSD XHCI driver does not use the speed information provided by >> the XHCI PCI descriptors currently nor any internal registers. Even if >> the device is 10Gbps capable it will be listed as 5Gbps. If you have an >> XHCI 1.1 device and the FreeBSD XHCI driver works, we might want to >> update the manual page. >> >> --HPS >> >> From owner-freebsd-usb@freebsd.org Tue Aug 28 19:05:12 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2791F1095644 for ; Tue, 28 Aug 2018 19:05:12 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 B91C492AB4 for ; Tue, 28 Aug 2018 19:05:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 64F412602FE; Tue, 28 Aug 2018 21:05:03 +0200 (CEST) Subject: Re: Is FreeBSD-current XHCI 1.1 compliant? To: Rajesh Kumar Cc: freebsd-usb@freebsd.org References: <679a5fd9-a3ee-b4a6-8a0c-6a1a7b850154@selasky.org> <7683a29a-2323-69ec-8f98-094980de62e7@selasky.org> From: Hans Petter Selasky Message-ID: Date: Tue, 28 Aug 2018 21:04:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 19:05:12 -0000 On 8/28/18 6:41 PM, Rajesh Kumar wrote: > Hi Hans, > > We have tried using a SSD disk with a USB 3.1 gen 2 to SATA bridge device > (XHCI 1.1). The disk is detected and usable. But seems it works in > "Bulk-Only" mode. Is there any plans to support USB attached SCSI? I see a > tunable "hw.usb.xhci.streams" to enable USB streams. But seems it does > nothing much. Hi, Streams mode is disabled by default (hw.usb.xhci.streams=0) and we have no drivers using it :-( --HPS From owner-freebsd-usb@freebsd.org Thu Aug 30 08:58:50 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 705C71099239 for ; Thu, 30 Aug 2018 08:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD0978095 for ; Thu, 30 Aug 2018 08:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C682E1099235; Thu, 30 Aug 2018 08:58:49 +0000 (UTC) Delivered-To: usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BD571099234 for ; Thu, 30 Aug 2018 08:58:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CCD578090 for ; Thu, 30 Aug 2018 08:58: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 75407146B3 for ; Thu, 30 Aug 2018 08:58:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7U8wmQX063606 for ; Thu, 30 Aug 2018 08:58:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7U8wm7Y063605 for usb@FreeBSD.org; Thu, 30 Aug 2018 08:58:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 213877] xhci reset causes panic on SuperMicro A1SRi-2758F board Date: Thu, 30 Aug 2018 08:58:47 +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-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bz@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: usb@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? 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.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 08:58:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213877 Bjoern A. Zeeb changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bz@FreeBSD.org --- Comment #11 from Bjoern A. Zeeb --- I keep getting this almost every night as of recently when trying to move d= ata to an external disk: xhci0: Resetting controller^M^M (da1:umass-sim1:1:0:0): WRITE(10). CDB: 2a 00 00 00 e1 d0 00 00 10 00 ^M^M (da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error^M^M (da1:umass-sim1:1:0:0): Retrying command^M^M (da1:umass-sim1:1:0:0): WRITE(10). CDB: 2a 00 00 00 e1 d0 00 00 10 00 ^M^M (da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error^M^M (da1:umass-sim1:1:0:0): Retrying command^M^M uhub1: at usbus1, port 1, addr 1 (disconnected)^M^M ugen1.2: at usbus1 (disconnected)^M^M uhub2: at uhub1, port 2, addr 1 (disconnected)^M^M ugen1.3: at usbus1 (disconnected)^M^M umass1: at uhub1, port 5, addr 2 (disconnected)^M^M (da1:umass-sim1:1:0:0): WRITE(10). CDB: 2a 00 00 00 e1 d0 00 00 10 00 ^M^M (da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error^M^M (da1:umass-sim1:1:0:0): Retrying command^M^M da1 at umass-sim1 bus 1 scbus8 target 0 lun 0^M^M ... Neither the plugged in media nor the kernel have changed in a few weeks however, so not sure what triggered it. The follow-up is a geom/file system panic. Is there a way to find out why xhci is resetting? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Aug 30 10:06:44 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF8E4109AB8F for ; Thu, 30 Aug 2018 10:06:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6D1FB7A41D for ; Thu, 30 Aug 2018 10:06:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3139D109AB8C; Thu, 30 Aug 2018 10:06:44 +0000 (UTC) Delivered-To: usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20067109AB8B for ; Thu, 30 Aug 2018 10:06:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B47427A417 for ; Thu, 30 Aug 2018 10:06:43 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E813F14D40 for ; Thu, 30 Aug 2018 10:06:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7UA6gdV073410 for ; Thu, 30 Aug 2018 10:06:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7UA6gef073409 for usb@FreeBSD.org; Thu, 30 Aug 2018 10:06:42 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 213877] xhci reset causes panic on SuperMicro A1SRi-2758F board Date: Thu, 30 Aug 2018 10:06:43 +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-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: usb@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: 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.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 10:06:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213877 --- Comment #12 from Hans Petter Selasky --- > Is there a way to find out why xhci is resetting? Try to set: hw.usb.xhci.debug=3D16 Or inspect the XHCI code for the reset call. There are a few cases currently for reset. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Aug 30 13:56:10 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7855B109F2F8 for ; Thu, 30 Aug 2018 13:56:10 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA0C28196D for ; Thu, 30 Aug 2018 13:56:09 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wr1-x435.google.com with SMTP id v17-v6so8164942wrr.9 for ; Thu, 30 Aug 2018 06:56:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DIncZkxAKJqSqe3Jtq0mPMoKHY/etR3nSkU003RKje4=; b=mbIm4VhL1AcsmmkesAM3fcmqLeeZgu+T7vTbaOt79B9Yr5F7QyE/wCy/RbnyLu445U Fz8MEm2rZRZ6bX+uPlpQwHvHIxskmeFpX3mhBxuClgoOs8tAmrROjlPDR21rD8MEYwrO F6LlxckuLly7x0t/e/Hg6j8l1xeXCs315dqHJQOANB8mOY38pkD6QMIPctcs6A1/HjaK 1tuiUfcnDiU0wjKwxzWutlo5HGEDUNwAPbP+Dp+Yhh42I+4cWra+JV+DMwmMhnNxecU5 R155tZHrMLKl7nPwERTGKh5a75dzt75VVlBb0Q5NDe5puZr7aPNVjKgeRU72qhH+ejLB a6jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DIncZkxAKJqSqe3Jtq0mPMoKHY/etR3nSkU003RKje4=; b=hWIxZpcaFLZmWyso8ROzoV3dNFwY7ePeWaB3toxqw3BxajckGutDK9KRYMZhzgBP6X qEDWfO0F8ZLF5LwTv6cdKOS5rN8Mt4+mYRR9+OaxL2ezJRWAgFu2ZoYs7o+Ozx2FwC4o qG8dehbz083D20q5G+0Sx+YNSmjMr0d2ZNxaatkKn/XaqFmAC3nJ9/nGDKqc37GrqWel nuQl8ZjX5rHjsg8gtmgoVgy5R94ALxjEKpe0FBcNayzyw692af4rU6bcgYO3nReWtIKU G/8IspBdd/oJ/0k8y3niEpdwGXc8qq9woz7Puv1B+SEupKOOk57ss9eznK9Ncc68THrN 8XtQ== X-Gm-Message-State: APzg51B1cKzSyID978wsxXbvGGb5Vs0WeFzdG1a4pwtsQv6TPOi4oiuM 7PSa0JVwIjTWe9VWbnuo8vueYlxmfAn7Ei+gH9PItQ== X-Google-Smtp-Source: ANB0VdY0YOIPxa02H+Zzf9BS474lzD5rL3DcJGUMry4hGTUJLCcrLZHwsj15o2+Xn2FDLhqxeufJl/xyGOicxg4m5Mg= X-Received: by 2002:adf:ad34:: with SMTP id p49-v6mr7975943wrc.10.1535637368941; Thu, 30 Aug 2018 06:56:08 -0700 (PDT) MIME-Version: 1.0 References: <679a5fd9-a3ee-b4a6-8a0c-6a1a7b850154@selasky.org> <7683a29a-2323-69ec-8f98-094980de62e7@selasky.org> In-Reply-To: From: Rajesh Kumar Date: Thu, 30 Aug 2018 19:25:57 +0530 Message-ID: Subject: Re: Is FreeBSD-current XHCI 1.1 compliant? To: hps@selasky.org Cc: freebsd-usb@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 13:56:10 -0000 Thanks Hans. We tried to gather some storage performance benchmarking numbers. But we are seeing poor benchmark number with USB 3.1 gen1/gen2 when compared with SATA (For test, we connected a SATA SSD using direct SATA cable (or) through a USB-SATA bridge). So, just enabled streams mode (hw.usb.xhci.streams=1) with no luck (expected, as you say no drivers are currently using it). After a quick debug, seems UE_GET_BULK_STREAMS(ecomp->bmAttributes) returns 0. So, Default mode (may be BULK) is chosen instead of streams mode. So, does using streams mode helps in improving the storage performance with USB? If so, what is needed to use streams mode effectively? Do we need to consider anything else when taking USB performance numbers in FreeBSD? On Wed, Aug 29, 2018 at 12:35 AM Hans Petter Selasky wrote: > On 8/28/18 6:41 PM, Rajesh Kumar wrote: > > Hi Hans, > > > > We have tried using a SSD disk with a USB 3.1 gen 2 to SATA bridge device > > (XHCI 1.1). The disk is detected and usable. But seems it works in > > "Bulk-Only" mode. Is there any plans to support USB attached SCSI? I > see a > > tunable "hw.usb.xhci.streams" to enable USB streams. But seems it does > > nothing much. > > Hi, > > Streams mode is disabled by default (hw.usb.xhci.streams=0) and we have > no drivers using it :-( > > --HPS > From owner-freebsd-usb@freebsd.org Thu Aug 30 16:57:30 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6238610A3E39 for ; Thu, 30 Aug 2018 16:57:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 049D08A08C for ; Thu, 30 Aug 2018 16:57:29 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 3B8EF26039F; Thu, 30 Aug 2018 18:57:28 +0200 (CEST) Subject: Re: Is FreeBSD-current XHCI 1.1 compliant? To: Rajesh Kumar Cc: freebsd-usb@freebsd.org References: <679a5fd9-a3ee-b4a6-8a0c-6a1a7b850154@selasky.org> <7683a29a-2323-69ec-8f98-094980de62e7@selasky.org> From: Hans Petter Selasky Message-ID: Date: Thu, 30 Aug 2018 18:57:01 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 16:57:30 -0000 On 8/30/18 3:55 PM, Rajesh Kumar wrote: > So, does using streams mode helps in improving the storage performance with > USB? If so, what is needed to use streams mode effectively? Do we need to > consider anything else when taking USB performance numbers in FreeBSD? Hi, Streams mode might help with latency, that you can queue more transfers at the same time. Also streams mode used to be controversial, that not all hardware manufacturers supported it. USB is no replacement for a PCI hardware device or a SATA controller. The block size effectively decides the performance of your device. The USB XHCI controller has a configurable IRQ limit of 16000 IRQ/s. At this rate you can queue at most 4000-8000 SCSI jobs per second towards the USB SCSI implementation. If you use small block size, performance drops. If you use bigger block size, performance increase. In /usr/src/tools you'll find a small utility that benchmark USB storage devices, called usbtest. Beware it can brick your USB disk. --HPS From owner-freebsd-usb@freebsd.org Fri Aug 31 15:06:27 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A85BFCDEBC for ; Fri, 31 Aug 2018 15:06:27 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic306-20.consmr.mail.ir2.yahoo.com (sonic306-20.consmr.mail.ir2.yahoo.com [77.238.176.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01D5E777E6 for ; Fri, 31 Aug 2018 15:06:26 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: nsvwAJsVM1mM4.Itmcz.pKkSFD81k1Bs9w8lBkcsi0ZfcXHAv2Ie_oX_eiIi0Ib jidMjN.H8u2as23cN8LHfL1sbtdWbF09g4Z7nhBFlsQ2BrSVhPocb4sisxZfHdFgDf0UQPOdbswr wKOdvBCM.HBtOgatntE_uNFgY.IPWlZfZtx7GpaRa8RkgX5xUlpiRnMvKAzieP6E1iBoqw6pBcwM OXTdFCBWSlaLSobQzKbbLbjsBGGH4.0WIftMl8U4Lx_k5QXSelyVJH9iSl4wJSJCXx5Up2s7pY8d iMTrLq5lAxbsZgld7QAHDK.wXh7bftI0b1kLW5CB5NJ4JIQP9Cyt_fhjke8iC44VGHPBLYl.ubAj QY.6s61dvQ8qQK1Vqy0B8nwAvdpLY4ACOHVcq8ZrGpQB8qsdL.S19Jj.vv9ZCqGlucp6BRpMptYs yADEjLNQsjXvpKu9D_jVqUCne45.M9CQgysZQ85ILOqBf8kyvkkQ.P.Mz6X13.Jzyv3yHzi58C0A HU8jXdhKjzclw.GgFyjryKI7jna3upIJdaaGNMc1Dc84plrBUn.ap3mnaoJF.uOh7Gvd0jx9c0xl aCsNuuMd.8GJ_Z..D_eexipeXEgZZbhHUdeeE3opuv1pJgEsJgGU0cTsaIz4Z0UcNtBX7tNOw7t5 t4_9w4oaGpNu3Uk5sava0bE45axWQuufVD6Mk31O7gLUrs8azN3h.0EQlapifqN0pSSuzlpLT8TY xUhWgMnX6gEcn8IM07mpdFqgTrTPxsPAWhYb3CTVzg.ymDit6cglpZyk2pSc8bFG48nwcU7Y4pVz e_Rubj0yHn9Hb.7a3Fp81_YIGblom6cnoPsjJbVwc2IBglwu.bcAXSUenbjVzD.xv0uHStK29XCl 1CXi1Y2VRmZDnG0vqXqYwlyDvRbAU85.D7yVHYIGowv6wx9VwBzTduJB9UJuxeTG3qx7Na_VrxVf CeoYJBuzG17ssb.QSqutznhS4pl1N.pF0f5p9bDxBH2CuWF5e.PzdzR0hh33bN5a3ZYHoskNpror BA0.fxL..CbhNSUcdc3d.JZu5Uw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ir2.yahoo.com with HTTP; Fri, 31 Aug 2018 15:06:20 +0000 Received: from 108.161.151.160 (EHLO [188.125.73.26]) ([108.161.151.160]) by smtp402.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID dc666d86c093dd4953b0a215edac5cdc for ; Fri, 31 Aug 2018 15:06:15 +0000 (UTC) To: freebsd-usb@freebsd.org From: Per Gunnarsson Subject: CM108B USB adapter with mono microphone Message-ID: <41d612b6-0734-26a4-57d8-fad3bb88edea@yahoo.com> Date: Fri, 31 Aug 2018 17:06:10 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 15:06:27 -0000 Hello! I failed to set the recording volume for this adapter. Writing a driver for it was more than I bargained for, so I decided to collect some information about it in a web page directory. https://mustafejen.se/~per/tmp/debug/CM108B pcm and rec seem stuck on 45 no matter how I try to configure it. Regards, Per Gunnarsson From owner-freebsd-usb@freebsd.org Fri Aug 31 16:00:01 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90B0BFCEFB5 for ; Fri, 31 Aug 2018 16:00:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 341BC793E4 for ; Fri, 31 Aug 2018 16:00:00 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 1737C26016D; Fri, 31 Aug 2018 17:59:52 +0200 (CEST) Subject: Re: CM108B USB adapter with mono microphone To: Per Gunnarsson , freebsd-usb@freebsd.org References: <41d612b6-0734-26a4-57d8-fad3bb88edea@yahoo.com> From: Hans Petter Selasky Message-ID: <616efa1d-915c-7ba0-d650-419c0a3c4ff7@selasky.org> Date: Fri, 31 Aug 2018 17:59:25 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <41d612b6-0734-26a4-57d8-fad3bb88edea@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 16:00:01 -0000 On 8/31/18 5:06 PM, Per Gunnarsson via freebsd-usb wrote: > Hello! > > I failed to set the recording volume for this adapter. Writing a driver > for it was more > than I bargained for, so I decided to collect some information about it > in a web page > directory. > > https://mustafejen.se/~per/tmp/debug/CM108B > > pcm and rec seem stuck on 45 no matter how I try to configure it. > Did you try looking at the sysctl mixer nodes? sysctl -a | grep pcm --HPS From owner-freebsd-usb@freebsd.org Sat Sep 1 15:20:30 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B494BFF2429 for ; Sat, 1 Sep 2018 15:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 52A2E8FEAC for ; Sat, 1 Sep 2018 15:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 12B07FF2428; Sat, 1 Sep 2018 15:20:30 +0000 (UTC) Delivered-To: usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4E9FFF2427 for ; Sat, 1 Sep 2018 15:20:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 745AA8FEAB for ; Sat, 1 Sep 2018 15:20:29 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 883652F4E9 for ; Sat, 1 Sep 2018 15:20:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w81FKS4Q097834 for ; Sat, 1 Sep 2018 15:20:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w81FKSSt097831 for usb@FreeBSD.org; Sat, 1 Sep 2018 15:20:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 231076] libusb_cancel_transfer() does NOT cancel a transfer after the USB device is removed Date: Sat, 01 Sep 2018 15:20:28 +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.4-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ludovic.rousseau+freebsd@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.27 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2018 15:20:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231076 Bug ID: 231076 Summary: libusb_cancel_transfer() does NOT cancel a transfer after the USB device is removed Product: Base System Version: 10.4-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: usb Assignee: usb@FreeBSD.org Reporter: ludovic.rousseau+freebsd@gmail.com I am the author of the CCID driver: a driver for smart card readers complia= nt to the USB CCID specification. My driver uses /usr/lib/libusb.so.3 $ ldd /usr/local/lib/pcsc/drivers/ifd-ccid.bundle/Contents/FreeBSD/libccid.= so=20 /usr/local/lib/pcsc/drivers/ifd-ccid.bundle/Contents/FreeBSD/libccid.so: libusb.so.3 =3D> /usr/lib/libusb.so.3 (0x2821c000) libthr.so.3 =3D> /lib/libthr.so.3 (0x2822d000) libc.so.7 =3D> /lib/libc.so.7 (0x2807a000) In my driver I use a transfer on an USB interrupt pipe to wait for card movements events (a card is inserted or removed in the reader) with a timeo= ut of 10 minutes. I use the asynchronous calls of libusb. The source of my function InterruptRead() is available at https://github.com/LudovicRousseau/CCID/blob/master/src/ccid_usb.c#L1294 When a USB reader is removed I have to cleanup and unload the driver so it cancels any transfer on the interrupt pipe. To do that I use libusb_cancel_transfer() in my function InterruptStop(). see https://github.com/LudovicRousseau/CCID/blob/master/src/ccid_usb.c#L1380 My problem is that libusb_cancel_transfer() returns with LIBUSB_ERROR_NOT_F= OUND (because the USB device has been removed and is no more present?) and the current transfer is NOT cancelled. My driver is still blocked in the libusb_handle_events_completed() waiting for the function to return. I looked at the FreeBSD libusb code. The error code LIBUSB_ERROR_NOT_FOUND = is returned just at the beginning of the libusb_cancel_transfer() function at https://github.com/freebsd/freebsd/blob/master/lib/libusb/libusb10.c#L1501 I have no patch to propose. Maybe libusb_cancel_transfer() should try to wake up libusb_handle_events_completed() even if the USB device is no more present. The problem is very easy to reproduce on my side. --=20 You are receiving this mail because: You are the assignee for the bug.=