From owner-freebsd-questions@freebsd.org Sat Nov 24 09:04:19 2018 Return-Path: Delivered-To: freebsd-questions@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 4312B1148055; Sat, 24 Nov 2018 09:04:19 +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 9F2AD6FB0A; Sat, 24 Nov 2018 09:04:18 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [178.17.145.230]) (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 1B8A82602D1; Sat, 24 Nov 2018 10:04:15 +0100 (CET) Subject: Re: kernel: uhub_reattach_port: giving up port reset - device vanished From: Hans Petter Selasky To: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org References: <20181123175136.GA37629@rpi3.zyxst.net> <3ccadeb1-274f-f1fe-dba7-52f2dca76db4@selasky.org> Message-ID: <7f31c23a-aedf-e532-b16d-f0d5a0edbbcf@selasky.org> Date: Sat, 24 Nov 2018 10:03:41 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <3ccadeb1-274f-f1fe-dba7-52f2dca76db4@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 9F2AD6FB0A X-Spamd-Result: default: False [-6.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[selasky.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; MX_GOOD(-0.01)[cached: mail.turbocat.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.97)[-0.966,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; IP_SCORE(-3.44)[ip: (-9.53), ipnet: 88.99.0.0/16(-4.81), asn: 24940(-2.81), country: DE(-0.02)]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2018 09:04:19 -0000 On 11/24/18 9:42 AM, Hans Petter Selasky wrote: > On 11/23/18 6:51 PM, tech-lists wrote: >> Hi, >> >> On a 12.0-BETA2 system, am seeing lots of this in /var/log/messages: >> >> uhub_reattach_port: giving up port reset - device vanished >> uhub_reattach_port: giving up port reset - device vanished >> uhub_reattach_port: giving up port reset - device vanished >> >> last message repeated 496 times >> >> There's only two things usb on this machine, a usb3 pci card (which has >> nothing plugged into it) and a usb2 wireless key plugged into the usb >> system built into the motherboard. It's detected as run0. The device >> works fine, doesn't drop packets. >> >> How can I debug this? Should I upgrade to 12-PRERELEASE (or whatever the >> latest is) first? > > Hi, > > There hasn't been any USB changes in this area. Likely you have a broken > or unsupported USB device, which doesn't enumerate properly. I see this > on my computer with a USB bluetooth device, which because it doesn't > receive valid firmware at first boot, becomes in-accessible. Maybe you > can disable some such USB devices in the BIOS. > > --HPS > BTW: There are some USB knobs to disable USB enumeration: sysctl -a | grep disable_enumeration --HPS