kern/74915: vinum: kernel panic with dumpconfig while reviving

[Jimmy Olgeni]

>Number:         74915
>Category:       kern
>Synopsis:       vinum: kernel panic with dumpconfig while reviving
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 10 13:30:22 GMT 2004
>Closed-Date:
>Last-Modified:
>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 at 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:
>Unformatted: