vm_fault during BBB-boot

[Manuel Stühn]

Am 28.12.2014 um 20:36 schrieb Ian Lepore:
>> [...]
> So all in all, I'm out of ideas.  We should have nearly identical
> setups, except I didn't build with crochet, and thus I'm probably using
> a slightly different u-boot (a bit newer probably).  I don't see how
> that could lead to working vs. failing at this point.

I tried to find out, with which revision the error occurs. The last 
working revision of current is r276046. Updating to any revision higher 
than r276046 results in the vm_fault.

I tried also to update to actual current and revert the changes made 
with r276047 (Add -march=armv7a to the kernel compile for all ARM 
systems which are v7a.), but this leads into this:

U-Boot 2014.04 (Nov 24 2014 - 20:42:56)

I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
mmc0 is current device
SD/MMC found on device 0
reading bb-uEnv.txt
reading bbubldr
253170 bytes read in 18 ms (13.4 MiB/s)
reading bboneblk.dtb
16204 bytes read in 5 ms (3.1 MiB/s)
## Starting application at 0x88000054 ...
Consoles: U-Boot console
Compatible U-Boot API signature found @9f635510

FreeBSD/armv6hf U-Boot loader, Revision 1.2
(root at freebsd-vm, Tue Dec 30 00:15:04 CET 2014)

DRAM: 512MB
Number of U-Boot devices: 2
U-Boot env: loaderdev not set, will probe all devices.
Found U-Boot device: disk
   Probing all disk devices...
   Checking unit=0 slice=<auto> partition=<auto>... good.
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=0x590108+0x3fef8 syms=[0x4+0x893f0+0x4+0x52ff2]
/boot/kernel/geom_label.ko text=0x4608 data=0x768+0x4 
syms=[0x4+0xe40+0x4+0xe0a]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by U-Boot at address 0x80000100.
Kernel entry at 0x80200100...
Kernel args: (null)