From owner-freebsd-hackers Mon Oct 23 23:41:02 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA17588 for hackers-outgoing; Mon, 23 Oct 1995 23:41:02 -0700 Received: from io.org (root@io.org [142.77.70.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA17566 for ; Mon, 23 Oct 1995 23:40:51 -0700 Received: from flinch.io.org (flinch.io.org [198.133.36.153]) by io.org (8.6.12/8.6.12) with SMTP id CAA09456 for ; Tue, 24 Oct 1995 02:40:47 -0400 Date: Tue, 24 Oct 1995 02:40:59 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS-L Subject: panic: free vnode isn't In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG Precedence: bulk On Tue, 17 Oct 1995, Brian Tao wrote: > > I'm starting to see total machine lockup on my IRC/FTP server > (2.1.0-950928-STABLE, 486DX2/66, irc 2.8.21, wu-ftpd 2.4). The only > pattern I can deduce so far is that it happens after about 2 days of > uptime. During those two days, the machine runs beautifully. With 64 > megs, it hardly touches swap even with a fully loaded EFnet IRC server > and 50-100 FTP connections. Then, out of the blue, it just freezes > up (always when I'm away from the office too :-/). I've been running the server with a debugging kernel for the past three days, and finally the darn thing crashed tonight (while I was away from the console too, of course). ddb popped up and left the following message on the console: panic: free vnode isn't Debugger("panic") Stopped at _Debugger+0x2b [/sys/compile/FTPSERV/:261]: movb $0,_inDebugger 110 ddb> Typing "continue" proceeded with the disk sync and reboot. I don't know if this is the cause of the machine hanging the last three times, but it is the only clue I have so far. Any ideas how I can avoid this? The system is an Intel 486DX2/66 on an ASUS SP3G board, 32 megabytes RAM, a 520-meg Maxtor drive on the built-in NCR controller and an NE2000-compatible Ethernet NIC. It is the NFS client for about 26 gigabytes of filesystems, but serving none of its own. I'm running the 2.1.0-950928 snapshot with the following kernel options: machine "i386" cpu "I486_CPU" cpu "I586_CPU" ident FTPSERV maxusers 64 options "CHILD_MAX=128" options "OPEN_MAX=128" options "NMBCLUSTERS=1024" config kernel root on sd0 dumps on sd0 options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options UCONSOLE options INET pseudo-device ether pseudo-device loop options FFS options NFS options "CD9660" options MSDOSFS options PROCFS options DDB options KTRACE controller scbus0 device sd0 device st0 device cd0 options SCSI_REPORT_GEOMETRY pseudo-device pty 32 pseudo-device log pseudo-device vn controller isa0 device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" options FAT_CURSOR device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device ed1 at isa? port 0x300 net irq 12 iomem 0xd8000 vector edintr controller pci0 device ncr0 options PROBE_VERBOSE -- Brian Tao (BT300, taob@io.org) Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"