Subject: kern/8696: no obvious `sync' command in ddb
To: None <gnats-bugs@gnats.netbsd.org>
From: Luke Mewburn <lukem@karybdis.cs.rmit.edu.au>
List: netbsd-bugs
Date: 10/27/1999 17:49:09
>Number:         8696
>Category:       kern
>Synopsis:       there's no obvious `sync' command in ddb
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 27 17:48:00 1999
>Last-Modified:
>Originator:     Luke Mewburn
>Organization:
ftp hackers r us
>Release:        1.4J
>Environment:
System: NetBSD karybdis.cs.rmit.edu.au 1.4K NetBSD 1.4K (KARYBDIS) #9: Thu Oct 7 08:45:17 EST 1999 lukem@karybdis.cs.rmit.edu.au:/nfs/echidna/netbsd/current/src/sys/arch/alpha/compile/KARYBDIS alpha

>Description:
	i have ddb in my kernels, and occasional the kernels panic.
	it would be really nice if there was an obvious way to force
	the system to attempt to dump core and then reboot.

	i'm thinking of something like `sync' (a la openprom on the
	sparcs)

>How-To-Repeat:
	have a kernel panic and end up at the `ddb>' prompt.
	scratch your head because you can't remember the symbol to
	call to force a panic (i tried `call cpu_reset', `call reset'
	`call sync'...)

>Fix:
	come up with an MI way to do this, and add the command...
>Audit-Trail:
>Unformatted: