Subject: port-i386/11193: crashes in lockmgr for Linux emulation
To: None <gnats-bugs@gnats.netbsd.org>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
List: netbsd-bugs
Date: 10/11/2000 09:53:13
>Number:         11193
>Category:       port-i386
>Synopsis:       1.5_ALPHA2
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 11 09:53:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Michael Richardson
>Release:        NetBSD-1.5_ALPHA2
>Organization:
Sandelman Software Works
>Environment:
	
System: NetBSD marajade.sandelman.ottawa.on.ca 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (XTERM) #14: Mon Oct 9 19:02:09 EDT 2000 mcr@marajade.sandelman.ottawa.on.ca:/mara/mcr/corp/network/kernels/compile-current/XTERM i386
Architecture: i386

>Description:
		Running of intensive Linux apps crashes system

db> trace
cpu_Debugger(c9ae66b4,18002,0,c9cb9c44,c017f9e5) at cpu_Debugger+0x4
panic(c037d060,10002,c03e216c,0,0) at panic+0x64
lockmgr(c9ae66b4,10002,c9ad068c,c9ad05f0,c03e216c) at lockmgr+0xb9
layer_lock(c9cb9ca4) at layer_lock+0x4c
vclean(c9ad05f0,8,c9bd598c) at vclean+0x71
vgonel(c9ad05f0,c9bd598c) at vgonel+0x3b
getnewvnode(2,c07f9400,c0745900,c9cb9d34,20) at getnewvnode+0x1b9
nfs_nget(c07f9400,c9923850,20,c9cb9da0,c9cb9df0) at nfs_nget+0xa1
nfs_create(c9cb9ddc,8fde540,c9cb9f30,602,c07fe980) at nfs_create+0x18fa
vn_open(c9cb9eac,602,1b4,c9cb9f88,c9bd598c) at vn_open+0xe8
sys_open(c9bd598c,c9cb9f30,c9cb9f80) at sys_open+0xca
linux_sys_open(c9bd598c,c9cb9f88,c9cb9f80,0,4) at linux_sys_open+0x6b
syscall() at syscall+0x234
--- syscall (number 5) ---
0x48daa474:
db> 

	Sorry, I don't have the message from the kernel as it crashed, as the serial
	terminal (my notebook) was not hooked up.
	
  	I will try again to get this.

ex0: uplistptr was 0
syncing disks... 25 25 25 25 24 21 20 17 17 17 17 17 17 17 17 17 17 17 16 14 14 14 14 14 14 14 giving up
Printing vnodes for busy buffers
tag 1 type VBLK, usecount 1040, writecount 0, refcount 16,
        tag VT_UFS, ino 14982, on dev 0, 0 flags 0x0, effnlink 1, nlink 1
        mode 060640, owner 0, group 5, size 0 not locked
tag 1 type VBLK, usecount 1040, writecount 0, refcount 16,
        tag VT_UFS, ino 14982, on dev 0, 0 flags 0x0, effnlink 1, nlink 1
        mode 060640, owner 0, group 5, size 0 not locked
tag 2 type VREG, usecount 1, writecount 1, refcount 245,
        tag VT_NFS, fileid 4701346 fsid 0x1f06
tag 2 type VREG, usecount 1, writecount 1, refcount 103,
        tag VT_NFS, fileid 4817072 fsid 0x1f06

dump to dev 0,1 not possible
rebooting...

 	I am investingating why I can't get a coredump.
>How-To-Repeat:
	Varries. Hard to reproduce consistently. Hardware was originally suspected.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: