>Number:         25581
>Category:       port-i386
>Synopsis:       Kernel panic unmounting partitions
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 15 14:36:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 2.0E
>Organization:
	
>Environment:
	
	
System: NetBSD tenebres.loc 1.6ZL NetBSD 1.6ZL (TENEBRES) #0: Sat Mar 27 02:04:18 GMT 2004 rob@tenebres.loc:/usr/src/sys/arch/i386/compile/TENEBRES i386
Architecture: i386
Machine: i386
>Description:
	I haven't been able to upgrade because the kernel panics.
	To test it, I created an altroot and booted from that after changing fstab.
	All seemed well until I tried "umount -a" at which point it panicked.
	The system was single-user because I had been fsck-ing due to a previous
	crash.

	I have two kernel core dumps + the kernel itself but
	gdb doesn't seem to recognise them as core dumps.

	From memory, the message was "vp != NULL" in softdeps

	Sources are -current from 11pm UK time (ie 7pm EST) on 11th May.

	All filesystems were upgraded a while ago for the new superblock
	with no problems.  For example

	    file system: /dev/rwd0a
	    endian  little-endian
	    magic   11954 (UFS1)    time    Sat May 15 14:37:03 2004
	    superblock location     8192    id      [ 0 0 ]
	    cylgrp  dynamic inodes  4.4BSD  sblock  FFSv2   fslevel 4
	    nbfree  1866    ndir    1060    nifree  17473   nffree  477

	This report seems a little sparse, so feel free to contact me for more details.
	It's easy to reproduce the problem.

>How-To-Repeat:
	Boot as normal and then type "umount -a"

	Contact me to get more data.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: