From nobody Mon Apr 11 13:59:10 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2C5F21A94A65 for ; Mon, 11 Apr 2022 13:59:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KcVpH0m3yz3G1x for ; Mon, 11 Apr 2022 13:59:18 +0000 (UTC) (envelope-from hps@selasky.org) Received: from [10.36.2.165] (unknown [176.74.213.87]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 4CE99260189; Mon, 11 Apr 2022 15:59:10 +0200 (CEST) Message-ID: <8dc68431-ad3d-84db-45b4-cd661d4a15df@selasky.org> Date: Mon, 11 Apr 2022 15:59:10 +0200 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: Raspberry Pi 3B Over-current USB Content-Language: en-US To: Archimedes Gaviola Cc: freebsd-arm@freebsd.org References: <5deaf68b-267c-56dd-603d-8ec0d82ceae2@selasky.org> From: Hans Petter Selasky In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KcVpH0m3yz3G1x X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-3.13 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.83)[-0.828]; MLMMJ_DEST(0.00)[freebsd-arm]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 4/11/22 15:59, Archimedes Gaviola wrote: > Hi Hans, > > Noted on the self-powered hub, thanks for the suggestion, I will try. > > Just wanted to share the observation from the testing I've conducted with > my Raspberry Pi 4B with the same 14.0-CURRENT to check if overcurrent is > also experienced and it did, there was overcurrent and each ports' power > shut-off during the situation but it was able to recover back. I initiated > the command 'usbconfig reset' and each port gloriously came back alive one > by one and loaded my USB keyboard and Prolific uplcom(4) drivers into > functional and operational states. My measuring device is showing the same > amount of current 460mA while the voltage stayed at 5.05 from a baseline of > 5.15 voltshttps://filebin.net/10vy575q6h2yl8og. Unlike my RPi 3B, voltage > dropped to 4.93 from a baseline of 5.19 volts. So, the difference I > observed is when the voltage dropped below 5, the system will not give a > chance to make the ports come back alive as a sort of protection mechanism. > Sharing to you the logs below (with hw.usb.uhub.debug=1). FreeBSD does not actively check and use "bMaxPower" . --HPS