>Number:         11135
>Category:       kern
>Synopsis:       raidframe panics in rf_ReleaseStripeLock
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 04 15:50:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Luke Mewburn
>Release:        NetBSD-1-5, a few days ago
>Organization:
Wasabi Systems
>Environment:
System: NetBSD argo.akimbo.com.au 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (ARGO) #1: Sun Oct 1 18:46:30 EST 2000 lukem@argo.akimbo.com.au:/z/src/netbsd-1-5/src/sys/arch/i386/compile/ARGO i386

>Description:
	i recently updated argo's kernel from the previous one (which
	was ~ 2000/07/17), and in the course of three days i've had
	two panics in raidframe.

	both messages had tracebacks something like:
		rf_ReleaseStripeLock ... +0x127
		rf_Stale_Cleanup ... +0x388
		rf_Continue_Raid_Access
		rf_Dag_Raid_Access
	(hand transcribed).

	i have /dev/rraid1 setup as a raid0 (i.e, pure stripe).

	i couldn't get a crashdump either time; the box just hung
	after i typed `sync' at ddb. simonb mentioned that apparantly
	you can't dump to a raid device, so i'm going to reconfigure
	my kernel to explicitly dump to sd0b, and see how that goes.

	side note: i get
	    Oct  4 23:59:52 argo savecore: /dev/raid0b: Device not configured
	except that i do have `sw,dp' in the entry for 'sd0b' in my
	fstab, so i thought that would be used. doesn't the `dp' do
	anything i wonder?

>How-To-Repeat:
	see above

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