I saw that jhb committed some changes as of r1.307 of
src/sys/i386/conf/GENERIC, so I replicated those changes (that I didn't
already have) to my kernel config.
Got -CURRENT built & running; the message below (bracketed by "normal"
messages, to supply a little context) appear to be documenting weirdnesses,
but I don't see other evidence of problems:
Apr 16 08:57:44 localhost /boot/kernel/kernel: pccard: card inserted, slot 1
Apr 16 08:57:44 localhost /boot/kernel/kernel: acquring duplicate lock of same type:
"allproc"
Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st @ /usr/src/sys/kern/kern_proc.c:584
Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd @ /usr/src/sys/kern/kern_proc.c:143
Apr 16 08:57:44 localhost /boot/kernel/kernel: lock order reversal
Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st vnode interlock last acquired @
/usr/src/sys/kern/vfs_vnops.c:625
Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd 0xc0459b80 mntvnode @
/usr/src/sys/ufs/ffs/ffs_vfsops.c:954
Apr 16 08:57:44 localhost /boot/kernel/kernel: 3rd 0xce7d54ac vnode interlock @
/usr/src/sys/ufs/ffs/ffs_vfsops.c:963
Apr 16 08:57:44 localhost savecore: magic number mismatch (8b98aa0d != 8fca0101)
Apr 16 08:57:44 localhost savecore: no core dump
Last CVSup was:
CVSup started from cvsup14.freebsd.org at Mon Apr 16 03:47:01 PDT 2001
CVSup ended from cvsup14.freebsd.org at Mon Apr 16 03:52:03 PDT 2001
And uname says
FreeBSD m138.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #33: Mon Apr 16 08:41:02 PDT
2001 root@localhost:/common/C/obj/usr/src/sys/LAPTOP_30W i386
Should this be interesting enough to pursue (probably off-list), I'll be
happy to work with one or more folks on it; the machine is my
(uni-processor) laptop.
Cheers,
david
--
David H. Wolfskill [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
