Re: panic: vrele: missed vn_close

2001-10-24 Thread David Wolfskill
>Date: Wed, 24 Oct 2001 15:12:52 -0500 >From: Jonathan Lemon <[EMAIL PROTECTED]> >> I suspect that this is the problem with the devfs/console code. >Ugh. Probably. The console code tries to remember what flag was >used from the open, but doesn't use that flag during close. >Here's an (unt

Re: panic: vrele: missed vn_close

2001-10-24 Thread Bruce Evans
On Wed, 24 Oct 2001, Jonathan Lemon wrote: > Hmm. The way the revamped console code works is this: > > cn_devopen() calls vn_open() to open the device. If this is not a > VCHR device, then it is closed. Otherwise, the vnode is stashed in > cnd->cnd_vp. > > When the device is closed though

Re: panic: vrele: missed vn_close

2001-10-24 Thread Jonathan Lemon
On Wed, Oct 24, 2001 at 11:59:52AM -0700, Matthew Dillon wrote: > > : > :Hmm. The way the revamped console code works is this: > : > : cn_devopen() calls vn_open() to open the device. If this is not a > :VCHR device, then it is closed. Otherwise, the vnode is stashed in > :cnd->cnd_vp. > : >

Re: panic: vrele: missed vn_close

2001-10-24 Thread Alfred Perlstein
* Matthew Dillon <[EMAIL PROTECTED]> [011024 13:28] wrote: > > :I got a panic on -current which is updated 3 hours before. > : > :... > :Additional TCP options:. > :Starting background filesystem checks > : > :Wed Oct 24 20:28:15 JST 2001 > :panic: vrele: m

Re: panic: vrele: missed vn_close

2001-10-24 Thread Matthew Dillon
(I meant must be closed with FWRITE, not VWRITE. There is no VWRITE). -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: panic: vrele: missed vn_close

2001-10-24 Thread Matthew Dillon
: :Hmm. The way the revamped console code works is this: : : cn_devopen() calls vn_open() to open the device. If this is not a :VCHR device, then it is closed. Otherwise, the vnode is stashed in :cnd->cnd_vp. : : When the device is closed though cnclose(), it walks through a list :of consol

Re: panic: vrele: missed vn_close

2001-10-24 Thread Jonathan Lemon
Hmm. The way the revamped console code works is this: cn_devopen() calls vn_open() to open the device. If this is not a VCHR device, then it is closed. Otherwise, the vnode is stashed in cnd->cnd_vp. When the device is closed though cnclose(), it walks through a list of console devices,

Re: panic: vrele: missed vn_close

2001-10-24 Thread Matthew Dillon
:... :Sttopped at Debugger+0x44: pushl%ebx :db> trace :Debugger() :panic() :vrele() :vn_close() :cnclose() :spec_close() :spec_vnoperate() :vclean() :vgonel() :vgone() :vop_revoke() :devfs_revoke() :exit1() :... In looking at a diff in the last few days, a huge number of changes have be

Re: panic: vrele: missed vn_close

2001-10-24 Thread Matthew Dillon
:I got a panic on -current which is updated 3 hours before. : :... :Additional TCP options:. :Starting background filesystem checks : :Wed Oct 24 20:28:15 JST 2001 :panic: vrele: missed vn_close :Debugger("panic") :Sttopped at Debugger+0x44: pushl%ebx :db> trace :Debugger() :p

Re: panic: vrele: missed vn_close

2001-10-24 Thread Matthew Dillon
: :I got a panic on -current which is updated 3 hours before. How old was your kernel prior to the update? :Additional TCP options:. :Starting background filesystem checks : :Wed Oct 24 20:28:15 JST 2001 :panic: vrele: missed vn_close :Debugger("panic") :Sttopped at Debugger+0x

panic: vrele: missed vn_close

2001-10-24 Thread Jun Kuriyama
I got a panic on -current which is updated 3 hours before. ... Additional TCP options:. Starting background filesystem checks Wed Oct 24 20:28:15 JST 2001 panic: vrele: missed vn_close Debugger("panic") Sttopped at Debugger+0x44: pushl%ebx db> trace Debugger() panic() vre