| All Things FreeBSDComments for FreeBSD developer's notebook

Comment on Building image for Raspberry Pi: up to date version by Dustin Dawes

Dustin Dawes — Tue, 14 May 2013 20:40:28 +0000

As I tried to compile NodeJS (I know, ridiculous :p).. Does the current FreeBSD ARM support HardFloat, and if not.. are you aware of any work on adding HFloat support?

Comment on FreeBSD/armv6 in QEMU by jpulz

jpulz — Mon, 13 May 2013 14:28:43 +0000

Oleksandr,

i’ve several difficulties with arm and QEMU.
I downloaded your prebuilt kernel and tried it in QEMU (1.4.0 and 1.4.1 from ports)
It hangs at every boot attempt, the last line is:
Timecounters tick every ….
sometimes there is a number printed sometimes not.
I decided to check out a fresh current to built it by myself and got it booting till it tries to mount the root fs. This failed because the driver for the “Versatile PCI controller” failed to attach (some memory related error).
The obvious thing is that i have to start QEMU with -m 512M (512Mb of RAM) otherwise the QEMU window stays black forever. I tried to set some different values for the amount of memory in “sys/boot/fdt/dts/versatilepb.dts” but it changes nothing. The kernel is only booting with -m 512M.
Today i rolled my CURRENT back to r244479 (right before “Replace generic ARM11 option with more specific support for ARM1136 and ARM1176″)
With this state i can boot the kernel, the “Versatile PCI controller” and the sym driver are working and i can successfully load the userland image. But i have to use -m 512M otherwise it’s not working.
Now if i try to use network together with r244479 the whole thing breaks with different errors. The most errors i see are from QEMU and look like this and are printed out hundred times:
vpb_sic_write: Bad register offset 0xd44
qemu: hardware error: smc91c111_write: Bad reg 0:2

together with the following message in the running versatilepb system:
: jemalloc_chunk.c:203: Failed assertion: “p[i] == 0″
interrupt storm detected on “intr31:”; throttling interrupt source

As far as i can see from the kernel boot messages the “kmi0 (PL050 Keyboard/Mouse Interface)” device is using irq31.

It looks like as it could all be related to the “-m 512M” argument but i’m not sure.
Can you shed some some light into this? Is a fresh CURRENT working for you as expected in QEMU?

Kind regards
Joerg

Comment on Building image for Raspberry Pi: up to date version by Matatu

Matatu — Wed, 08 May 2013 12:02:49 +0000

I’ve tried to build the world with gcc, it breaks after 1 day compiling with
an error.

gcc -O -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/arm -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -I/usr/src/lib/libc/../../contrib/libc-vis -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/jemalloc/include -I/usr/src/lib/libc/../../contrib/tzcode/stdtime -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -I/usr/src/lib/libc/arm/softfloat -I/usr/src/lib/libc/softfloat -DSOFTFLOAT_FOR_GCC -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c accept4.S
accept4.S: Assembler messages:
accept4.S:3: Error: undefined symbol `SYS_accept4′ in operation
*** [accept4.o] Error code 1

Stop in /usr/src/lib/libc.
*** [lib/libc__L] Error code 1

Stop in /usr/src.
*** [libraries] Error code 1

Stop in /usr/src.
*** [_libraries] Error code 1

Stop in /usr/src.
*** [buildworld] Error code 1

Comment on Building image for Raspberry Pi: up to date version by Josef Larsson

Josef Larsson — Tue, 07 May 2013 18:19:04 +0000

Last time I checked, the clang-compiler built with world had the same version number as clang-devel in ports.

If GCC won’t do for the world compilation, I do not think you can build world on the Pi before that bug is fixed.

Comment on Building image for Raspberry Pi: up to date version by Matatu

Matatu — Tue, 07 May 2013 14:09:15 +0000

Ok, now I’m running in the same problem, tried to compile my first world directly on the pi. When sending my first post, I thought this was related to the llvm port and not to the world itself. Do you have a solution in the meanwhile?

Comment on Building image for Raspberry Pi: up to date version by Josef Larsson

Josef Larsson — Mon, 06 May 2013 08:41:03 +0000

Knew that already, but thanks anyway. Another approach is to set USE_GCC=any in the makefile of the port in question.

Comment on Building image for Raspberry Pi: up to date version by Matatu

Matatu — Mon, 06 May 2013 02:35:16 +0000

If not known, it’s possible to switch from clang to gcc (which is still part
of the base system), you have only to redefine CC, CXX and CPP in your
/etc/make.conf . Not all ports will compile with clang at the moment.

Comment on Building image for Raspberry Pi: up to date version by Josef Larsson

Josef Larsson — Sat, 04 May 2013 18:33:28 +0000

Managed to get it running as a router now with USB ethernet. Thank you very much . It seems to be running at less than full speed but I have to test it thoroughly to say so confidently.

One interesting behaviour is that ping latency seems to cycle in the following fashion for both ethernet cards: 10 ms, 9 ms, 8ms, … , 1ms, 10 ms, 9ms, 8ms, …, 1 ms and round again.

Another problem seems to be the C++-compiler that get some kind of memory alignment error everytime I use it. (http://llvm.org/bugs/show_bug.cgi?id=15696)

Comment on Building image for Raspberry Pi: up to date version by gonzo

gonzo — Fri, 03 May 2013 18:27:08 +0000

I’ll be looking into this issue soon. Hope to find permanent solution for this bug.

Comment on Building image for Raspberry Pi: up to date version by Matatu

Matatu — Sat, 27 Apr 2013 13:17:46 +0000

This is a little bit annoying, two of my three different sd cards need these settings. Unfortunately, the problem does not occur at every reboot, so I’ve noticed it late. I made automatic reboot loops (100 reboots) to find it out. With both affected cards it occurs only in ~ 10% of the reboots. With these settings it does not occur.