Re: Rock64 flaky ethernet?

Mark Millard via freebsd-arm <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On 2021-May-8, at 12:40, Mark Millard <marklmi at yahoo.com> wrote:

> On 2021-May-8, at 12:19, Mark Millard <marklmi at yahoo.com> wrote:
> 
>> On 2021-May-8, at 10:42, Adriaan de Groot <adridg at freebsd.org> wrote:
>> 
>>> I've got an old-ish (2018 .. v2) Rock64 that hasn't been used much. I have 
>>> fetched and booted it into the 13-RELEASE image:
>>> 
>>> FreeBSD-13.0-RELEASE-arm64-aarch64-ROCK64.img.xz	452690956	2021-Apr-09 06:46
>>> 
>>> I have written this to an 8GB generic micro-SD card. For good measure, I have 
>>> written a recent Armbian image to the same brand and age of micro-SD card, so 
>>> I have comparison material. (I could also write everything to the 32GB eMMC 
>>> chip that's in the Rock64, if needed, but I'm holding off on that until I have 
>>> something that works).
>>> 
>>> After boot, dwc0 gets an address from DHCP, and I start pinging 10.0.0.2 in my 
>>> home network. I get ~3% packet loss if I'm lucky, more often around 7%. If I'm 
>>> pinging a machine in the network and also pinging my Rock64 from that machine, 
>>> I hit around 22% packet loss on both sides.
>> 
>> For my mid-March non-debug build of main [so: 14] I get,
>> for example, (.149 is the Rock64 V2.0; .120 is a
>> ThreadRipper 1950X, both going at the same time
>> here):
>> 
>> --- 192.168.1.149 ping statistics ---
>> 72 packets transmitted, 72 packets received, 0.0% packet loss
>> round-trip min/avg/max/stddev = 0.136/0.230/1.903/0.279 ms
>> 
>> --- 192.168.1.120 ping statistics ---
>> 81 packets transmitted, 81 packets received, 0.0% packet loss
>> round-trip min/avg/max/stddev = 0.211/0.241/0.286/0.013 ms
>> 
>> So, no problem observed.
>> 
>> The root file system is on a USB3 SSD. A removable eMMC is
>> involved in the booting but no microsd card is present.
>> 
>> For reference:
>> 
>> # ~/fbsd-based-on-what-freebsd-main.sh 
>> FreeBSD Rock64_RPi_4_3_2v1p2 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n245445-def0058cc690 GENERIC-NODBG  arm64 aarch64 1400005 1400005
>> def0058cc690 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git context.
>> merge-base: 7381bbee29df959e88ec59866cf2878263e7f3b2
>> merge-base: CommitDate: 2021-03-12 20:29:42 +0000
>> 7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all XPT_ASYNC ccbs in a dedicated thread
>> n245444 (--first-parent --count for merge-base)
>> 
>>> Armbian works fine - poweroff, swap SD card, power on - in the same setup.
>>> 
>>> With this kind of packet loss I can't really do anything with the board in 
>>> FreeBSD; `pkg bootstrap` for instance seems to sit there forever.
>>> 
>>> .. ok, digging in the archives gets me lots of threads from june/july 2020 
>>> about dwc timing, I'll dig through those first before carrying on.
>>> 
>>> [ade]
>>> 
>>> PS. Pine H6 never did catch on in FreeBSD-land, did it. Pity, I've got a 
>>> couple that I'd be happy enough to use instead of the Rock64 if they worked. 
>>> 
>> 
> 
> For reference as far as U-Boot goes:
> 
> U-Boot 2021.04 (Apr 09 2021 - 17:05:14 +0000)
> 
> Model: Pine64 Rock64
> DRAM:  4 GiB
> PMIC:  RK8050 (on=0x40, off=0x00)
> MMC:   mmc@ff500000: 1, mmc@ff520000: 0
> 
> It is from a sysutils/u-boot-rock64 build with no
> local patches. Previously 2020.10 was in use,
> also without problems. (But one of my non-debug
> builds of main was in use.)

I dd'd FreeBSD-13.0-RELEASE-arm64-aarch64-ROCK64.img to
a microsd card and booted it (no eMMC or USB storage
attached). This created .185 instead of the .149 for
networking:

--- 192.168.1.185 ping statistics ---
102 packets transmitted, 102 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.126/0.198/1.925/0.244 ms

--- 192.168.1.120 ping statistics ---
102 packets transmitted, 102 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.175/0.206/0.629/0.044 ms

(.120 is a ThreadRipper 1950X.)

Consistent with the past, it appears that various Rock64 v2.0's
may not be equivalent. At least for my context,
FreeBSD-13.0-RELEASE-arm64-aarch64-ROCK64.img of itself does not
seem to be a problem for the Rock64 v2.0 that I have access to.
That spans U-Boot and FreeBSD being the same as you tried.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.