From nobody Thu Nov 02 15:01:19 2023 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 4SLnBt0xFmz4yYT7 for ; Thu, 2 Nov 2023 15:01:26 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 4SLnBs2qRjz4ZSt for ; Thu, 2 Nov 2023 15:01:25 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=lOOirEWB; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=ZsPOvKRu; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AAF8B5C00AD for ; Thu, 2 Nov 2023 11:01:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 02 Nov 2023 11:01:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm3; t=1698937284; x=1699023684; bh=EquFvdBafOZ3IVx7QDX1Ui3gi CfC7slBTwVA+c7H10c=; b=lOOirEWBpb+8dE6UYk2DKnpb61LKIXrJj3uAV+t2u 9+3GqjdrleLyps9KBw9ZYz4AQz2Z35IsS+tvchVqLBsvI+vWFlZ+yLuMRK1+B+GT VIxcqC+BRd2q7TSSKO9yP+kFR3Q0sUgpzT4H/YkVGcrt8u/vKGZ017f8prf8xmL7 SwN2ZhMF9qZWej9OwiJfw8IqfwsN8qJGNB5vU1cg9QH4VhWQRgC5MVoH8XeGKnTy /+61c3K37aoUNNOOmUMUaTDjlTHe/ikRzgCUsELofSgGBrOc7cnKjke9hbwJ+pJM JDGk4WKFE05wT8d19VAjpAIVK3w+L5C6iy4nVDXD1IXqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1698937284; x=1699023684; bh=EquFvdBafOZ3IVx7QDX1Ui3giCfC7slBTwV A+c7H10c=; b=ZsPOvKRu4MI3Z9ihoENhQCv1ka9Y8BRsLBOnpZH8H8vVW5NcwE5 w/m//6P8AUKmh27cti9biWo86FEMVXydNreWiVDiFmaZm+Oz9+YPNz7jwUpSGPGx 6q8whSxHALZV2GDRhlUzvsUsRCkc/OW00RD3owlmvg+PmDG7cnVL5mdlZCcxzhd5 Zv5iBzwCS8AyS8cCU7vPFEsNSVp+H2U6rtngrnOkJHajXXgGwT2l67KBfNfOr/iP vK4jc0WQ37yoCCXKw2SswZUEoKNsqb2+sJ0cGL3yDtkHFGd2R267IUjJmAx7CYiY Hd+tjeREvbBgfFt3VjXDdyToEvv3rffmX1Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddtiedgjedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegff eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 2 Nov 2023 11:01:24 -0400 (EDT) Date: Thu, 2 Nov 2023 15:01:19 +0000 From: void To: freebsd-arm@freebsd.org Subject: usb2 problems when connecting multiple devices Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-4.70 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SLnBs2qRjz4ZSt X-Spamd-Bar: ---- I've noticed that when more than one device is connected to the onboard usb2 ports, one device's (signalling? i guess) interferes with the other, knocking it offline. It's happened in a number of contexts, only with this hardware: 1. where the os is 13-stable 2. recent 14-stable 3. usb2 is keyboard & wireless mouse 4. usb2 is run0: MAC/BBP RT5390 firmware RT3071 wlan0 & plain usb2 cable connecting to a UPS. 5. the pi4 has the recommended 3.1A PSU At the moment, I don't have a spare usb2 hub to plug into a usb2 port. I've worked around the situation previously, either by using a powered usb3 hub into a usb3 port and plugging the usb2 devices into the hub, and/or using just one usb2 device in one usb2 port and leaving the other on-board usb2 port empty. But both usb ports should be usable and not knock each other offline. How can I capture relevant information for this for a PR? --