NetBSD Problem Report #10374

Received: (qmail 29604 invoked from network); 15 Jun 2000 19:04:35 -0000
Message-Id: <200006151904.MAA00585@kaben.frye.com>
Date: Thu, 15 Jun 2000 12:04:03 -0700 (PDT)
From: "Aaron J. Grier" <aaron@frye.com>
Reply-To: aaron@frye.com
To: gnats-bugs@gnats.netbsd.org
Subject: lockmgr: locking against myself during heavy disk IO
X-Send-Pr-Version: 3.95

>Number:         10374
>Category:       kern
>Synopsis:       lockmgr: locking against myself during heavy disk IO
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    fvdl
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 15 19:05:00 +0000 2000
>Closed-Date:    Sat Feb 12 21:43:25 +0000 2005
>Last-Modified:  Sat Feb 12 21:43:25 +0000 2005
>Originator:     
>Release:        1.4.2
>Organization:
Frye Electronics, Tigard, OR
>Environment:

System: NetBSD kaben 1.4.2 NetBSD 1.4.2 (kaben) #4: Tue Jun 6 16:48:48 PDT 2000 aaron@kaben:/usr/src/sys/arch/i386/compile/kaben i386


>Description:
	during heavy disk IO (usually the daily cron jobs) the machine
will panic.  running a bunch of concurrent finds also triggers it.  This
appears to be the first lockmgr problem dealing with nfs_lookup according
to query-pr.

(gdb) target kcore netbsd.0.core
panic: lockmgr: locking against myself
#0  0xc012564d in lockstatus (lkp=0xc4ac0b30)
    at ../../../../kern/kern_lock.c:154
154     }
(gdb) where
#0  0xc012564d in lockstatus (lkp=0xc4ac0b30)
    at ../../../../kern/kern_lock.c:154
#1  0xc01f1bd3 in cpu_reboot (howto=260, bootstr=0x0)
    at ../../../../arch/i386/i386/machdep.c:1353
#2  0xc0132109 in panic (fmt=0xc012564d "lockmgr: locking against myself")
    at ../../../../kern/subr_prf.c:212
#3  0xc01259da in lockmgr (lkp=0xc4a60f0c, flags=65554, interlkp=0xc4a11e64)
    at ../../../../kern/kern_lock.c:328
#4  0xc01dc452 in ufs_lock (v=0xc4ac0b70)
    at ../../../../ufs/ufs/ufs_vnops.c:1585
#5  0xc014fc93 in vn_lock (vp=0xc4a11dd4, flags=65554)
    at ../../../../sys/vnode_if.h:724
#6  0xc014993a in vget (vp=0xc4a11dd4, flags=65554)
    at ../../../../kern/vfs_subr.c:872
#7  0xc01cb043 in ffs_sync (mp=0xc0487e00, waitfor=2, cred=0xc044e480, 
    p=0xc0297234) at ../../../../ufs/ffs/ffs_vfsops.c:825
#8  0xc014bd0c in sys_sync (p=0xc0297234, v=0x0, retval=0x0)
    at ../../../../kern/vfs_syscalls.c:524
#9  0xc014af6e in vfs_shutdown () at ../../../../kern/vfs_subr.c:2056
#10 0xc01f1bab in cpu_reboot (howto=256, bootstr=0x0)
    at ../../../../arch/i386/i386/machdep.c:1340
#11 0xc0132109 in panic (fmt=0xc012564d "lockmgr: locking against myself")
    at ../../../../kern/subr_prf.c:212
#12 0xc01259da in lockmgr (lkp=0xc4a60f0c, flags=65538, interlkp=0xc4a11e64)
    at ../../../../kern/kern_lock.c:328
#13 0xc01dc452 in ufs_lock (v=0xc4ac0c90)
    at ../../../../ufs/ufs/ufs_vnops.c:1585
#14 0xc014fc93 in vn_lock (vp=0xc4a11dd4, flags=65538)
    at ../../../../sys/vnode_if.h:724
#15 0xc0149ae2 in vrele (vp=0xc4a11dd4) at ../../../../kern/vfs_subr.c:948
#16 0xc01acd73 in nfs_lookup (v=0xc4ac0e04) at ../../../../nfs/nfs_vnops.c:822
#17 0xc01486c8 in lookup (ndp=0xc4ac0e94) at ../../../../sys/vnode_if.h:71
#18 0xc01483b7 in namei (ndp=0xc4ac0e94) at ../../../../kern/vfs_lookup.c:153
#19 0xc014d690 in sys___stat13 (p=0xc4aa8894, v=0xc4ac0f88, retval=0xc4ac0f80)
    at ../../../../kern/vfs_syscalls.c:1572
#20 0xc01f8f9a in syscall (frame={tf_es = -1078001633, tf_ds = 31, 
      tf_edi = -1077945036, tf_esi = -1077945028, tf_ebp = -1077945276, 
      tf_ebx = 53400, tf_edx = 819072, tf_ecx = 0, tf_eax = 278, 
      tf_trapno = 3, tf_err = 2, tf_eip = 1076397967, tf_cs = 23, 
      tf_eflags = 582, tf_esp = -1077946424, tf_ss = 31, tf_vm86_es = 0, 
      tf_vm86_ds = 0, tf_vm86_fs = 0, tf_vm86_gs = 0})
    at ../../../../arch/i386/i386/trap.c:782

NetBSD 1.4.2 (kaben) #4: Tue Jun  6 16:48:48 PDT 2000
    aaron@kaben:/usr/src/sys/arch/i386/compile/kaben
cpu0: family 6 model 1 step 9
cpu0: Intel Pentium Pro (686-class)
real mem  = 66715648
avail mem = 59785216
using 840 buffers containing 3440640 bytes of memory
biostramp installed @ 1000
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o enabled, memory enabled
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82441FX PCI and Memory Controller (PMC) (rev. 0x02)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01)
pciide0 at pci0 dev 7 function 1: Intel 82371SB IDE Interface (PIIX3)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
pciide0: disabling primary channel (no drives)
pciide0: secondary channel wired to compatibility mode
pciide0: disabling secondary channel (no drives)
uhci0 at pci0 dev 7 function 2: Intel 82371SB USB Host Controller (PIIX3) (rev. 0x01)
uhci0: interrupting at irq 10
uhci0: USB version 1.0
usb0 at uhci0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
vga0 at pci0 dev 11 function 0: S3 ViRGE/DX (rev. 0x01)
wsdisplay0 at vga0: console (80x25, vt100 emulation)
fxp0 at pci0 dev 15 function 0: Intel EtherExpress Pro 10+/100B Ethernet
fxp0: interrupting at irq 10
fxp0: Ethernet address 00:d0:b7:3f:c1:50
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Ensoniq AudioPCI 97 (audio multimedia, revision 0x08) at pci0 dev 17 function 0 not configured
ncr0 at pci0 dev 19 function 0: ncr 53c895 fast40 wide scsi
ncr0: interrupting at irq 11
ncr0: minsync=10, maxsync=137, maxoffs=31, 128 dwords burst, large dma fifo
ncr0: single-ended, open drain IRQ driver, using on-chip SRAM
ncr0: restart (scsi reset).
scsibus0 at ncr0: 16 targets, 8 luns per target
sd0 at scsibus0 targ 0 lun 0: <IBM, DDRS-34560D, DC1B> SCSI2 0/direct fixed
sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled
sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15)
sd0: 4357MB, 8387 cyl, 5 head, 212 sec, 512 bytes/sect x 8925000 sectors
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
lpt0 at isa0 port 0x378-0x37b irq 7
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
apm0 at mainbus0: Power Management spec V1.1 (BIOS mgmt disabled) (BIOS managing devices)
apm0: A/C state: on
apm0: battery charge state: no battery
biomask c40 netmask c40 ttymask 1cc2
wscons: wskbd0 glued to wsdisplay0 (console)
boot device: sd0
root on sd0a dumps on sd0b
mountroot: trying msdos...
mountroot: trying cd9660...
mountroot: trying nfs...
mountroot: trying lfs...
mountroot: trying ext2fs...
mountroot: trying ffs...
root file system type: ffs

coredump and debugging kernel available on request.

>How-To-Repeat:
	running a whole bunch of find jobs will do it.  (49 were run to
produce this crash, however, often as few as one or two will trigger it.)
>Fix:
	you guys are the kernel gurus.  :)
>Release-Note:
>Audit-Trail:

From: "Aaron J. Grier" <aaron@frye.com>
To: gnats-bugs@netbsd.org
Cc:  
Subject: Re: kern/10374
Date: Tue, 11 Jul 2000 10:05:06 -0700

 again, this time before the daily cron job.

 #0  0xc012564d in lockstatus (lkp=0xc4ab1c50)
     at ../../../../kern/kern_lock.c:154
 #1  0xc01f1bd3 in cpu_reboot (howto=256, bootstr=0x0)
     at ../../../../arch/i386/i386/machdep.c:1353
 #2  0xc0132109 in panic (fmt=0xc012564d "lockmgr: locking against myself")
     at ../../../../kern/subr_prf.c:212
 #3  0xc01259da in lockmgr (lkp=0xc4a0760c, flags=65538, interlkp=0xc48eadb0)
     at ../../../../kern/kern_lock.c:328
 #4  0xc01dc452 in ufs_lock (v=0xc4ab1c90)
     at ../../../../ufs/ufs/ufs_vnops.c:1585
 #5  0xc014fc93 in vn_lock (vp=0xc48ead20, flags=65538)
     at ../../../../sys/vnode_if.h:724
 #6  0xc0149ae2 in vrele (vp=0xc48ead20) at ../../../../kern/vfs_subr.c:948
 #7  0xc01acd73 in nfs_lookup (v=0xc4ab1e04) at ../../../../nfs/nfs_vnops.c:822
 #8  0xc01486c8 in lookup (ndp=0xc4ab1e94) at ../../../../sys/vnode_if.h:71
 #9  0xc01483b7 in namei (ndp=0xc4ab1e94) at ../../../../kern/vfs_lookup.c:153
 #10 0xc014d690 in sys___stat13 (p=0xc4aa83b4, v=0xc4ab1f88, retval=0xc4ab1f80)
     at ../../../../kern/vfs_syscalls.c:1572
 #11 0xc01f8f9a in syscall (frame={tf_es = -1078001633, tf_ds = 1075904543, 
       tf_edi = -1077945036, tf_esi = -1077945028, tf_ebp = -1077945276, 
       tf_ebx = 53400, tf_edx = 756160, tf_ecx = 0, tf_eax = 278, 
       tf_trapno = 3, tf_err = 2, tf_eip = 1076410255, tf_cs = 23, 
       tf_eflags = 646, tf_esp = -1077946424, tf_ss = 31, tf_vm86_es = 0, 
       tf_vm86_ds = 0, tf_vm86_fs = 0, tf_vm86_gs = 0})
     at ../../../../arch/i386/i386/trap.c:782

 coredump and debugging kernel still available by request...

 -- 
   Aaron J. Grier   |   Frye Electronics, Tigard, OR   |   aaron@frye.com

From: he@netbsd.org (Havard Eidnes)
To: aaron@frye.com
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10374: lockmgr: locking against myself during heavy disk IO
Date: Wed, 02 Aug 2000 10:46:49 -0400

 Hi,

 I won't even pretend to be able to find and fix this bug, but I
 thought that I might at least take a stab at getting some more
 information out of you regarding these crashes and the
 environment they are occurring in.

 It would seem that in both the submitted backtraces, NFS is
 always a part of the picture.  Can you say a little about your
 NFS configuratin?  What's the server?  Do you use AMD, and to
 what extent?

 I run many machines with 1.4.2, and I have never seen the problem
 you are observing.  However, none of those machines use NFS...

 Regards,

 - H=E5vard

From: "Aaron J. Grier" <aaron@frye.com>
To: Havard Eidnes <he@netbsd.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10374: lockmgr: locking against myself during heavy disk IO
Date: Wed, 2 Aug 2000 10:19:12 -0700

 On Wed, Aug 02, 2000 at 10:46:49AM -0400, Havard Eidnes wrote:

 > It would seem that in both the submitted backtraces, NFS is always a
 > part of the picture.  Can you say a little about your NFS
 > configuratin?  What's the server?  Do you use AMD, and to what extent?

 both AMD and NFS are used heavily.  the only NFS servers are NetBSD
 machines.

 machine			exports
 -------			-------
 kaben (NetBSD 1.4.2)	/usr/projects
 aaron (NetBSD 1.4)	/usr/home

 both machines are i386.  (kaben is pentium pro, aaron is AMD 5x86.)

 kaben is the machine that is crashing.

 cross-mounting between the two machines is frequent, and a third machine
 (aaron2, running linux) often mounts both of the above (also via AMD),
 but exports nothing.

 from the amd master map:

 /defaults       opts:=rsize=8192,wsize=8192,intr

 # top level mount points... try and avoid symlink tag
 aaron		type:=auto;fs:=${map};pref:=${key}/
 aaron/home	host!=aaron;type:=nfs;rhost:=aaron;rfs:=/usr/home \
 		host==aaron;type:=link;fs:=/usr/home

 kaben		type:=auto;fs:=${map};pref:=${key}/
 kaben/projects	host!=kaben;type:=nfs;rhost:=kaben;rfs:=/usr/projects \
 		host==kaben;type:=link;fs:=/usr/projects

 everything else in the amd universe is symlinked down to the above two
 places.

 -- 
   Aaron J. Grier   |   Frye Electronics, Tigard, OR   |   aaron@frye.com
Responsible-Changed-From-To: kern-bug-people->fvdl 
Responsible-Changed-By: fvdl 
Responsible-Changed-When: Fri Aug 4 14:03:52 PDT 2000 
Responsible-Changed-Why:  
I'll investigate this one. 

