Hi Peter, On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote: > On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote: > >Managed to get a dump on our system for a similar prob we are getting: > > That traceback looks like a panic, not a deadlock. What was the panic > message?
Only have remote access to the box im afraid, is there anyway I can obtain the panic message? > > >#2 0xc0513474 in panic (fmt=0xc06c3da5 "%s") at > >/usr/src/sys/kern/kern_shutdown.c:566 > ... > >#7 0xc0510018 in crcopy () at /usr/src/sys/kern/kern_prot.c:1810 > >#8 0xc0598c77 in in_pcbdetach (inp=0xc0743a40) at > >/usr/src/sys/netinet/in_pcb.c:720 > >#9 0xc05b21a6 in tcp_close (tp=0x0) at /usr/src/sys/netinet/tcp_subr.c:783 > > There's something wrong here: If tcp_close() is passed NULL it will panic > at this point when it tries to dereference tp. Starting to stretch my knowledge a bit now ;) If I can provide you with further debug output would you be able to give me some pointers? Thanks for your help -- Jamie Heckford Network Manager Trident Microsystems Ltd. t: +44(0)1737-780790 f: +44(0)1737-771908 w: http://www.tridentmicrosystems.co.uk/ _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
