From owner-freebsd-current Mon Jun 28 19: 7:14 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 5FBDB14F48 for ; Mon, 28 Jun 1999 19:06:58 -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 LAA21310; Tue, 29 Jun 1999 11:36:56 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA96942; Tue, 29 Jun 1999 09:43:34 +0930 (CST) Date: Tue, 29 Jun 1999 09:43:33 +0930 From: Greg Lehey To: "Niels Chr. Bank-Pedersen" Cc: FreeBSD current users Subject: Re: panic after loading vinum Message-ID: <19990629094333.A86806@freebie.lemis.com> References: <19990628232624.A11159@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990628232624.A11159@bank-pedersen.dk>; from Niels Chr. Bank-Pedersen on Mon, Jun 28, 1999 at 11:26:24PM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 [Format recovered--see http://www.lemis.com/email/email-format.html] On Monday, 28 June 1999 at 23:26:24 +0200, Niels Chr. Bank-Pedersen wrote: > Since the latest patches for vinum were commited I am getting a panic > immediately after vinum has started. This is on a UP -current (as of > today). > > --- > changing root device to da0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15) > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > da2 at ahc0 bus 0 target 8 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing > Enabled > da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 4.237MB/s transfers (4.237MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > vinum: loaded > Can't open history file /var/tmp/vinum_history: Read-only file system > (30) > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x1 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc017b954 > stack pointer = 0x10:0xc64c7d18 > frame pointer = 0x10:0xc64c7d34 > 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 = 17 (vinum) > interrupt mask = > kernel: type 12 trap, code=0 > Stopped at vn_lock+0x10: testb $0x1,0x1(%esi) > db> trace > vn_lock(0,20002,0,c09acc00,c09acce4) at vn_lock+0x10 > _end(c09acc00,c09acc00,c09d56e0,c5,0) at 0xc09ce85b > _end(c09acc00,0,4000e600,c64c7d94,c09d4980) at 0xc09ce82f > _end(c64c7dac,c09d3461,c64c7e08,4000e600,c5afa4c0) at 0xc09d4890 > _end(c64c7e08,4000e600,c5afa4c0,c64c7ecc,c64c7dd4) at 0xc09d4980 > _end(4000e600,465d,c64c7ecc,3,c5afa4c0) at 0xc09d3461 > spec_ioctl(c64c7e08,c64c7dec,c01e5d65,c64c7e08,c64c7e98) at spec_ioctl+0x40 > spec_vnoperate(c64c7e08,c64c7e98,c017b89d,c64c7e08,c09c2800) at spec_vnoperate+0x15 > ufs_vnoperatespec(c64c7e08,c09c2800,c09ad440,0,0) at ufs_vnoperatespec+0x15 > vn_ioctl(c09ad440,465d,c64c7ecc,c5afa4c0,c5afa4c0) at vn_ioctl+0xdd > ioctl(c5afa4c0,c64c7f80,2,bfbfde00,bfbfde0c) at ioctl+0x1ef > syscall(2f,2f,2f,bfbfde0c,bfbfde00) at syscall+0x182 > Xint0x80_syscall() at Xint0x80_syscall+0x30 > db> ps > [omitted] > db> > > Kernel configuration: > > [omitted] > > Any clues? Yes, they're in vinum(4). They explain what information you should supply if things go wrong. Basically, the information above wouldn't normally be of much use. Having said that, however, in this particular case I *do* recognize the problem. As soon as we get over the lockmgr panics, I should be able to commit a fix for it--hopefully later today. 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