>Number:         9544
>Category:       kern
>Synopsis:       add ddb reboot info
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Mar  5 00:20:58 2000
>Last-Modified:
>Originator:     
>Organization:
Redback Networks
	
>Release:        <NetBSD-current source date>1.4.2
>Environment:
	
System: NetBSD fartmangler.redback.com 1.4.2_ALPHA NetBSD 1.4.2_ALPHA (EQUITY) #2: Tue Feb 1 16:45:28 PST 2000 dogcow@fartmangler.redback.com:/amd/elvis/build/moofsrc/nb/syssrc/sys/arch/i386/compile/EQUITY i386


>Description:
	
Occasionally, nasty bugs pop up in RAIDframe such that after dropping
into the debugger, the kernel hangs in 'syncing disks'. It'd be quite
handy to know about `call cpu_reboot(104)` or 'call cpu_reboot(4)` in
the ddb manpage (or even have them as flags to reboot (e.g. `reboot
nosync,dump`).
>How-To-Repeat:
	
Watch RAIDframe panic. Try to figure out how to dump core. Not know the
magic of <sys/reboot.h>.
>Fix:
Patch ddb or ddb(4)
	

>Audit-Trail:
>Unformatted: