From nobody Wed May 4 15:41:25 2022 X-Original-To: freebsd-net@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 B3A661AB9742 for ; Wed, 4 May 2022 15:41:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ktgzl3wl3z4V6y for ; Wed, 4 May 2022 15:41:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 244FfVPj026733 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 4 May 2022 08:41:32 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 244FfPfi026732; Wed, 4 May 2022 08:41:25 -0700 (PDT) (envelope-from fbsd) Date: Wed, 4 May 2022 08:41:25 -0700 From: bob prohaska To: Hans Petter Selasky Cc: Bakul Shah , freebsd-net@freebsd.org, bob prohaska Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 Message-ID: <20220504154125.GA26674@www.zefox.net> References: <20220501232757.GA15446@www.zefox.net> <2F4599BF-EEDA-4D08-AB6E-7AA9F410B2C5@yahoo.com> <20220502011312.GA15807@www.zefox.net> <6f57cd1d-e1d4-5ca4-e301-2633c1d4c1fa@selasky.org> <20220502155334.GA17962@www.zefox.net> <0d131ec7-3c83-9470-7052-6a80af1bb574@selasky.org> <20220503022310.GA19378@www.zefox.net> List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220503022310.GA19378@www.zefox.net> X-Rspamd-Queue-Id: 4Ktgzl3wl3z4V6y X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-0.94 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.980]; NEURAL_HAM_MEDIUM(-0.86)[-0.856]; MLMMJ_DEST(0.00)[freebsd-net]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N After updating one of the troublesome Pi3s to FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #53 stable/13-n250662-0625715977d: Wed May 4 06:23:14 PDT 2022 bob@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 a series of error messages appeared on the serial console. I've not seen them before and wonder if they might be relevant to the connectivity problems lately seen. The machine was freshly-rebooted and at the time would not answer ping, though it did successfully set time using ntp. I got on the console to start an outbound ping, which usually sufficed to let inbound ssh connections work. Here's the console: Starting background file system checks in 60 seconds. Wed May 4 08:10:53 PDT FreeBSD/arm64 (pelorus.zefox.org) (ttyu0) login: bob Password: Last login: Tue May 3 09:01:03 from gateway.zefox.net FreeBSD 13.1-STABLE #53 stable/13-n250662-0625715977d: Wed May 4 06:23:14 PDT 2022 bob@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC [message of the day omitted] bob@pelorus:~ % ping 50.1.20.31 > ping.log & [1] 937 bob@pelorus:~ % May 4 08:12:19 pelorus su[952]: bob to root on /dev/pts/0 smsc0: error: usb error on tx: USB_ERR_IOERROR smsc0: warning: bulk read error, USB_ERR_IOERROR smsc0: warning: Failed to read register 0x118 smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x2c smsc0: warning: failed to read initial AFC_CFG, error 18 smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: at uhub1, port 1, addr 3 (disconnected) smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smscphy0: detached miibus0: detached smsc0: detached ping: sendto: No route to host usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_SHORT_XFER ping: sendto: No route to host smsc0 on uhub1 smsc0: on usbus1 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 smscphy0: PHY 1 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto smsc0: chip 0xec00, rev. 0002 ping: sendto: No route to host ping: sendto: No route to host There were no further ping errors and I was able to log in via ssh before noticing the errors on the console. An immediate run of usbconfig dump_stats reported: root@pelorus:/usr/home/bob # usbconfig dump_stats ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) { UE_CONTROL_OK : 0 UE_ISOCHRONOUS_OK : 0 UE_BULK_OK : 0 UE_INTERRUPT_OK : 0 UE_CONTROL_FAIL : 0 UE_ISOCHRONOUS_FAIL : 0 UE_BULK_FAIL : 0 UE_INTERRUPT_FAIL : 0 } ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) { UE_CONTROL_OK : 791 UE_ISOCHRONOUS_OK : 0 UE_BULK_OK : 0 UE_INTERRUPT_OK : 4 UE_CONTROL_FAIL : 0 UE_ISOCHRONOUS_FAIL : 0 UE_BULK_FAIL : 0 UE_INTERRUPT_FAIL : 0 } ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) { UE_CONTROL_OK : 15495 UE_ISOCHRONOUS_OK : 0 UE_BULK_OK : 1435 UE_INTERRUPT_OK : 0 UE_CONTROL_FAIL : 29 UE_ISOCHRONOUS_FAIL : 0 UE_BULK_FAIL : 2 UE_INTERRUPT_FAIL : 0 } ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) { UE_CONTROL_OK : 31 UE_ISOCHRONOUS_OK : 0 UE_BULK_OK : 25290 UE_INTERRUPT_OK : 0 UE_CONTROL_FAIL : 0 UE_ISOCHRONOUS_FAIL : 0 UE_BULK_FAIL : 3 UE_INTERRUPT_FAIL : 0 } ugen1.5: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) { UE_CONTROL_OK : 83 UE_ISOCHRONOUS_OK : 0 UE_BULK_OK : 5527 UE_INTERRUPT_OK : 0 UE_CONTROL_FAIL : 0 UE_ISOCHRONOUS_FAIL : 0 UE_BULK_FAIL : 61 UE_INTERRUPT_FAIL : 0 } root@pelorus:/usr/home/bob # Might this suggest any further experiments? I believe this is the first time errors other than on the boot drive have been reported using dump_stats. Thanks for reading, bob prohaska