Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Mar 2022 12:34:06 -0700
From:      bob prohaska <fbsd@www.zefox.net>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-net@freebsd.org, Free BSD <freebsd-arm@freebsd.org>
Subject:   Re: Erratic ping behavior, was Re: Pi3 answers ssh only if outbound ping is running on -current
Message-ID:  <20220313193406.GA65568@www.zefox.net>
In-Reply-To: <8936EFD1-F1FD-48CF-9ED3-4D42595464DC@yahoo.com>
References:  <20220212185618.GA37391@www.zefox.net> <34F5C092-7C35-4CBB-9CC3-99E373D1F785@yahoo.com> <F5FC2E50-C1E8-4E84-B4D4-DC7BFC3C9C14@yahoo.com> <20220215034924.GA46139@www.zefox.net> <8F9A6C9A-69BF-4D42-9886-A3F08BCB2EA0@yahoo.com> <506CD1A7-3D34-4E1B-AEAA-A1A819C6CC73@yahoo.com> <B186B406-233A-4765-9B1B-EB8136D01F2B@yahoo.com> <20220216231826.GA54961@www.zefox.net> <64138E81-2415-4D4A-A31A-D901DC53EB01@yahoo.com> <8936EFD1-F1FD-48CF-9ED3-4D42595464DC@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
It looks as if things are somewhat altered, but not really
improved,  after updating to 

FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #24 stable/13-n249989-b85d0d603c5: Sat Mar 12 17:47:19 PST 2022     bob@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64

on the Pi3 with USB root disk (hdd, not ssd).

After reboot the machine answered around 30 % of incoming pings and
sometimes responded to ssh login attempts. At least once the login
attempt was successful, even with no outgoing ping process running.
That seems like progress.

With an outgoing ping running it's possible to ssh into the machine,
with a highly variable delay for the password prompt.

Unfortunately, new console errors are appeared:

bob@pelorus:~ % (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 1f ea a3 c0 00 00 40 00 
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
(da0:umass-sim0:0:0:0): Retrying command (per sense data)

The error message repeated at intervals, seemingly linked to disk activity,
with the machine running out of retries after starting buildworld. 
That seems like progress in reverse 8-)

Reverting to 13-n249985-dd6c1475a63: Fri Mar 11 18:06:31 PST 2022
permitted recovery, with the old problems attendant.
 
-current now has some usb testing tools:
root@www:/usr/src # ls tools/tools/usbtest
Makefile		usb_control_ep_test.c	usb_msc_test.c		usbtest.c
Makefile.depend		usb_modem_test.c	usb_msc_test.h		usbtest.h

Is there any guidance on what they do? I couldn't find a man page.

Thanks for reading,

bob prohaska




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220313193406.GA65568>