From owner-freebsd-current Fri Apr 9 17:37:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BC4BB14F6C for ; Fri, 9 Apr 1999 17:37:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA29807; Sat, 10 Apr 1999 10:05:04 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA34907; Sat, 10 Apr 1999 10:05:03 +0930 (CST) Message-ID: <19990410100502.Y2142@lemis.com> Date: Sat, 10 Apr 1999 10:05:03 +0930 From: Greg Lehey To: Michael Reifenberger , greg@lemis.com Cc: FreeBSD-Current Subject: Re: panic: integer divide fault with vinum References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Fri, Apr 09, 1999 at 03:01:51PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 9 April 1999 at 15:01:51 +0200, Michael Reifenberger wrote: > Hi, > next try. > Please forgive if gets too stupid :-) > > # cat x > drive d1 device /dev/da1d > drive d2 device /dev/da2d > volume raid > plex org stripe 256k > sd length 50m drive d1 > sd length 50m drive d2 > (please note again the misspelling of striped) > # vinum create x > 1: drive d1 device /dev/da1d > ** 1 Can't initialize drive d1: Device not configured You need to configure it. Use disklabel -e. > 2: drive d2 device /dev/da2d > ** 2 Can't initialize drive d2: Device not configured > 4: plex org stripe 256k > ** 4 Invalid plex organization: Invalid argument As advertised. But this isn't your primary fault, it's the one above. > 5: sd length 50m drive d1 > ** 5 Unnamed sd is not associated with a plex: Invalid argument Since you don't have a plex, you don't have a subdisk. > 6: sd length 50m drive d2 > ** 6 Unnamed sd is not associated with a plex: Invalid argument > Configuration summary > > Drives: 0 (4 configured) > Volumes: 1 (4 configured) > Plexes: 0 (8 configured) > Subdisks: 0 (16 configured) > > > V raid State: down Plexes: 0 Size: 0 B > (juppie no panic!) Not much of anything, in fact. > (Ok, after repairing 'striped' in x) > # vinum create x > Configuration summary > > Drives: 0 (4 configured) > Volumes: 2 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > > V raid State: down Plexes: 1 Size: 100 MB > > P raid.p0 S State: down Subdisks: 2 Size: 100 MB > > S raid.p0.s0 State: stale PO: 0 B Size: 50 MB > S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB > (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my > situation. Well, I would have thought that the fact you have no drives would give you something to think about. > this time, no `vinum resetconfig`, so:) > > # vinum detach raid.p0 > # vinum detach raid.p0.s0 > # vinum detach raid.p0.s1 > > (Maybe this was too stupid and I get a deserved:) > ..panic.. > > IdlePTD 3686400 > initial pcb at 2f747c > panicstr: integer divide fault > panic messages: > --- > Fatal trap 18: integer divide fault while in kernel mode > instruction pointer = 0x8:0xc0283b27 > stack pointer = 0x10:0xc377cc64 > frame pointer = 0x10:0xc377ccd8 > 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 = 330 (vinum) > interrupt mask = > trap number = 18 > panic: integer divide fault > > syncing disks... 3 3 done > > running gdb post mortem: > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 > #1 0xc016e6f5 in panic (fmt=0xc02c9ea9 "integer divide fault") > at ../../kern/kern_shutdown.c:448 > #2 0xc025a8ce in trap_fatal (frame=0xc377cc28, eva=0) > at ../../i386/i386/trap.c:943 > #3 0xc025a32c in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, > tf_esi = 102400, tf_ebp = -1015558952, tf_isp = -1015559088, tf_ebx = 0, > tf_edx = 0, tf_ecx = 102400, tf_eax = 1, tf_trapno = 18, tf_err = 0, > tf_eip = -1071105241, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, > tf_ss = -1065135960}) at ../../i386/i386/trap.c:586 > #4 0xc0283b27 in __qdivrem (uq=102400, vq=0, arq=0xc377ccf4) > at ../../libkern/qdivrem.c:100 > #5 0xc028496f in __umoddi3 (a=102400, b=0) at ../../libkern/umoddi3.c:51 > #6 0xc0842fe6 in ?? () > #7 0xc0848dc4 in ?? () > #8 0xc0848528 in ?? () > #9 0xc01a0567 in spec_ioctl (ap=0xc377ce0c) > at ../../miscfs/specfs/spec_vnops.c:440 > #10 0xc019fe79 in spec_vnoperate (ap=0xc377ce0c) > at ../../miscfs/specfs/spec_vnops.c:129 > #11 0xc02309a9 in ufs_vnoperatespec (ap=0xc377ce0c) > at ../../ufs/ufs/ufs_vnops.c:2327 > #12 0xc019aae5 in vn_ioctl (fp=0xc0811040, com=3223602776, > data=0xc377ced0 "\001", p=0xc352b780) at vnode_if.h:395 > #13 0xc017a114 in ioctl (p=0xc352b780, uap=0xc377cf84) > at ../../kern/sys_generic.c:564 > #14 0xc025ab17 in syscall (frame={tf_es = 47, tf_ds = 47, > tf_edi = -1077945576, tf_esi = 1, tf_ebp = -1077945696, > tf_isp = -1015558188, tf_ebx = -1077945732, tf_edx = 0, > tf_ecx = 134781696, tf_eax = 54, tf_trapno = 12, tf_err = 2, > tf_eip = 134619728, tf_cs = 31, tf_eflags = 663, tf_esp = -1077945760, > tf_ss = 47}) at ../../i386/i386/trap.c:1101 > #15 0xc024f20c in Xint0x80_syscall () > #16 0x80483d1 in ?? () > #17 0x8048295 in ?? () > #18 0x80480ec in ?? () > > Anything else I can do or inspect? Well, you could RTFM, in this case vinum(4). It tells you in some detail what to do if you have a panic. The stack trace you have there doesn't help. If you give me (root) access to your machine, I'll take a look at it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message