From olgeni@FreeBSD.org  Fri Dec 10 13:25:36 2004
Return-Path: <olgeni@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1775C16A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 10 Dec 2004 13:25:36 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0435B43D41; Fri, 10 Dec 2004 13:25:36 +0000 (GMT)
	(envelope-from olgeni@FreeBSD.org)
Received: from freefall.freebsd.org (olgeni@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBADPZwA069879;
	Fri, 10 Dec 2004 13:25:35 GMT
	(envelope-from olgeni@freefall.freebsd.org)
Received: (from olgeni@localhost)
	by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBADPZCv069878;
	Fri, 10 Dec 2004 13:25:35 GMT
	(envelope-from olgeni)
Message-Id: <200412101325.iBADPZCv069878@freefall.freebsd.org>
Date: Fri, 10 Dec 2004 13:25:35 GMT
From: Jimmy Olgeni <olgeni@freebsd.org>
Reply-To: Jimmy Olgeni <olgeni@freebsd.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc: olgeni@uli.it
Subject: vinum: kernel panic with dumpconfig while reviving
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         74915
>Category:       kern
>Synopsis:       [vinum] [panic] kernel panic with dumpconfig while reviving
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    le
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 10 13:30:22 GMT 2004
>Closed-Date:    Fri Nov 04 20:06:07 GMT 2005
>Last-Modified:  Fri Nov 04 20:06:07 GMT 2005
>Originator:     Jimmy Olgeni
>Release:        FreeBSD 4.10-RELEASE i386
>Organization:
Colby
>Environment:

System: FreeBSD  4.10-RELEASE FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

>Description:

If the "vinum dumpconfig" command is ran while the vinum daemon is reviving
a mirrored volume, the kernel may panic with the following error message:

Fatal trap 18: integer divide fault while in kernel mode
instruction pointer     = 0x8:0xc03bdc1a
stack pointer           = 0x10:0xccc45c5c
frame pointer           = 0x10:0xccc45cc8
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         = 144 (vinum)
interrupt mask          = none
trap number             = 18
panic: integer divide fault

syncing dists... 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
giving up on 5 buffers

The vinum pid refers to the vinum daemon, not the vinum instance running
dumpconfig.

Sometimes the kernel will hang while syncing disks (tested on 2 hosts
with a simple 2 disk mirror).

>How-To-Repeat:

>Fix:
>Release-Note:
>Audit-Trail:

From: Greg 'groggy' Lehey <grog@FreeBSD.org>
To: Jimmy Olgeni <olgeni@FreeBSD.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org, olgeni@uli.it
Subject: Re: kern/74915: vinum: kernel panic with dumpconfig while reviving
Date: Sat, 11 Dec 2004 10:30:57 +1030

 --xaMk4Io5JJdpkLEb
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 On Friday, 10 December 2004 at 13:25:35 +0000, Jimmy Olgeni wrote:
 >
 >> Synopsis:       vinum: kernel panic with dumpconfig while reviving
 >> Description:
 >
 > If the "vinum dumpconfig" command is ran while the vinum daemon is reviving
 > a mirrored volume, the kernel may panic with the following error message:
 >
 > ...
 
 Please supply the information requested in
 http://www.vinumvm.org/vinum/how-to-debug.html.
 
 Greg
 --
 See complete headers for address and phone numbers.
 
 --xaMk4Io5JJdpkLEb
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.6 (FreeBSD)
 
 iD8DBQFBuji5IubykFB6QiMRAiCgAJ92AQqGiiciyzcanRhI+OdD9I7FfQCfcJb+
 aFTiXkrCUphqjqdOMO20QEI=
 =pMMx
 -----END PGP SIGNATURE-----
 
 --xaMk4Io5JJdpkLEb--
Responsible-Changed-From-To: freebsd-bugs->le 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sun Apr 3 08:16:42 GMT 2005 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=74915 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Fri Oct 28 05:57:11 GMT 2005 
State-Changed-Why:  
This should have been set to 'feedback' to note that the submitter had 
been asked for more information. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=74915 
State-Changed-From-To: feedback->closed 
State-Changed-By: ceri 
State-Changed-When: Fri Nov 4 20:05:16 GMT 2005 
State-Changed-Why:  
If this bug only exists in vinum as it exists in 4.x and early 5.x then  
it basically isn't going to get fixed.  Since we don't even have enough 
information to troubleshoot it even if we still wanted to support old 
vinum, close this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=74915 
>Unformatted:
