Hi,

My system, which is running 2.0, was about to be rebooted to load a newly 
compiled kernel from today's sources. The previous kernel and userland were 
from 27-August-2004. However, when wall made the 10 minute announcement, the 
whole machine locked, and when I dropped into the debugger, all I got was this:

Stopped in pid 13712.1 (wall) at        netbsd:cpu_Debugger+0x10: lwz
r
0, r1, 0x14
db> tr
0x00767f00: at zs_abort+0x70
0x00767f10: at zstty_stint+0xd4
0x00767f30: at zsc_intr_hard+0x124
0x00767f50: at zshard+0x54
0x00767f70: at ext_intr_openpic+0x178
0x00767fa0: at trapstart+0x880
0xd6843cd0: at genfs_unlock+0x1c
0xd6843ce0: at spec_write+0x10c
0xd6843d50: at ufsspec_write+0x50
0xd6843d60: at vn_write+0x150
0xd6843df0: at dofilewritev+0x160
0xd6843eb0: at sys_writev+0x8c
0xd6843ed0: at syscall_plain+0xe0
0xd6843f40: user SC trap #121 by 0x41873428: srr1=0xd032
             r1=0xffffe5b0 cr=0x80002042 xer=0x20000000 ctr=0

BTW - does anyone remember where the flags that one can give to the debugger's 
reboot command are explained? When stuff like this happens, I know that the 
system won't reboot on its own if I allow it to try to sync, so I'd like to 
give it the flag to tell it not to - but I don't remember it. Was is 0x4?

Thanks,
John Klos