Built today's -CURRENT as usual; booted & ran a few things without incident.
Issued: freebeast(5.0-C) sudo boot0cfg -s 1 ad0 && sudo reboot and this showed up on the serial console: FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: Fboot() called on cpu#1 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped lock order reversal 1st 0xc0335600 sched lock @ /usr/src/sys/kern/kern_idle.c:105 2nd 0xc038ea60 sio @ /usr/src/sys/dev/sio/sio.c:3137 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 00000000 fault virtual address = 0xd6820001 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01a638f stack pointer = 0x10:0xd683dcd0 frame pointer = 0x10:0xd683dce0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 11 (idle: cpu0) kernel: type 12 trap, code=0 timeout stopping cpus Stopped at runq_choose+0x83: movl 0(%edx),%eax db> trace runq_choose(c0358880,d683dd0c,c02b01ce,c01a7857,34948) at runq_choose+0x83 choosethread(c01a7857,34948,c0194f10,d682d500,77) at choosethread+0xd sw1(d682d604,d683dd34,c0194d50,0,d683dd48) at sw1+0x20 idle_proc(0,d683dd48,0,c0194f10,0) at idle_proc+0x5c fork_exit(c0194f10,0,d683dd48) at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 db> I haven't seen any kernel-related commits since I did the CVSup (from 0347 - about 0356 hrs. today, US/Pacific (8 hrs. west of GMT). (Previous CVSup was 24 hrs. earilier, and the kernel built then -- which is what I was running when I built this one -- had not exhibited the symptom.) Anything else I can do to help find & resolve this? Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message