From owner-freebsd-current Sun Oct 3 12:49:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A237C14EE0 for ; Sun, 3 Oct 1999 12:49:54 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA18510; Sun, 3 Oct 1999 15:49:52 -0400 (EDT) Message-ID: <19991003154952.A18256@netmonger.net> Date: Sun, 3 Oct 1999 15:49:52 -0400 From: Christopher Masto To: Jake Burkholder Cc: current@FreeBSD.ORG Subject: Re: SOLVED (partly): Re: Can't start vinum with new kernels References: <19991003150902.A15336@netmonger.net> <19991003194254.5C2911FD7@io.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991003194254.5C2911FD7@io.yi.org>; from Jake Burkholder on Sun, Oct 03, 1999 at 12:42:54PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 03, 1999 at 12:42:54PM -0700, Jake Burkholder wrote: > > I found out what was causing "Can't get device list: Cannot allocate > > memory".. libdevstat mismatch. > > > > Now I'm getting a panic, but hopefully I'll have a decent backtrace > > out of it soon. > > then promptly rebuilt the world, and everything was fine. > the panic could be from old /sbin/vinum with new kernel and/or vinum.ko, > I'd suggest rebuilding that too. Nope, I've been rebuilding them all along. Just got it again.. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017cf0f stack pointer = 0x10:0xcdacfb9c frame pointer = 0x10:0xcdacfbcc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 16 (vinum) interrupt mask = bio kernel: type 12 trap, code=0 Stopped at getblk+0x21b: cmpl $0x3,0x48(%edx) db> trace getblk(0,8,1000,0,0) at getblk+0x21b bread(0,8,1000,0,cdacfc3c) at bread+0x22 _end(c1150800,c1151000,20000,1200,0) at 0xc108d0f3 _end(c1098284,4,0,c1062800,cdacfd74) at 0xc108e19e _end(c1062800,c109813c,0,0,cdacfd98) at 0xc108c009 _end(c1062800,c109813c,cdacfdf4,c106c580,cc734500) at 0xc108c063 _end(c106c580,c4004640,c1062800,3,cc734500) at 0xc1092658 spec_ioctl(cdacfdf4,cdacfdd8,c0206489,cdacfdf4,cdacfe84) at spec_ioctl+0x33 spec_vnoperate(cdacfdf4,cdacfe84,c0189a3c,cdacfdf4,c1081dc0) at spec_vnoperate+0x15 ufs_vnoperatespec(cdacfdf4,c1081dc0,0,400,0) at ufs_vnoperatespec+0x15 vn_ioctl(c1081dc0,c4004640,c1062800,cc734500,cc734500) at vn_ioctl+0x114 ioctl(cc734500,cdacff80,4,bfbfd4f0,4) at ioctl+0x20b syscall(2f,2f,2f,4,bfbfd4f0) at syscall+0x195 Xint0x80_syscall() at Xint0x80_syscall+0x26 Waiting for the dump now.. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message