From owner-freebsd-usb@freebsd.org Fri Dec 20 23:46:18 2019 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 939011E6D56 for ; Fri, 20 Dec 2019 23:46:18 +0000 (UTC) (envelope-from denverh@comcast.net) Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (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 47flkc5Kf6z4ZM7 for ; Fri, 20 Dec 2019 23:46:16 +0000 (UTC) (envelope-from denverh@comcast.net) Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-03v.sys.comcast.net with ESMTP id iRXSiUsde6kCOiRyHiF97d; Fri, 20 Dec 2019 23:46:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1576885573; bh=dxwvrDBCsdLOnmLugFn9WDfKibsQp4S/VtxqudTzXIU=; h=Received:Received:Reply-To:Subject:To:From:Message-ID:Date: MIME-Version:Content-Type; b=s99OY01CjepkcqjlENhv/AnnEbUrT2jA1iEIgozJ5claQqGDQAJjtYSncZ1m7Bio0 K5WSS6Xw0vdJEKUTnQfENcpzVHLosy4+T5sDIYobIjAwYyKU3Mjcb7LeM27FTkR3sn zuoy5ME2C7qc8y8utrXiKwSt/IF1HEhUlzby2cybEooz3k6wvy17MoeXhHLAVARQQL cXscbe3cdFDIF8n/9KGPMjo7ZOVNd9bfgfopLh2ybHqTT/qoQDG5E+V9V8A7iWikO1 GU8i/5+3jb76G89k2qC3PhGX0k04xEgAoP/5+4/pLEeRwsA9OJHtFK4+OJyJqGzkyt N9gXIBadQ4gvw== Received: from dhbsd.dhull.home ([104.129.31.27]) by resomta-po-06v.sys.comcast.net with ESMTPA id iRy6iGEhcEbhMiRy7iw2T2; Fri, 20 Dec 2019 23:46:11 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedufedrvddugedguddtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucenucfjughrpehruffvfhfhkffffgggjggtsehmtderredtfeejnecuhfhrohhmpeffvghnvhgvrhcujfhulhhluceouggvnhhvvghrhhestghomhgtrghsthdrnhgvtheqnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecukfhppedutdegrdduvdelrdefuddrvdejnecurfgrrhgrmhephhgvlhhopeguhhgsshgurdguhhhulhhlrdhhohhmvgdpihhnvghtpedutdegrdduvdelrdefuddrvdejpdhmrghilhhfrhhomhepuggvnhhvvghrhhestghomhgtrghsthdrnhgvthdprhgtphhtthhopehfrhgvvggsshguqdhushgssehfrhgvvggsshgurdhorhhgpdhrtghpthhtohephhhpshesshgvlhgrshhkhidrohhrghenucevlhhushhtvghrufhiiigvpedt X-Xfinity-VMeta: sc=0.00;st=legit Reply-To: denverh@comcast.net Subject: Re: Timeouts during initial Mode Sense commands To: Hans Petter Selasky , freebsd-usb@freebsd.org References: <98b6599e-5027-48c9-4230-47bc0f087180@comcast.net> From: Denver Hull Message-ID: <079c989a-5d45-df1f-ed48-15cdd8c8f194@comcast.net> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: X-Rspamd-Queue-Id: 47flkc5Kf6z4ZM7 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=comcast.net header.s=20190202a header.b=s99OY01C; dmarc=pass (policy=none) header.from=comcast.net; spf=pass (mx1.freebsd.org: domain of denverh@comcast.net designates 2001:558:fe16:19:96:114:154:162 as permitted sender) smtp.mailfrom=denverh@comcast.net X-Spamd-Result: default: False [-0.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[denverh@comcast.net]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:558:fe16:19:96:114:154:160/123]; FREEMAIL_FROM(0.00)[comcast.net]; HAS_ATTACHMENT(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[comcast.net:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[comcast.net,none]; HFILTER_HELO_5(3.00)[resqmta-po-03v.sys.comcast.net]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[2.6.1.0.4.5.1.0.4.1.1.0.6.9.0.0.9.1.0.0.6.1.e.f.8.5.5.0.1.0.0.2.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:7922, ipnet:2001:558::/29, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[comcast.net.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[comcast.net]; R_DKIM_ALLOW(-0.20)[comcast.net:s=20190202a]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; FREEMAIL_REPLYTO(0.00)[comcast.net]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ipnet: 2001:558::/29(-0.39), asn: 7922(-0.46), country: US(-0.05)] X-Mailman-Approved-At: Sun, 02 Feb 2020 11:32:50 +0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Fri, 20 Dec 2019 23:46:18 -0000 X-Original-Date: Fri, 20 Dec 2019 17:46:01 -0600 X-List-Received-Date: Fri, 20 Dec 2019 23:46:18 -0000 Hans Petter Selasky wrote: > On 2019-12-20 13:54, Denver Hull wrote: >> Hans Petter Selasky wrote: >>> On 2019-12-19 01:11, Denver Hull wrote: >>>> Hello, >>>> >>>> I have several different microcontroller boards that are supposed >>>> to appear as storage devices when plugged in.  They work fine on >>>> Linux systems, but on FreeBSD 11.3 and 12.1 they don't show up at >>>> all. Here's what dmesg shows for one of them: >>>> >>>> ugen1.3: at usbus1 >>>> umodem0 on uhub1 >>>> umodem0: on usbus1 >>>> umodem0: data interface 1, has no CM over data, has no break >>>> umass3 on uhub1 >>>> umass3: on usbus1 >>>> umass3:  SCSI over Bulk-Only; quirks = 0x0000 >>>> umass3:5:3: Attached to scbus5 >>>> uaudio0 on uhub1 >>>> uaudio0: on usbus1 >>>> uaudio0: No playback. >>>> uaudio0: No recording. >>>> uaudio0: MIDI sequencer. >>>> uaudio0: No HID volume keys found. >>>> ums2 on uhub1 >>>> ums2: on usbus1 >>>> ums2: 16 buttons and [XYZ] coordinates ID=2 >>>> (da3:umass-sim3:3:0:0): got CAM status 0x44 >>>> (da3:umass-sim3:3:0:0): fatal error, failed to attach to device >>>> g_access(944): provider da3 has error 6 set >>>> g_access(944): provider da3 has error 6 set >>>> g_access(944): provider da3 has error 6 set >>>> g_access(944): provider da3 has error 6 set >>>> g_access(944): provider da3 has error 6 set >>>> >>>> There's a definite delay after the last ums message.  I used >>>> camcontrol debug in single user mode on a bare 12.1 system to get a >>>> little more information about what was happening. It looks like the >>>> initial Inquiry and Test Unit Ready commands succeed, but the next >>>> Mode Sense command times out, as well as all subsequent commands. >>>> There are several seconds of inactivity between retries, and >>>> there's no sense data, so I'm assuming that indicates timeout. >>>> >>>> At this point I'm not sure how best to proceed to get these devices >>>> to work, so any help will be appreciated. >>>> >>> >>> Did you try setting one or more quirks for these devices using >>> usbconfig? >>> >>> UQ_MSC_NO_TEST_UNIT_READY >>> UQ_MSC_NO_RS_CLEAR_UA >>> UQ_MSC_NO_START_STOP >>> UQ_MSC_NO_GETMAXLUN >>> UQ_MSC_NO_INQUIRY >>> UQ_MSC_NO_INQUIRY_EVPD >>> UQ_MSC_NO_PREVENT_ALLOW >>> UQ_MSC_NO_SYNC_CACHE >>> UQ_MSC_SHUTTLE_INIT >>> UQ_MSC_ALT_IFACE_1 >>> UQ_MSC_FLOPPY_SPEED >>> UQ_MSC_IGNORE_RESIDUE >>> UQ_MSC_WRONG_CSWSIG >>> UQ_MSC_RBC_PAD_TO_12 >>> UQ_MSC_READ_CAP_OFFBY1 >>> UQ_MSC_FORCE_SHORT_INQ >>> >>> If you run "usbdump -i usbusX -f Y -s 65536 -vvv" you might see the >>> last failing SCSI command. X.Y are numbers after ugen for your device. >>> >>> Likely your device has a software bug in its USB/SCSI >>> implementation, which is quite common unfortunately. >>> >>> --HPS >>> >> After I sent the previous message I did try >> UQ_MSC_NO_TEST_UNIT_READY. Although the system reports "quirks = >> 0001", the initial TUR is still being issued during the probe >> sequence.  I tried the usbdump command you suggested, and I can >> clearly see where the timeouts are, and frames that begin with "USBC" >> seem to contain a SCSI CDB.  But there's a lot of other stuff in >> between that I haven't been able to figure out, so I've attached a >> sample.  Hopefully it will help. >> > > Hi, > > All the USBC's are raw SCSI commands, which use the following layout: > >> /* Command Block Wrapper */ >> typedef struct { >>         uDWord  dCBWSignature; >> #define CBWSIGNATURE    0x43425355 >>         uDWord  dCBWTag; >>         uDWord  dCBWDataTransferLength; >>         uByte   bCBWFlags; >> #define CBWFLAGS_OUT    0x00 >> #define CBWFLAGS_IN     0x80 >>         uByte   bCBWLUN; >>         uByte   bCDBLength; >> #define CBWCDBLENGTH    16 >>         uByte   CBWCDB[CBWCDBLENGTH]; >> } __packed umass_bbb_cbw_t; > > We had a SoC to add support for the usbdump format to wireshark: > > https://wiki.freebsd.org/SummerOfCode2017/usbdump-wireshark > > You might find that useful. > > My first suspicion is that your device is not fully USB class > compliant, and that's why it is STALLING and failing to recover. > > --HPS > > I checked on a Linux system, and the negotiation follows a slightly different pattern, but as far as I can see, the biggest difference is that Linux uses 6 byte Mode Sense commands instead of 10 byte.  I wonder if that's all that's making the device choke?  How hard would it be to change things to use 0x1a instead of 0x5a temporarily? Alternatively, I could see if I can figure out how to issue arbitrary SCSI commands on Linux.  I used to have something for that purpose that worked on a variety of platforms, but it's been ages since I needed it.  In any case, I'll attach the Linux wireshark trace.  The negotiation seems to begin at frame 2331. Thanks, Denver From owner-freebsd-usb@freebsd.org Sun Feb 2 13:13:53 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5F46C22E298 for ; Sun, 2 Feb 2020 13:13:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x844.google.com (mail-qt1-x844.google.com [IPv6:2607:f8b0:4864:20::844]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 489Wcc4BNBz47pg for ; Sun, 2 Feb 2020 13:13:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x844.google.com with SMTP id l19so9305085qtq.8 for ; Sun, 02 Feb 2020 05:13:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MOBOACE8iTk2+OG7wzd37/V4iw5Jz6sqrRUnm9JrAI4=; b=Euw3LVX5LHWQsSYBS3/0GcUIhKJ/20jI58/GPdr/MTS/d9VC6QwcVepMCQkKfrE+aw 0oKFidJjRbY5X42UhrVdJ7/tIrMgiBEsHHM6yUefhIUsGugtHuaFKETW5blj4hfCJLB7 UtcWwL1s1oqvU8r0PWPDfloLpQYD8IyTY57eGIpJ9/FmeznmtuLH77rCio2Xdd1nb40i 3jD8fSDE68reSOLoPqBRqvYHTTKEx3RYukKm5O/ZSJH8+RrnJG/CQ7CRSip0A7N5BieB SoXqlIj0KMU3mT6snCu30TCOKL+RefFQizTjm8qkisaLsdjB5s7r6h+oLDgr4z+SyscC h31Q== 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=MOBOACE8iTk2+OG7wzd37/V4iw5Jz6sqrRUnm9JrAI4=; b=kqY29w+v0YkwsS044+mjcifGBjWs9wP1eF53pDj2e4YdUED1DCVYVzzyJDfGPAW2Fr mmXagLcp9NuHWN9bdKLlIJnB0sIrs1UpsiDvQYNxGlghe8hFxwX4S+vnoSdRQC9oDx1V t7eAnta4kRJNyDfaMqrr8o1gl4T5PaeaxXc9g4QY8/PG2GVrTux5yzCVppC0hGAkfVHf cWGmViJW42l2L61vJruI/BnUgRKyJMpSMANN/XId5mPXcLFZYvjSDvTQ5MFK8dxMBJeY amA4bL/AsR0k8BuMquMJODS0+z4aXfJpMEkplBEu3RBx2gnbl0DkWSSlzWTIYjM9hbsc 8wXw== X-Gm-Message-State: APjAAAWVS9BIKP0sap/VHoy40FFzwrVBSeXbddSvb8RriXUrmDGPRQGW svsGCVY8344FN/Wl7dRsZR16StN2gqLF+wKhBbNJTU0VWgP9TA== X-Google-Smtp-Source: APXvYqwlNBfU3vAJ8ZyrTHc8DEpusP2JYVJXlLkl+c/RhGfnL7tYrGkCA7P3ukTsShVwKWbC9ZFRQSGVRdzjlf4L9zw= X-Received: by 2002:ac8:1e08:: with SMTP id n8mr19335738qtl.175.1580649231606; Sun, 02 Feb 2020 05:13:51 -0800 (PST) MIME-Version: 1.0 References: <98b6599e-5027-48c9-4230-47bc0f087180@comcast.net> <079c989a-5d45-df1f-ed48-15cdd8c8f194@comcast.net> In-Reply-To: <079c989a-5d45-df1f-ed48-15cdd8c8f194@comcast.net> From: Warner Losh Date: Sun, 2 Feb 2020 14:13:40 +0100 Message-ID: Subject: Re: Timeouts during initial Mode Sense commands To: denverh@comcast.net Cc: Hans Petter Selasky , "freebsd-usb@FreeBSD.org" X-Rspamd-Queue-Id: 489Wcc4BNBz47pg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=Euw3LVX5; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::844) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-1.31 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.99)[-0.992,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.977,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-usb@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[4.4.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[comcast.net]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-0.34)[ip: (2.12), ipnet: 2607:f8b0::/32(-2.00), asn: 15169(-1.76), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2020 13:13:53 -0000 On Sun, Feb 2, 2020 at 12:32 PM Denver Hull wrote: > Hans Petter Selasky wrote: > > On 2019-12-20 13:54, Denver Hull wrote: > >> Hans Petter Selasky wrote: > >>> On 2019-12-19 01:11, Denver Hull wrote: > >>>> Hello, > >>>> > >>>> I have several different microcontroller boards that are supposed > >>>> to appear as storage devices when plugged in. They work fine on > >>>> Linux systems, but on FreeBSD 11.3 and 12.1 they don't show up at > >>>> all. Here's what dmesg shows for one of them: > >>>> > >>>> ugen1.3: at usbus1 > >>>> umodem0 on uhub1 > >>>> umodem0: on usbus1 > >>>> umodem0: data interface 1, has no CM over data, has no break > >>>> umass3 on uhub1 > >>>> umass3: on usbus1 > >>>> umass3: SCSI over Bulk-Only; quirks = 0x0000 > >>>> umass3:5:3: Attached to scbus5 > >>>> uaudio0 on uhub1 > >>>> uaudio0: on usbus1 > >>>> uaudio0: No playback. > >>>> uaudio0: No recording. > >>>> uaudio0: MIDI sequencer. > >>>> uaudio0: No HID volume keys found. > >>>> ums2 on uhub1 > >>>> ums2: on usbus1 > >>>> ums2: 16 buttons and [XYZ] coordinates ID=2 > >>>> (da3:umass-sim3:3:0:0): got CAM status 0x44 > >>>> (da3:umass-sim3:3:0:0): fatal error, failed to attach to device > >>>> g_access(944): provider da3 has error 6 set > >>>> g_access(944): provider da3 has error 6 set > >>>> g_access(944): provider da3 has error 6 set > >>>> g_access(944): provider da3 has error 6 set > >>>> g_access(944): provider da3 has error 6 set > >>>> > >>>> There's a definite delay after the last ums message. I used > >>>> camcontrol debug in single user mode on a bare 12.1 system to get a > >>>> little more information about what was happening. It looks like the > >>>> initial Inquiry and Test Unit Ready commands succeed, but the next > >>>> Mode Sense command times out, as well as all subsequent commands. > >>>> There are several seconds of inactivity between retries, and > >>>> there's no sense data, so I'm assuming that indicates timeout. > >>>> > >>>> At this point I'm not sure how best to proceed to get these devices > >>>> to work, so any help will be appreciated. > >>>> > >>> > >>> Did you try setting one or more quirks for these devices using > >>> usbconfig? > >>> > >>> UQ_MSC_NO_TEST_UNIT_READY > >>> UQ_MSC_NO_RS_CLEAR_UA > >>> UQ_MSC_NO_START_STOP > >>> UQ_MSC_NO_GETMAXLUN > >>> UQ_MSC_NO_INQUIRY > >>> UQ_MSC_NO_INQUIRY_EVPD > >>> UQ_MSC_NO_PREVENT_ALLOW > >>> UQ_MSC_NO_SYNC_CACHE > >>> UQ_MSC_SHUTTLE_INIT > >>> UQ_MSC_ALT_IFACE_1 > >>> UQ_MSC_FLOPPY_SPEED > >>> UQ_MSC_IGNORE_RESIDUE > >>> UQ_MSC_WRONG_CSWSIG > >>> UQ_MSC_RBC_PAD_TO_12 > >>> UQ_MSC_READ_CAP_OFFBY1 > >>> UQ_MSC_FORCE_SHORT_INQ > >>> > >>> If you run "usbdump -i usbusX -f Y -s 65536 -vvv" you might see the > >>> last failing SCSI command. X.Y are numbers after ugen for your device. > >>> > >>> Likely your device has a software bug in its USB/SCSI > >>> implementation, which is quite common unfortunately. > >>> > >>> --HPS > >>> > >> After I sent the previous message I did try > >> UQ_MSC_NO_TEST_UNIT_READY. Although the system reports "quirks = > >> 0001", the initial TUR is still being issued during the probe > >> sequence. I tried the usbdump command you suggested, and I can > >> clearly see where the timeouts are, and frames that begin with "USBC" > >> seem to contain a SCSI CDB. But there's a lot of other stuff in > >> between that I haven't been able to figure out, so I've attached a > >> sample. Hopefully it will help. > >> > > > > Hi, > > > > All the USBC's are raw SCSI commands, which use the following layout: > > > >> /* Command Block Wrapper */ > >> typedef struct { > >> uDWord dCBWSignature; > >> #define CBWSIGNATURE 0x43425355 > >> uDWord dCBWTag; > >> uDWord dCBWDataTransferLength; > >> uByte bCBWFlags; > >> #define CBWFLAGS_OUT 0x00 > >> #define CBWFLAGS_IN 0x80 > >> uByte bCBWLUN; > >> uByte bCDBLength; > >> #define CBWCDBLENGTH 16 > >> uByte CBWCDB[CBWCDBLENGTH]; > >> } __packed umass_bbb_cbw_t; > > > > We had a SoC to add support for the usbdump format to wireshark: > > > > https://wiki.freebsd.org/SummerOfCode2017/usbdump-wireshark > > > > You might find that useful. > > > > My first suspicion is that your device is not fully USB class > > compliant, and that's why it is STALLING and failing to recover. > > > > --HPS > > > > > I checked on a Linux system, and the negotiation follows a slightly > different pattern, but as far as I can see, the biggest difference is > that Linux uses 6 byte Mode Sense commands instead of 10 byte. I wonder > if that's all that's making the device choke? How hard would it be to > change things to use 0x1a instead of 0x5a temporarily? Alternatively, I > could see if I can figure out how to issue arbitrary SCSI commands on > Linux. I used to have something for that purpose that worked on a > variety of platforms, but it's been ages since I needed it. In any > case, I'll attach the Linux wireshark trace. The negotiation seems to > begin at frame 2331. > There's a DA_Q_NO_6_BYTE quirk, but that does rather the opposite of what I think is needed here. and we use it here: * RBC devices don't have to support READ(6), only READ(10). */ if (softc->quirks & DA_Q_NO_6_BYTE || SID_TYPE(&cgd->inq_data) == T_RBC) softc->minimum_cmd_size = 10; else softc->minimum_cmd_size = 6; but there's a way to override: * Load the user's default, if any. */ snprintf(tmpstr, sizeof(tmpstr), "kern.cam.da.%d.minimum_cmd_size", periph->unit_number); TUNABLE_INT_FETCH(tmpstr, &softc->minimum_cmd_size); so you could try setting the tunable kern.cam.da.X.minimum_cmd_size="6" in /boot/loader.conf (where X is the drive the system assigns) and see if that changes the wireshark output to be closer to Linux or not... I'm unsure if we have a direct way to ask if it's RBC or not... Warner From owner-freebsd-usb@freebsd.org Sun Feb 2 21:01:09 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C32D423AA81 for ; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 489jzn4j5wz4gKn for ; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id A134D23AA7D; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9F44F23AA7C for ; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 489jzn3jfXz4gKk for ; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 770611DE0A for ; Sun, 2 Feb 2020 21:01:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 012L1909025684 for ; Sun, 2 Feb 2020 21:01:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 012L19Rm025683 for usb@FreeBSD.org; Sun, 2 Feb 2020 21:01:09 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202002022101.012L19Rm025683@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, 2 Feb 2020 21:01:09 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2020 21:01:09 -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 Open | 233884 | Corsair CORSAIR K70 RGB MK.2 / K63 / K63 Wireless Open | 234578 | Support for Sierra Wireless EM7455 modem Open | 237666 | repeated messages of "uhub_reattach_port: giving 4 problems total for which you should take action. From owner-freebsd-usb@freebsd.org Thu Feb 6 12:21:09 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4623722AD04 for ; Thu, 6 Feb 2020 12:21:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48CyFx0vYfz3ymh for ; Thu, 6 Feb 2020 12:21:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1D35022AD03; Thu, 6 Feb 2020 12:21:09 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1CFAE22AD02 for ; Thu, 6 Feb 2020 12:21:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48CyFw6r6sz3ymg for ; Thu, 6 Feb 2020 12:21:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E62891B7AC for ; Thu, 6 Feb 2020 12:21:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 016CL8xT018741 for ; Thu, 6 Feb 2020 12:21:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 016CL8EE018697 for usb@FreeBSD.org; Thu, 6 Feb 2020 12:21:08 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 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Date: Thu, 06 Feb 2020 12:21:09 +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: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gerard_seibert@outlook.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: usb@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? 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.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2020 12:21:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 --- Comment #101 from Gerard Seibert --- Apparently, this problem has existed since at least April 2019. That seems,= at least to me, to be an awfully long time, at least at this level, for a bug = to go unsquashed. I am preparing to purchase another PC similar to the one I n= ow have to replace an older unit. It is apparent that FreeBSD 12.x will not operate on it correctly. I am starting to wonder if FreeBSD is the best platform for my use. If it is unable to run modern hardware, then perhaps it is time for me to investigate other operating systems. I would hate to start over with a new OS, but I do= n't seem to be left with too many other options. While 12.2 is still a long way off, 11.4 is due this summer. I am not even sure if that will work on my PC= or simple make the system unbootable. I guess my quest is if there is anyone actively working on this bug and what the prognosis is for this problem. I don't mean to sound crass, but this problem has gone on, in my opinion, f= ar too long. With newer systems coming on the market daily, I honestly believe that this problem will manifest into a much larger problem and potential embarrassment for FreeBSD. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Feb 6 13:18:25 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F45122BED3 for ; Thu, 6 Feb 2020 13:18:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48CzX102syz42Sw for ; Thu, 6 Feb 2020 13:18:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id F3ED022BED2; Thu, 6 Feb 2020 13:18:24 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F3B6522BECF for ; Thu, 6 Feb 2020 13:18:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48CzX06J77z42Sv for ; Thu, 6 Feb 2020 13:18:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D38F11C2AC for ; Thu, 6 Feb 2020 13:18:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 016DIO6M046322 for ; Thu, 6 Feb 2020 13:18:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 016DIOIO046321 for usb@FreeBSD.org; Thu, 6 Feb 2020 13:18:24 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 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Date: Thu, 06 Feb 2020 13:18:23 +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: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People 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-stable12? 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.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2020 13:18:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 --- Comment #102 from Hans Petter Selasky --- Hi, I have a no-name Skylake based laptop and USB XHCI works fine. You might find the following read interesting: http://freebsd.1045724.x6.nabble.com/Can-t-reattach-USB-devices-Lenovo-bug-= td6369656.html If I'm right, this issue has nothing to do with the generic USB/XHCI, it is entirely ACPI/BIOS related and you should bring it up with the vendor of yo= ur computer. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Feb 6 16:48:31 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8DD002303D0 for ; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48D4BR3Jk9z4Fl6 for ; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 7186B2303CA; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 714872303C7 for ; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48D4BR2M5yz4Fl5 for ; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3307C1EA47 for ; Thu, 6 Feb 2020 16:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 016GmVLg070840 for ; Thu, 6 Feb 2020 16:48:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 016GmVfJ070839 for usb@FreeBSD.org; Thu, 6 Feb 2020 16:48:31 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 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Date: Thu, 06 Feb 2020 16:48:31 +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: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gerard_seibert@outlook.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: usb@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? 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.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2020 16:48:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 --- Comment #103 from Gerard Seibert --- I just updated the BIOS on my system. That version was only one version old= er than the new one. Anyway, this is the output from 'dmidecode'. # dmidecode 3.2 # SMBIOS entry point at 0x6fe8d000 Found SMBIOS entry point in EFI, reading table from /dev/mem. SMBIOS 3.1 present. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.1.10 Release Date: 10/31/2019 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.1 Does anyone have any idea if this will correct the problem? I would really = hate to trash the whole system again if this doesn't correct the problem. Also, = why would this problem NOT exist on a FreeBSD 11.x (and perhaps older) system? = It only started with 12.x. I find it somewhat difficult to believe it is solel= y a BIOS version problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Thu Feb 6 16:58:50 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 49D67230B40 for ; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48D4QL1908z4Gdg for ; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 27D70230B3E; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 279FF230B3D for ; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48D4QL0Hfkz4Gdd for ; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0559E1EC54 for ; Thu, 6 Feb 2020 16:58:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 016GwnXT098180 for ; Thu, 6 Feb 2020 16:58:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 016Gwnew098179 for usb@FreeBSD.org; Thu, 6 Feb 2020 16:58:49 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 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Date: Thu, 06 Feb 2020 16:58:50 +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: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People 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-stable12? 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.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2020 16:58:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 --- Comment #104 from Hans Petter Selasky --- > Does anyone have any idea if this will correct the problem? I would reall= y hate to trash the whole system again if this doesn't correct the problem.= Also, why would this problem NOT exist on a FreeBSD 11.x (and perhaps olde= r) system? It only started with 12.x. I find it somewhat difficult to belie= ve it is solely a BIOS version problem. I think for the kind of debugging which is needed, physical access to your machine will be required. How much are you willing to pay to have this issue resolved? Can you for example donate or ship a machine to me (Norway) which have these problems and I can probably look into it in a 1-2 months time fr= ame. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.=