[head tinderbox] failure on mips/mips
TB --- 2012-04-08 09:00:29 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-08 09:00:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-04-08 09:00:29 - starting HEAD tinderbox run for mips/mips TB --- 2012-04-08 09:00:29 - cleaning the object tree TB --- 2012-04-08 09:01:10 - cvsupping the source tree TB --- 2012-04-08 09:01:10 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2012-04-08 09:01:58 - building world TB --- 2012-04-08 09:01:58 - CROSS_BUILD_TESTING=YES TB --- 2012-04-08 09:01:58 - MAKEOBJDIRPREFIX=/obj TB --- 2012-04-08 09:01:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-04-08 09:01:58 - SRCCONF=/dev/null TB --- 2012-04-08 09:01:58 - TARGET=mips TB --- 2012-04-08 09:01:58 - TARGET_ARCH=mips TB --- 2012-04-08 09:01:58 - TZ=UTC TB --- 2012-04-08 09:01:58 - __MAKE_CONF=/dev/null TB --- 2012-04-08 09:01:58 - cd /src TB --- 2012-04-08 09:01:58 - /usr/bin/make -B buildworld World build started on Sun Apr 8 09:01:59 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries [...] ranlib libvers.a === kerberos5/lib/libkdc (all) cc -O -pipe -G0 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/default_config.c -o default_config.o cc -O -pipe -G0 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/set_dbinfo.c -o set_dbinfo.o cc -O -pipe -G0 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/digest.c -o digest.o cc -O -pipe -G0 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c -o kerberos5.o /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c: In function '_kdc_as_rep': /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c:1097: error: 'krb5_kdc_configuration' has no member named 'as_use_strongest_session_key' *** Error code 1 Stop in /src/kerberos5/lib/libkdc. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-04-08 09:29:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-04-08 09:29:03 - ERROR: failed to build world TB --- 2012-04-08 09:29:03 - 1146.01 user 245.73 system 1714.02 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on powerpc/powerpc
TB --- 2012-04-08 09:29:03 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-08 09:29:03 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-04-08 09:29:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-04-08 09:29:03 - cleaning the object tree TB --- 2012-04-08 09:29:03 - cvsupping the source tree TB --- 2012-04-08 09:29:03 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-04-08 09:29:44 - building world TB --- 2012-04-08 09:29:44 - CROSS_BUILD_TESTING=YES TB --- 2012-04-08 09:29:44 - MAKEOBJDIRPREFIX=/obj TB --- 2012-04-08 09:29:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-04-08 09:29:44 - SRCCONF=/dev/null TB --- 2012-04-08 09:29:44 - TARGET=powerpc TB --- 2012-04-08 09:29:44 - TARGET_ARCH=powerpc TB --- 2012-04-08 09:29:44 - TZ=UTC TB --- 2012-04-08 09:29:44 - __MAKE_CONF=/dev/null TB --- 2012-04-08 09:29:44 - cd /src TB --- 2012-04-08 09:29:44 - /usr/bin/make -B buildworld World build started on Sun Apr 8 09:29:45 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries [...] ranlib libvers.a === kerberos5/lib/libkdc (all) cc -O2 -pipe -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/default_config.c -o default_config.o cc -O2 -pipe -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/set_dbinfo.c -o set_dbinfo.o cc -O2 -pipe -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/digest.c -o digest.o cc -O2 -pipe -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/roken -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/lib/hdb -I/src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc -DHAVE_CONFIG_H -I/src/kerberos5/lib/libkdc/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c -o kerberos5.o /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c: In function '_kdc_as_rep': /src/kerberos5/lib/libkdc/../../../crypto/heimdal/kdc/kerberos5.c:1097: error: 'krb5_kdc_configuration' has no member named 'as_use_strongest_session_key' *** Error code 1 Stop in /src/kerberos5/lib/libkdc. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-04-08 10:02:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-04-08 10:02:42 - ERROR: failed to build world TB --- 2012-04-08 10:02:42 - 1476.20 user 249.34 system 2019.05 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
xdm failing to start on FBSD 10.0 r2340030 erratically
I loose hair ... Since yesterady's make world (last make world: the day before yesterday), getting FreeBSD 10.0-CURRENT/amd64 to r234000 or so, the X11 system on all of our FreeBSD 10.0-CUR/amd64 boxes start rejecting the start of xdm display manager. xdm is started from /etc/ttys on ttyv7. This worked before flawless. At this very moment, I do have X11 started via xdm - but this is a erratic and non-reproduceable process! This morning, I update world and kernel to r234030. I recompiled many ports via portmaster -f xorg xdm, hoping the new kernel/world could affect the ports, but this isn't. Starting Xorg X11 server works fine. xdm fails. The log in /var/log/xdm.log looks like: Build Date: 07 April 2012 04:51:08PM Current version of pixman: 0.24.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Apr 7 18:38:24 2012 (==) Using config file: /etc/X11/xorg.conf xdm info (pid 2055): sourcing /usr/local/share/X11/xdm/Xsetup_0 xdm error (pid 2050): Unknown session exit code 2560 from process 2055 xdm info (pid 2050): Exiting When running properly, this occurs: Build Date: 07 April 2012 04:51:08PM Current version of pixman: 0.24.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Apr 8 13:10:41 2012 (==) Using config file: /etc/X11/xorg.conf xdm info (pid 18378): sourcing /usr/local/etc/X11/xdm/Xsetup_0 xdm info (pid 18378): sourcing /usr/local/etc/X11/xdm/GiveConsole xdm info (pid 19848): executing session /usr/local/etc/X11/xdm/Xsession Content of XSetup_0 is #!/bin/sh #xconsole -geometry 480x130-0-0 -daemon -notify -verbose -fn fixed -exitOnFail xsetroot -solid black I feel a bit helpless around here since I can not get close to what is happening. The erratic behaviour of starting xdm is frightening. Starting xdm via /etc/ttys doesn't work at all, but sometimes, with a bit luck, xdm starts when started from the console. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: ECC memory driver in FreeBSD 10?
Nikolay Denev wrote: On Apr 6, 2012, at 2:48 PM, O. Hartmann wrote: I'm looking for a way to force FreeBSD 10 to maintain/watch ECC errors reported by UEFI (or BIOS). Since ECC is said to be essential for server systems both in buisness and science and I do not question this, I was wondering if I can not report ECC errors via a watchdog or UEFI (ACPI?) report to syslog facility on FreeBSD. FreeBSD is supposed to be a server operating system, as far as I know, so I believe there must be something which didn't have revealed itself to me, yet. If the hardware supports it, such errors should be logged as MCEs (Machine Check Exceptions). I can say for sure it works pretty well with Dell servers, as I had one with failing RAM module, and it reported the corrected ECC errors in dmesg. Memory ECC errors are logged in to messages and you can decode it by sysutils/mcelog. I did it in the past on one of our Sun Fire X2100 M2 with FreeBSD 8.x. Miroslav Lachman ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: (unionfs) panic: excl-share with r230341 and above
Hi
Please try an attached patch that improves handlings of fs locks.
I think that this patch can resolve this issue. If that works well,
I'm going to refine and commit it to head.
On Fri, 6 Apr 2012 21:36:29 -0400 (EDT)
kwh...@site.uottawa.ca wrote:
Starting with r230341, I get the following panic when trying to run
an executable on a unionfs filesystem:
exclusive lock of (lockmgr) ufs @
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843
while share locked from
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843
panic: excl-share
cpuid = 0
KDB: enter: panic
Narrowing down with a binary search: r230340 (no panic), r230341 (panic).
How to repeat:
# uuname -a
FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r233946M: Fri Apr 6
21:09:32 EDT 2012 kwhite@demo:/usr/src/obj/usr/src/sys/GENERIC
i386
# mkdir /tmp/local
# mount -t unionfs -o noatime /tmp/local /usr/local
# cp /bin/ls /usr/local/bin/ls
# /usr/local/bin/ls
exclusive lock of (lockmgr) ufs @
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843
while share locked from
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843
panic: excl-share
cpuid = 0
KDB: enter: panic
[ thread pid 68 tid 100054 ]
Stopped at kdb_enter+0x3b: movl$0,kdb_why
db show all locks
Process 68 (ls) thread 0xc578 (100054)
exclusive sleep mutex vnode interlock (vnode interlock) r = 0
(0xc57cec28) locked @
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1835
shared lockmgr ufs (ufs) r = 0 (0xc57cec08) locked @
/usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843
db
Workaround?
After reverting the change from LK_EXCLUSIVE to LK_SHARED
in sys/kern/kern_exec.c, executables on union filesystems no
longer cause a panic.
...keith
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
--
Daichi GOTO (daichi)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
diff -urBN /usr/src.orig/sys/fs/unionfs/union_subr.c /usr/src/sys/fs/unionfs/union_subr.c
--- /usr/src.orig/sys/fs/unionfs/union_subr.c 2012-04-08 12:31:30.0 +0900
+++ /usr/src/sys/fs/unionfs/union_subr.c 2012-04-08 12:43:04.0 +0900
@@ -350,19 +350,22 @@
uvp = unp-un_uppervp;
dvp = unp-un_dvp;
unp-un_lowervp = unp-un_uppervp = NULLVP;
-
vp-v_vnlock = (vp-v_lock);
vp-v_data = NULL;
- lockmgr(vp-v_vnlock, LK_EXCLUSIVE | LK_INTERLOCK, VI_MTX(vp));
+ vp-v_object = NULL;
+ VI_UNLOCK(vp);
+
if (lvp != NULLVP)
- VOP_UNLOCK(lvp, 0);
+ VOP_UNLOCK(lvp, LK_RELEASE);
if (uvp != NULLVP)
- VOP_UNLOCK(uvp, 0);
- vp-v_object = NULL;
+ VOP_UNLOCK(uvp, LK_RELEASE);
if (dvp != NULLVP unp-un_hash.le_prev != NULL)
unionfs_rem_cached_vnode(unp, dvp);
+ if (lockmgr(vp-v_vnlock, LK_EXCLUSIVE, VI_MTX(vp)) != 0)
+ panic(the lock for deletion is unacquirable.);
+
if (lvp != NULLVP) {
vfslocked = VFS_LOCK_GIANT(lvp-v_mount);
vrele(lvp);
@@ -550,7 +553,7 @@
cn-cn_flags |= (cnp-cn_flags SAVESTART);
vref(dvp);
- VOP_UNLOCK(dvp, 0);
+ VOP_UNLOCK(dvp, LK_RELEASE);
if ((error = relookup(dvp, vpp, cn))) {
uma_zfree(namei_zone, cn-cn_pnbuf);
@@ -957,7 +957,7 @@
*vpp = vp;
unionfs_vn_create_on_upper_free_out1:
- VOP_UNLOCK(udvp, 0);
+ VOP_UNLOCK(udvp, LK_RELEASE);
unionfs_vn_create_on_upper_free_out2:
if (cn.cn_flags HASBUF) {
diff -urBN /usr/src.orig/sys/fs/unionfs/union_vfsops.c /usr/src/sys/fs/unionfs/union_vfsops.c
--- /usr/src.orig/sys/fs/unionfs/union_vfsops.c 2012-04-08 12:31:30.0 +0900
+++ /usr/src/sys/fs/unionfs/union_vfsops.c 2012-04-08 12:43:04.0 +0900
@@ -165,7 +165,7 @@
uid = va.va_uid;
gid = va.va_gid;
}
- VOP_UNLOCK(mp-mnt_vnodecovered, 0);
+ VOP_UNLOCK(mp-mnt_vnodecovered, LK_RELEASE);
if (error)
return (error);
@@ -250,7 +250,7 @@
* Save reference
*/
if (below) {
- VOP_UNLOCK(upperrootvp, 0);
+ VOP_UNLOCK(upperrootvp, LK_RELEASE);
vn_lock(lowerrootvp, LK_EXCLUSIVE | LK_RETRY);
ump-um_lowervp = upperrootvp;
ump-um_uppervp = lowerrootvp;
@@ -281,7 +281,7 @@
/*
* Unlock the node
*/
- VOP_UNLOCK(ump-um_uppervp, 0);
+ VOP_UNLOCK(ump-um_uppervp, LK_RELEASE);
/*
* Get the unionfs root vnode.
diff -urBN /usr/src.orig/sys/fs/unionfs/union_vnops.c /usr/src/sys/fs/unionfs/union_vnops.c
--- /usr/src.orig/sys/fs/unionfs/union_vnops.c 2012-04-08 12:31:30.0 +0900
+++ /usr/src/sys/fs/unionfs/union_vnops.c 2012-04-08 12:43:04.0 +0900
@@ -75,21 +75,6 @@
KASSERT(((vp)-v_op == unionfs_vnodeops), \
(unionfs: it is not unionfs-vnode))
-/* lockmgr lock - reverse table */
Re: xdm failing to start on FBSD 10.0 r2340030 erratically
On Sun, Apr 08, 2012 at 01:29:36PM +0200, O. Hartmann wrote: I loose hair ... Since yesterady's make world (last make world: the day before yesterday), getting FreeBSD 10.0-CURRENT/amd64 to r234000 or so, the X11 system on all of our FreeBSD 10.0-CUR/amd64 boxes start rejecting the start of xdm display manager. xdm is started from /etc/ttys on ttyv7. This worked before flawless. At this very moment, I do have X11 started via xdm - but this is a erratic and non-reproduceable process! This morning, I update world and kernel to r234030. I recompiled many ports via portmaster -f xorg xdm, hoping the new kernel/world could affect the ports, but this isn't. Starting Xorg X11 server works fine. xdm fails. The log in /var/log/xdm.log looks like: Build Date: 07 April 2012 04:51:08PM ... I feel a bit helpless around here since I can not get close to what is happening. The erratic behaviour of starting xdm is frightening. Starting xdm via /etc/ttys doesn't work at all, but sometimes, with a bit luck, xdm starts when started from the console. I am not having trouble starting xdm via /etc/ttys; my environment is known to differ from yours in the following ways: * My ports (save for x11/nvidia-driver and misc/compat8x) are built under stable/8. (I track stable/8, stable/9, and head on a daily basis, and have a common /usr/local among them. I also update any installed ports that have updates available daily.) * I am running FreeBSD/i386, vs. FreeBSD/amd64. * My last 2 updates were r233994 (yesterday) and r234031 (today). * I have a mildly hacked-up startup script for xdm. I doubt this is an issue -- I've been doing this since 2006/03/05 19:04:03 (according to the RCS log), though I have modified the script a few times since its inception. But the point here is that I'm not directly invoking the xdm executable from /etc/ttys. * I don't know that this is different, but it may well be: my xorg.conf includes a stanza: Section ServerFlags Option AutoAddDevices False EndSection because my experiences with hald dbus were so unpleasant. I don't use them; I don't even try to start them. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpCX4KikQzDB.pgp Description: PGP signature
OpenRD-CL support
Hi,
Based on the work from arm/156814 I've got a working config and device
tree for the OpenRD-CL.
It successfully boots over NFS, both network interfaces as well as the
cesa (crypto accelerator) work.
The patch:
diff --git a/sys/arm/conf/OPENRD-CL b/sys/arm/conf/OPENRD-CL
new file mode 100644
index 000..25707ed
--- /dev/null
+++ b/sys/arm/conf/OPENRD-CL
@@ -0,0 +1,81 @@
+#
+# Custom kernel for OpenRD Client/Ultimate devices.
+#
+# $FreeBSD$
+#
+
+ident OPENRD-CL
+include../mv/kirkwood/std.sheevaplug
+
+optionsSOC_MV_KIRKWOOD
+makeoptionsMODULES_OVERRIDE=
+
+makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols
+makeoptionsWERROR=-Werror
+makeoptions INVARIANTS
+
+optionsSCHED_4BSD #4BSD scheduler
+optionsINET#InterNETworking
+optionsINET6 #IPv6 communications protocols
+optionsFFS #Berkeley Fast Filesystem
+optionsNFSCL #New Network Filesystem Client
+optionsNFSLOCKD#Network Lock Manager
+optionsNFS_ROOT#NFS usable as /, requires NFSCL
+optionsBOOTP
+optionsBOOTP_NFSROOT
+optionsBOOTP_NFSV3
+optionsBOOTP_WIRED_TO=mge0
+
+# Root fs on USB device
+#options ROOTDEVNAME=\ufs:/dev/da0a\
+
+optionsSYSVSHM #SYSV-style shared memory
+optionsSYSVMSG #SYSV-style message queues
+optionsSYSVSEM #SYSV-style semaphores
+options_KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
+optionsMUTEX_NOINLINE
+optionsRWLOCK_NOINLINE
+optionsNO_FFS_SNAPSHOT
+optionsNO_SWAPPING
+
+# Debugging
+optionsALT_BREAK_TO_DEBUGGER
+optionsDDB
+optionsKDB
+
+# Pseudo devices
+device random
+device pty
+device loop
+
+# Serial ports
+device uart
+
+# Networking
+device ether
+device mge # Marvell Gigabit Ethernet controller
+device mii
+device e1000phy
+device bpf
+optionsHZ=1000
+optionsDEVICE_POLLING
+device vlan
+
+device cesa# Marvell security engine
+device crypto
+device cryptodev
+
+# USB
+optionsUSB_DEBUG # enable debug msgs
+device usb
+device ehci
+device umass
+device scbus
+device pass
+device da
+
+# Flattened Device Tree
+optionsFDT
+optionsFDT_DTB_STATIC
+makeoptionsFDT_DTS_FILE=openrd-cl.dts
+
diff --git a/sys/boot/fdt/dts/openrd-cl.dts b/sys/boot/fdt/dts/openrd-cl.dts
new file mode 100644
index 000..6d11779
--- /dev/null
+++ b/sys/boot/fdt/dts/openrd-cl.dts
@@ -0,0 +1,340 @@
+/*
+ * Copyright (c) 2009-2010 The FreeBSD Foundation
+ * All rights reserved.
+ *
+ * This software was developed by Semihalf under sponsorship from
+ * the FreeBSD Foundation.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ *
+ * OpenRD-Client/Ultimate Device Tree Source.
+ *
+ * $FreeBSD$
+ */
+
+/dts-v1/;
+
+/ {
+ model = mrvl,OpenRD-CL;
+ compatible = OpenRD-CL;
+ #address-cells = 1;
+ #size-cells = 1;
+
+ aliases {
+ ethernet0 = enet0;
+ ethernet1 = enet1;
+ mpp = MPP;
+ pci0 = pci0;
+ serial0 = serial0;
+ serial1 = serial1;
+ soc = SOC;
+ sram = SRAM;
+ };
+
+ cpus {
+ #address-cells = 1;
+ #size-cells = 0;
+
+ cpu@0