From: "Aaron J. Grier" <aaron@frye.com>
To: gnats-bugs@gnats.netbsd.org
Cc: Frank van der Linden <fvdl@vaasje.org>, sommerfeld@orchard.arlington.ma.us
Subject: Re: kern/10374
Date: Tue, 8 Aug 2000 11:54:36 -0700

 Here is the patch I applied to nfs_vnops.c:

 --- nfs_vnops.c.orig	Thu Jan  6 05:48:32 2000
 +++ nfs_vnops.c	Mon Aug  7 13:36:05 2000
 @@ -780,6 +780,12 @@
  		struct vattr vattr;
  		int vpid, err2;

 +		if (error != ENOENT) {
 +			/* needs to happen before anything which can block.. */
 +			newvp = *vpp;
 +			vpid = newvp->v_id;
 +		}
 +		  	
  		err2 = VOP_ACCESS(dvp, VEXEC, cnp->cn_cred, cnp->cn_proc);
  		if (err2) {
  			*vpp = NULLVP;
 @@ -796,8 +802,6 @@
  			goto dorpc;
  		}

 -		newvp = *vpp;
 -		vpid = newvp->v_id;
  		/*
  		 * See the comment starting `Step through' in ufs/ufs_lookup.c
  		 * for an explanation of the locking protocol
 @@ -819,6 +823,8 @@
  			   }
  			   cache_purge(newvp);
  			}
 +			if (dvp != newvp)
 +			  	VOP_UNLOCK(newvp, 0);
  			vrele(newvp);
  		}
  		*vpp = NULLVP;

 the system was none too happy... first, a login prompt hung on ttyout
 while exiting, and an attempt to attach to it with gdb to see what was
 going on caused a panic.  (no coredump -- not enough disk space.)  X
 died unhappily on the next bootup, and at that point my coworker and I
 started getting a little nervous and decided to call it quits for the
 day.

 I'll put a recently cvs'd version of 1.4.3 (it's currently running
 1.4.2) on the machine this evening to make sure that the problems I was
 seeing aren't related to 1.4.2 -> 1.4.3 migration.

 -- 
   Aaron J. Grier   |   Frye Electronics, Tigard, OR   |   aaron@frye.com

From: Frank van der Linden <fvdl@vaasje.org>
To: "Aaron J. Grier" <aaron@frye.com>
Cc: gnats-bugs@gnats.netbsd.org, sommerfeld@orchard.arlington.ma.us
Subject: Re: kern/10374
Date: Tue, 8 Aug 2000 21:54:54 +0200

 On Tue, Aug 08, 2000 at 11:54:36AM -0700, Aaron J. Grier wrote:
 > the system was none too happy... first, a login prompt hung on ttyout
 > while exiting, and an attempt to attach to it with gdb to see what was
 > going on caused a panic.  (no coredump -- not enough disk space.)  X
 > died unhappily on the next bootup, and at that point my coworker and I
 > started getting a little nervous and decided to call it quits for the
 > day.

 Hmm.. those problems are unlikely to have been related to the patch.
 Someone else is running the patch without these problems (and without
 crashes so far). Try the updated tree.. something else must be
 wrong there.

 - Frank

From: "Aaron J. Grier" <aaron@frye.com>
To: Frank van der Linden <fvdl@vaasje.org>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10374
Date: Tue, 12 Sep 2000 10:28:34 -0700

 On Tue, Aug 08, 2000 at 09:54:54PM +0200, Frank van der Linden wrote:

 > Try the updated tree.. something else must be wrong there.

 I updated the kernel to 1.4.3_ALPHA, and ditched windowmaker.  The
 machine has been stable for two weeks now.

 I figure this PR can finally be put to rest, unless somebody else wants
 to continue the investigation.

 -- 
   Aaron J. Grier   |    Frye Electronics, Tigard, OR   |   aaron@frye.com
    "Cthulhu for President. Why settle for a lesser evil?" -- Matt Minnis

From: "Aaron J. Grier" <aaron@frye.com>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: Re: kern/10374
Date: Fri, 20 Oct 2000 12:09:18 -0700

 after six weeks of trouble-free use with a stock 1-4 branch:

 NetBSD kaben 1.4.3_ALPHA NetBSD 1.4.3_ALPHA (kaben) #1: Tue Aug  8 13:32:51 PDT 2000 aaron@kaben:/usr/projects/NetBSD/src/sys/arch/i386/compile/kaben i386

 I'm hitting the same thing again.
 <sigh>

 #0  0xc0125805 in lockstatus (lkp=0xc4b37c50)
     at ../../../../kern/kern_lock.c:154
 #1  0xc01f206b in cpu_reboot (howto=256, bootstr=0x0)
     at ../../../../arch/i386/i386/machdep.c:1353
 #2  0xc0132419 in panic (fmt=0xc0125805 "lockmgr: locking against myself")
     at ../../../../kern/subr_prf.c:212
 #3  0xc0125b92 in lockmgr (lkp=0xc4a22cf4, flags=65538, interlkp=0xc48edd10)
     at ../../../../kern/kern_lock.c:328
 #4  0xc01dc952 in ufs_lock (v=0xc4b37c90)
     at ../../../../ufs/ufs/ufs_vnops.c:1585
 #5  0xc014fef3 in vn_lock (vp=0xc48edc80, flags=65538)
     at ../../../../sys/vnode_if.h:724
 #6  0xc0149d4a in vrele (vp=0xc48edc80) at ../../../../kern/vfs_subr.c:948
 #7  0xc01ad1f3 in nfs_lookup (v=0xc4b37e04) at ../../../../nfs/nfs_vnops.c:822
 #8  0xc0148930 in lookup (ndp=0xc4b37e94) at ../../../../sys/vnode_if.h:71
 #9  0xc014861f in namei (ndp=0xc4b37e94) at ../../../../kern/vfs_lookup.c:153
 #10 0xc014d8f4 in sys___stat13 (p=0xc4b0beb4, v=0xc4b37f88, retval=0xc4b37f80)
     at ../../../../kern/vfs_syscalls.c:1574
 #11 0xc01f943a in syscall (frame={tf_es = 524319, tf_ds = 31, tf_edi = 294912, 
       tf_esi = 550976, tf_ebp = -1077948512, tf_ebx = 0, tf_edx = 615040, 
       tf_ecx = 61788, tf_eax = 278, tf_trapno = 3, tf_err = 2, 
       tf_eip = 1075918735, tf_cs = 23, tf_eflags = 514, tf_esp = -1077948624, 
       tf_ss = 31, tf_vm86_es = 0, tf_vm86_ds = 0, tf_vm86_fs = 0, 
       tf_vm86_gs = 0}) at ../../../../arch/i386/i386/trap.c:782

   PID  PADDR WCHAN  TT  STAT      TIME COMMAND
     0 c029a6b0 -      ??  RLs    0:00.23 (swapper)
     1 c48f1000 wait   ??  IWs    0:00.04 (init)
     2 c48f1138 daemon ??  DL     0:01.01 (pagedaemon)
     3 c48f1270 reaper ??  DL     0:00.26 (reaper)
   110 c48f1618 select ??  Ss     0:00.65 (syslogd)
   117 c48f1750 select ??  IWs    0:00.00 (portmap)
   122 c48f1888 -      ??  Rs     0:06.68 (ypbind)
   129 c48f19c0 select ??  IWs    0:00.00 (mountd)
   132 c48f1c30 netcon ??  IWs    0:00.00 (nfsd)
   135 c48f1af8 -      ??  RL     0:39.29 (nfsd)
   137 c48f1d68 -      ??  RL     0:03.08 (nfsd)
   138 c4a48004 -      ??  RL     0:01.81 (nfsd)
   139 c4a4813c nfsd   ??  IL     0:01.02 (nfsd)
   149 c4a483ac nfsidl ??  IL     0:07.66 (nfsiod)
   150 c4a48274 nfsidl ??  IL     0:02.55 (nfsiod)
   151 c4a484e4 nfsidl ??  IL     0:01.15 (nfsiod)
   152 c4a4861c nfsidl ??  IL     0:00.88 (nfsiod)
   156 c48f1ea0 select ??  IWs    0:00.00 (rpc.statd)
   164 c4a4888c select ??  IWs    0:00.00 (rpc.lockd)
   169 c4a48754 select ??  Is     0:03.77 (amd)
   203 c4a489c4 -      ??  Rs     0:03.07 (update)
   205 c4a48afc nanosl ??  Is     0:00.89 (cron)
   207 c4a48c34 -      ??  R<s    0:08.62 (xntpd)
   209 c4a48d6c select ??  IWs    0:00.00 (lpd)
   212 c4a48ea4 pause  ??  Is     0:00.18 (sendmail)
   216 c4a7d008 select ??  IWs    0:00.00 (inetd)
   231 c48f14e0 pause  ??  IWs    0:00.00 (xdm)
   239 c4a7d758 select ??  Ss    29:14.18 (XF86_S3V)
   240 c4a7d4e8 select ??  Is     0:01.07 (sshd1)
   245 c4a7d3b0 wait   ??  IWs    0:00.00 (xdm)
   246 c4a7d140 select ??  IWs    0:00.00 (postgres)
   263 c4a7d9c8 wait   ??  IWs    0:00.00 (sh)
   269 c4a7db00 select ??  IW     0:00.00 (xconsole)
   271 c4a7dd70 -      ??  R      0:26.04 (tail)
   272 c4a7dc38 -      ??  Rs     0:01.81 (ssh-agent1)
   273 c4a7dea8 select ??  I      0:18.70 (ctwm)
   292 c4aab4ec select ??  IW     0:00.00 (xterm)
   321 c4aab894 select ??  IW     0:00.00 (xterm)
   341 c4aabd74 select ??  IW     0:00.00 (xterm)
   354 c4ade010 select ??  IW     0:00.00 (xterm)
   364 c4ade3b8 select ??  IW     0:00.00 (xterm)
   387 c4ade628 select ??  I      0:07.17 (xterm)
   397 c4ade898 select ??  I      0:03.87 (xterm)
   407 c4adeb08 select ??  I      0:01.48 (xterm)
   417 c4aded78 select ??  I      0:01.79 (xterm)
   466 c4b0b764 select ??  IW     0:00.00 (xterm)
   540 c4b0b014 select ??  IW     0:00.00 (xterm)
   716 c4b39018 select ??  IW     0:04.33 (xterm)
   731 c4b39630 select ??  IW     0:01.38 (xterm)
  3716 c4b39eb8 netio  ??  I      0:00.00 (cron)
  3717 c4b398a0 wait   ??  Is     0:00.02 (sh)
  3718 c4b39d80 wait   ??  I      0:00.02 (sh)
  3720 c4b39b10 netio  ??  I      0:00.01 (tee)
  3722 c4b39768 netio  ??  I      0:00.04 (sendmail)
  3728 c4b393c0 -      ??  R      0:11.64 (find)
   541 c4b0b284 wait   p1  IWs    0:00.00 (bash)
   552 c4b0b89c ttyin  p1  IW+    0:00.00 (w3m)
   293 c4aab27c ttyin  p2  IWs+   0:00.00 (bash)
   330 c4aab9cc -      p2  R      1:37.73 (xclock)
   337 c4aabc3c -      p2  R      0:01.89 (titrax)
   487 c4b0b9d4 pause  p2  IW     0:00.00 (xdvi.bin)
   322 c4aab3b4 ttyin  p3  IWs+   0:00.00 (bash)
   342 c4aabb04 wait   p4  IWs    0:00.00 (bash)
   507 c4aab144 ttyin  p4  IW+    0:00.00 (cscope)
   355 c4aabeac wait   p5  IWs    0:00.00 (bash)
   959 c4adec40 select p5  IW+    0:00.00 (vim)
   960 c4adeeb0 netio  p5  IW+    0:00.00 (cscope)
   365 c4ade148 wait   p6  IWs    0:00.00 (bash)
   579 c4aab00c select p6  IW+    0:00.00 (vim)
   580 c4b0bb0c netio  p6  IW+    0:00.00 (cscope)
   388 c4ade280 wait   p7  IWs    0:00.00 (bash)
   585 c4b0b62c select p7  I+     0:07.79 (ssh1)
   398 c4ade4f0 ttyin  p8  IWs+   0:00.96 (bash)
   408 c4ade760 wait   p9  IWs    0:00.48 (bash)
  3510 c4b0beb4 -      p9  R+     0:20.53 (gv)
  3520 c4b39288 select p9  I+     0:01.18 (gs)
   418 c4ade9d0 ttyin  pa  Is+    0:00.76 (bash)
   717 c4b39150 ttyin  pb  IWs+   0:00.00 (bash)
  3003 c4b0b14c select pb  I      4:20.30 (netscape)
  3005 c4b0bd7c -      pb  Z      0:00.00 (netscape)
   467 c4b0b4f4 ttyin  pc  IWs+   0:00.00 (bash)
   732 c4b394f8 wait   pd  IWs    0:00.00 (bash)
  2954 c4b0bc44 select pd  IW+    0:00.00 (vim)
  2955 c4b0b3bc netio  pd  IW+    0:00.00 (cscope)
   249 c48f13a8 ttyin  E0  IWs+   0:00.00 (getty)
   250 c4a7d278 ttyin  E1  IWs+   0:00.00 (getty)
   251 c4a7d620 ttyin  E2  IWs+   0:00.00 (getty)
   252 c4a7d890 wait   E3  IWs    0:00.00 (bash)
   311 c4aab624 wait   E3  IW+    0:00.00 (bash)
   319 c4aab75c select E3  I+     0:01.00 (ssh1)

 coredumps and gdb kernel available by request.

 -- 
   Aaron J. Grier   |    Frye Electronics, Tigard, OR   |   aaron@frye.com
State-Changed-From-To: open->feedback 
State-Changed-By: tls 
State-Changed-When: Wed Mar 31 22:42:55 UTC 2004 
State-Changed-Why:  
can anyone reproduce this with current code? 

From: "Aaron J. Grier" <aaron@frye.com>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: Re: kern/10374
Date: Thu, 15 Apr 2004 14:20:22 -0700

 On Wed, Mar 31, 2004 at 10:43:55PM -0000, tls@netbsd.org wrote:
 > can anyone reproduce this with current code?

 last year I had this machine running 1.6 without incident.  I suppose
 it's safe to close the PR.  (we can always re-open if the problem
 occurrs again.)

 -- 
   Aaron J. Grier  |   Frye Electronics, Tigard, OR   |  aaron@frye.com
State-Changed-From-To: feedback->closed
State-Changed-By: chs@netbsd.org
State-Changed-When: Sat, 12 Feb 2005 21:43:25 +0000
State-Changed-Why:
closed at request of submitter.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.