Date: Wed, 19 May 1999 16:07:58 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: ip@mcc.ac.uk Cc: questions@FreeBSD.ORG Subject: Re: panic: ffs_valloc: dup alloc & speaking klingon Message-ID: <Pine.BSF.4.03.9905191600510.9085-100000@resnet.uoregon.edu> In-Reply-To: <199905191044.LAA09994@albatross.mcc.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 May 1999, Ian Pallfreeman wrote: > I'm getting a shitload of: > > mode = 0100600, inum = 642886, fs = /var > panic: ffs_valloc: dup alloc > > since installing 3.2-BETA (now 3.2-STABLE). The crash dump was OK, but whilst > doing savecore, I get: > > additional daemons: syslogd. > checking for core dump...savecore: warning: /kernel version mismatch: > FdreeBSD 3.2-STABLsE #2: Tue May 18c 12:09:01 BST 19h99 Odd. what binary version do you have installed? Have you tried rebuilding savecore? > csavecore: rebootk > May 19 11:18:5:9 curlew savecor e: reboot > savencore: system wenet down at Wed Magy 19 11:15:22 19a99 > savecore: /vtar/crash/bounds:i No such file orv directory This is fun. > saveecore: writing co re to /var/crashb/vmcore.0 > blkno -1047972 > savecore: /dev/rda0s1b: Invalid argument > savecore: WARNING: vmcore may be incomplete > > May 19 11:19:00 curlew savecore: /dev/rda0s1b: Invalid argument > Doing additional network setup: named ntpdate xntpd portmap. The dup alloc is a bit suspicious. Read the section on kernel debugging in the Handbook and try building a kernel with 'options DDB' so you can peg this in person. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9905191600510.9085-100000>