Re: kern/38762: panic: vwakeup: neg numoutput

[Antti Kantee <pooka%cs.hut.fi@localhost>]

The following reply was made to PR kern/38762; it has been noted by GNATS.

From: Antti Kantee <pooka%cs.hut.fi@localhost>
To: Andreas Gustafsson <gson%gson.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/38762: panic: vwakeup: neg numoutput
Date: Fri, 22 Aug 2008 15:31:54 +0300

 On Fri Aug 22 2008 at 15:23:34 +0300, Andreas Gustafsson wrote:
 >    panic: wvakeup: neg numoutput, vp 0xcc10c750
 >    Stopped in pid 0.4 (system) at  netbsd:breakpoint+0x4:  popl    %ebp
 >    db{0}> show vnode 0xcc10c750
 >    OBJECT 0xcc10c750: locked=1, pgops=0xc07cfca0, npages=0, refs=3
 > 
 >    VNODE flags 24010<MPSAFER,ONWORKLST,LAYER>
 >    mp 0xcbd19000 numoutput -1 size 0x0 writesize 0x0
 >    data 0xcbe4044c writecount 0 holdcnt 4
 >    tag VT_NULL(9) type VBLK(3) mount 0xcbd19000 typedata 0xcbe40460
 >    v_lock 0xcc10c7dc v_unlock 0xcbe70b1c
 
 Ahaa, so the livecd device node is *still* on nullfs.  Well that explains
 a few things.  IIRC having a device node on nullfs is broken in other
 ways also.  I think there's a tech-something thread from around last
 summer going over the issues, maybe even a PR somewhere (I was really
 busy that time).
 
 Either fix layerfs or use tmpfs for /dev.