Date: Tue, 2 Jan 2018 14:27:30 -0800 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: RPI2 boot hangs with red light on Message-ID: <20180102222730.GB10596@www.zefox.net>
next in thread | raw e-mail | index | archive | help
An RPI2 with sources at 327493
and kernel at 322520 makes and installs world and kernel, but
boot fails with the red LED stuck on. Starting with the reboot
command, the console reports
login: Jan 2 14:16:39 www shutdown: reboot by bob:
Stopping cron.
Waiting for PIDS: 624.
Stopping sshd.
Waiting for PIDS: 614.
Stopping devd.
Waiting for PIDS: 341.
Writing entropy file:.
Writing early boot entropy file:.
.
Terminated
Jan 2 14:16:50 www syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Syncing disks, vnodes remaining... 3 Waiting (max 60 seconds) for system process `syncer' to stop... 4 3 2 1 0 0 1 0 0 done
Waiting (max 60 seconds) for system process `bufdaemon' to stop... done
All buffers synced.
lock order reversal:
1st 0xc46a5274 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1271
2nd 0xc4828274 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2764
stack backtrace:
lock order reversal:
1st 0xc46a5274 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1271
2nd 0xc4365814 devfs (devfs) @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1410
stack backtrace:
Uptime: 14h18m53s
Rebooting...
c�
U-Boot 2015.04 (Jun 26 2017 - 22:31:06)
DRAM: 944 MiB
WARNING: Caches not enabled
RPI 2 Model B
MMC: bcm2835_sdhci: 0
reading uboot.env
** Unable to read "uboot.env" from mmc0:1 **
Using default environment
In: serial
Out: lcd
Err: lcd
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
Booting from: mmc 0 ubldr
reading ubldr
293073 bytes read in 235 ms (1.2 MiB/s)
## Starting application at 0x02000098 ...
Consoles: U-Boot console
Compatible U-Boot API signature found @0x3ab4b4c8
FreeBSD/armv6 U-Boot loader, Revision 1.2
(Mon Jun 26 22:46:48 UTC 2017 root@releng3.nyi.freebsd.org)
DRAM: 944MB
Number of U-Boot devices: 1
U-Boot env: loaderdev='mmc 0'
Found U-Boot device: disk
Checking unit=0 slice=<auto> partition=<auto>... good.
Booting from disk0s2a:
/boot/kernel/kernel data=0x69ab94+0x1d946c syms=[0x4+0x72bd0+0x4+0xa6299]
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by U-Boot at address 0x100.
Kernel entry at 0x2200100...
Kernel args: (null)
At this point the only recourse seems to be cycling power.
It was necessary to comment out the crossbuild tests in
/usr/src/makefile.inc1 thus
#.if make(buildworld)
#BUILD_ARCH!= uname -p
#.if ${MACHINE_ARCH} != ${BUILD_ARCH}
#.error To cross-build, set TARGET_ARCH.
#.endif
#.endif
to avoid stopping on the demand to set TARGET_ARCH error.
In the past this practice caused no problems, but its necessity
is puzzling.
/etc/make.conf contains
NO_CLEAN=yes
KERNCONF=RPI2
TARGET=arm
TARGET_ARCH=armv7
DESTDIR=/
#FORCE_PKG_REGISTER=yes
DISABLE_VULNERABILITIES=yes
MAKE_JOBS_UNSAFE=yes
/etc/src.conf contains
NO_CLEAN=yes
KERNCONF=RPI2
TARGET=arm
TARGET_ARCH=armv7
DESTDIR=/
Thanks for reading, and any guidance!
bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180102222730.GB10596>