Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 May 2020 17:12:45 -0500 (CDT)
From:      Dan Mack <mack@macktronics.com>
To:        "Herbert J. Skuhra" <herbert@gojira.at>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: rpi4 headless experience
Message-ID:  <alpine.GSO.2.20.2005191710140.14202@localhost.local>
In-Reply-To: <20200519214259.GA16253@mail.bsd4all.net>
References:  <alpine.GSO.2.20.2005191521340.14202@localhost.local> <20200519214259.GA16253@mail.bsd4all.net>

next in thread | previous in thread | raw e-mail | index | archive | help

Thanks for you report info, especially the fact that you are having it see 
all your memory.  Perhaps this is an issue with different revisions of the 
rpi4 ?   I have a pre-Nov 2019 rpi4-4GB.

And I can confirm that reboot doesn't work, on my system, it does this:

root@generic:~ # reboot
May 14 12:28:56 generic reboot[1642]: rebooted by root
May 14 12:28:56 generic syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 2 0 0 done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... 
done
All buffers synced.
lock order reversal:
  1st 0xfffffd00012809f0 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1631
  2nd 0xfffffd00012f5438 devfs (devfs) @ 
/usr/src/sys/fs/msdosfs/msdosfs_vfsops.c:945
stack backtrace:
#0 0xffff00000047f440 at witness_debugger+0x64
#1 0xffff0000003e7794 at lockmgr_lock_flags+0x1d8
#2 0xffff0000004fa3c0 at _vn_lock+0x54
#3 0xffff0000002e5508 at msdosfs_sync+0x1a8
#4 0xffff0000002e512c at msdosfs_unmount+0x30
#5 0xffff0000004de514 at dounmount+0x430
#6 0xffff0000004e9034 at vfs_unmountall+0x8c
#7 0xffff0000004c4844 at bufshutdown+0x280
#8 0xffff000000415ea4 at kern_reboot+0x238
#9 0xffff000000415c00 at sys_reboot+0x338
#10 0xffff000000775a00 at do_el0_sync+0x3f8
#11 0xffff000000759224 at handle_el0_sync+0x90
Uptime: 1h49m6s





On Tue, 19 May 2020, Herbert J. Skuhra wrote:

> On Tue, May 19, 2020 at 03:32:07PM -0500, Dan Mack wrote:
>> Just tried the latest FreeBSD on RPI image on my rpi4-4GB system.  Here's
>> what I experienced in case anyone else is interested:
>>
>> - Install method - I just dd'd the unxz'd image from the download site
>>   onto a new microSD card.
>>
>> - used a serial port connected RPI to another RPI using a ttl to usb cable.
>>
>> - powered on, freebsd booted up just fine.
>>
>> root@generic:~ # uname -a ; df -h ; sysctl hw | grep physmem
>>   FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r361019: Thu May 14
>>   09:12:43 UTC 2020
>>   root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC  arm64
>>
>> Filesystem                Size    Used   Avail Capacity  Mounted on
>> /dev/ufs/rootfs            29G    2.6G     24G    10%    /
>> devfs                     1.0K    1.0K      0B   100%    /dev
>> /dev/msdosfs/MSDOSBOOT     50M     25M     25M    50%    /boot/msdos
>> tmpfs                      50M    4.0K     50M     0%    /tmp
>>
>>
>> hw.physmem: 973434880
>>
>> I pluged in a USB connected SSD and it was not recognized on either USB2 or
>> USB3 ports.
>>
>> And the memory size is not reporting the full 4GB as can be seen above.
>>
>> Ethernet is working without any changes (dhcp kicked in by default) and
>> seems to work.
>>
>> Not sure about the on-board WiFI.
>>
>> That's it, if anyone knows the status of the USB support or how to get the
>> system to see all the memory, let me know :-)
>
> Hmm, I am running r360723 (GENERIC) on my RPi4 and it shows "hw.physmem:
> 4127662080".
>
> I can confirm that USB (and Wifi) is not working:
>
> usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
> simplebus0: <usb@7e980000> mem 0x7e980000-0x7e98ffff,0x7e00b200-0x7e00b3ff irq 44,45 disabled compat brcm,bcm2708-usb (no driver attached)
> usb_needs_explore_all: no devclass
>
> Powerd reports "no cpufreq(4) support". No idea if it runs at full
> speed or not.
>
> I have two issues with the ethernet adapter (genet0):
>
> 1. Apparently, my RPi4 is sending icmp replies to the wrong destination!?
>
> Ping from laptop to RPi4:
>
> % ping -c 1 192.168.0.9
> PING 192.168.0.9 (192.168.0.9) 56(84) bytes of data.
>
> --- 192.168.0.9 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> tcpdump on laptop:
>
> 23:20:22.244458 IP 192.168.0.2 > 192.168.0.9: ICMP echo request, id 14, seq 1, length 64
> 23:20:22.244651 IP 192.168.0.9 > 192.168.255.191: ICMP echo reply, id 14, seq 1, length 64
>
> tcpdump on RPi4:
>
> 23:20:22.247490 IP 192.168.0.2 > 192.168.0.9: ICMP echo request, id 14, seq 1, length 64
> 23:20:22.247562 IP 192.168.0.9 > 192.168.0.2: ICMP echo reply, id 14, seq 1, length 64
>
> Ping from RPi4 is OK.
>
> 2. IPv6 (accept_rtadv) is not working.
>
> And the RPi does not reboot.
>
> -- 
> Herbert
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
>



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