Re: How to force a panic

On Thu, Oct 21, 2004 at 07:43:36PM -0700, Julian Elischer wrote:
> Marc Ramirez wrote:
> >Sorry, folks, I'm being a dunce.  I'm trying to get a coredump, and it's 
> >been a while for me.
> >
> >I'm currently fetching and building 5.3RC1, but in the meantime, I'm 
> >running 
> >FreeBSD laptop.ghostmrami.com 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Thu Oct 21 
> >18:46:32 EDT 2004     
> >mrami_at_laptop.ghostmrami.com:/usr/src/sys/i386/compile/LAPTOPOLDCARD  i386
> >
> >supped on 
> >
> >drwxr-xr-x  2 root  wheel  512 Oct 11 15:10 
> >/usr/local/etc/cvsup/sup/src-all/
> >
> >When I break into ddb, I type in panic, it says it's panicking, and then 
> >just freezes.  diediedie doesn't seem to be there, either.
> >
> >Is there a new/better way to force a dump?
> >
> 
> 
>  "call doadump"
> 

For that to work I had to add:

RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v
retrieving revision 1.163.2.2
diff -r1.163.2.2 kern_shutdown.c
244a245,246
>       if (panicstr == NULL)
>               panicstr = "In doadump()";      /* Major hack XXX pho */

Whithout thet hack I get:

~KDB: enter: Line break on console
[thread 100466]
Stopped at      kdb_enter+0x2b: nop   
db> call doadump
Dumping 255 MB
panic: blockable sleep lock (sleep mutex) taskqueue _at_ kern/subr_taskqueue.c:132
cpuid = 0
Uptime: 3d1h20m32s

-- 
Peter Holm