Subject: kern/12793: softdep_fsync panic syncing mmap()ed file
To: None <gnats-bugs@gnats.netbsd.org>
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
List: netbsd-bugs
Date: 04/30/2001 09:27:52
>Number:         12793
>Category:       kern
>Synopsis:       softdep_fsync panic syncing mmap()ed file
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 30 09:28:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Rupprecht
>Release:        <NetBSD-current source date>
>Organization:
W S Rupprecht Computer Consulting, Fremont CA
>Environment:
	
System: NetBSD capsicum.wsrcc.com 1.5U NetBSD 1.5U (WSRCC_ATHLON) #12: Tue Apr 24 00:38:54 PDT 2001 wolfgang@capsicum.wsrcc.com:/v/src/netbsd/src/sys/arch/i386/compile/WSRCC_ATHLON i386
Architecture: i386
Machine: i386

	Ignore the date, the date above.  The machine panicing is built from
	sources cvs-ed on April 28.

>Description:
	
	The kernel panics with an fsync of a mmap()ed file.  This
	appears related to physical memory size.  (It only occurs on a 
	machine with 64Megs.  A machine with 128megs works fine.)

	cpu_debugger()
	panic()
	softdep_fsync() at softdep_fsync+0x7a
	syscall_plain()

	(kernel build without DIAGNOSTIC -- offsets may vary)

>How-To-Repeat:

	I have a 100% success rate running a certain application on a
	certain machine here.  I can provide kernel dumps etc if need
	be.

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