My -current kernel on my DEC 3000/300 is really unstable.  If I breathe
too heavily it crashes, it seems. :-)

Here are the last three DDB tracebacks I captured for the hell of it:

>>>>>
db> trace
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0xfc
lockmgr() at lockmgr+0x78
genfs_unlock() at genfs_unlock+0x2c
vput() at vput+0xfc
ufs_rename() at ufs_rename+0xd4c
rename_files() at rename_files+0x2e0
sys_rename() at sys_rename+0x28
syscall() at syscall+0x1dc
XentSys() at XentSys+0x50
--- syscall (128, netbsd.sys_rename) ---
--- user mode ---
db>
<<<<<

>>>>>
panic: setrunqueue
Stopped in pid 0 (swapper) at   cpu_Debugger+0x4:       ret
zero,(ra)
db> trace
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0xfc
setrunqueue() at setrunqueue+0x24
uvm_swapin() at uvm_swapin+0x94
uvm_scheduler() at uvm_scheduler+0xf8
main() at main+0xa9c
locorestart() at locorestart+0x68
--- root of call graph ---
db>
<<<<<

>>>>>
Setting tty flags.
panic: kernel debugging assertion "p->p_flag & P_INMEM" failed: file
"../../../../arch/alpha/alpha/machdep.c", line 1821

Stopped at      cpu_Debugger+0x4:       ret     zero,(ra)
db> trace
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0xfc
__assert() at __assert+0x34
fpusave_proc() at fpusave_proc+0x60
cpu_exit() at cpu_exit+0x30
exit1() at exit1+0x4b8
sys_exit() at sys_exit+0x24
syscall_plain() at syscall_plain+0x130
XentSys() at XentSys+0x5c
--- syscall (1) ---
--- user mode ---
db>
<<<<<


Am I correct in assuming -current is somewhat in a state of major flux
right now?  I noticed a new kernel process appeared (aiodoned).  Is this
another revamp of the UVM system?

Cheers,

Paul.

e-mail: paul@gromit.dlib.vt.edu

"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa