In message <20060120033019.GE828@mjch.net>, Malcolm Herbert writes:
>I've recently upgraded my machine from 2.0.2 to 3.0 and have been having
>the kernel spit the dummy when under load (actually when doing a bulk
>package build or, strangely, when doing a pkgsrc CVS update once).
>
>It used to do the same with 2.0.2, so I don't suspect the new version of
>NetBSD. Given these messages I think it may be a problem with memory.
>Here's a (hand transcribed) copy of the messages that appear on the
>console:
>
>|uvm_fault(0xcc191b6c, 0, 0, 1) -> 0xe
>|kernel: page fault trap, code = 0
>|Sopped in pid 6374, 1 (make) at netbsd:getcwd_common+0x5d:  mov1  0(%edx),  %
>eax
>|db> sync
>|syncing disks...ex0: uplistprt was 0
>|16 23 done
>|unmounting file systems...panic: lockmgr: locking against myself
>|Stopped in pid 6374,1 (make) at netbsd:cpu_Debugger+0x4:  leave
>|db> reboot
>
>Looking at that fragment, should I suspect memory or hard-drive? 

My money would be on memory, and it's easy to test -- get a copy of 
memtest86+ from http://www.memtest.org/ and boot it.  Note: memtest86+ 
appears to find more problems than pkgsrc/sysutils/memtest.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb