>Number:         14866
>Category:       kern
>Synopsis:       lockmgr panic with siop * 2, RAID, softdep
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 07 17:40:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Chris Jones
>Release:        NetBSD 1.5.3_ALPHA
>Organization:
	
>Environment:
	
1.5.3_ALPHA, i386, 2 independent RAID sets, softdep on some file systems.

cpu0: Intel Pentium II (Klamath) (686-class)
siop1 at pci0 dev 11 function 0: Symbios Logic 53c875 (ultra-wide scsi)
siop1: using on-board RAM
siop1: interrupting at irq 9
scsibus1 at siop1: 16 targets, 8 luns per target
siop0 at pci0 dev 13 function 0: Symbios Logic 53c875 (ultra-wide scsi)
siop0: using on-board RAM
siop0: interrupting at irq 10
scsibus0 at siop0: 16 targets, 8 luns per target
sd2 at scsibus1 target 2 lun 0: <IBM, DMVS36D, 0210> SCSI3 0/direct fixed
sd3 at scsibus1 target 3 lun 0: <IBM, DMVS36D, 0210> SCSI3 0/direct fixed
st0 at scsibus1 target 5 lun 0: <HP, C1557A, U812> SCSI2 1/sequential removable
ch0 at scsibus1 target 5 lun 1: <HP, C1557A, U812> SCSI2 8/changer removable
sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST34572W, 0784> SCSI2 0/direct fixed
sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST32272W, 0784> SCSI2 0/direct fixed
sd4 at scsibus0 target 4 lun 0: <IBM, DMVS36D, 0210> SCSI3 0/direct fixed

>Description:
When this machine boots a recent 1.5.x kernel, it usually panics.

panic: lockmgr: no context

Stack trace copied by hand:

cpu_Debugger
panic
lockmgr
uvm_map
uvm_km_valloc
_bus_dmamem_map
siop_morecbd
siop_scsicmd
scsipi_execute_xs
scsi_scsipi_cmd
scsipi_command
sdstart
scsipi_free_xs
scsipi_done
siop_scsicmd_end
siop_intr
Xintr10
--- interrupt ---
idle
bpendtsleep
ffs_full_fsync
ffs_fsync
sys_fsync
syscall

Another instance of this panic was the same up to the interrupt.  The
rest of the trace was:

--- interrupt ---
idle
bpendtsleep
rf_VerifyParityRAID1
rf_VerifyParity
rf_RewriteParity
rf_RewriteParityThread

In both instances, ddb's ps didn't show any process with the '>' next
to it.  Is there another way I can determine the active process?

>How-To-Repeat:
I can reproduce this on 1.5.3_ALPHA, and several earlier kernels.
It does not occur with the following kernel, though:

NetBSD gamera.mt.sri.com 1.5 NetBSD 1.5 (GAMERA) #6: Mon Jul  9 09:28:05 MDT 2001     root@gamera.mt.sri.com:/usr/src/sys/arch/i386/compile/GAMERA i386
NetBSD 1.5 (GAMERA) #6: Mon Jul  9 09:28:05 MDT 2001
    root@gamera.mt.sri.com:/usr/src/sys/arch/i386/compile/GAMERA

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