Re: nb5 panic: kernel diagnostic assertion "cv_is_valid(cv)" failed: file "/usr/nbcvs/src-5/sys/kern/kern_condvar.c", line 329 (fwd)

[Brett Lymn <blymn%baesystems.com.au@localhost>]

On Thu, Jan 22, 2009 at 12:40:59PM +0100, Hubert Feyrer wrote:
> 
> FWIW, I got the following panic now twice, after flipping an external 
> PPPoE connectipn down & up on a machine that's connecting a LAN with an 
> IPsec-encrypted GRE-Tunnel...
> 
> 

How old are your sources?  There was a fix that went in late last year
to the routing code to stop it stomping random kernel memory - the bug
would cause effects like you are seeing now.  If your sources are up
to date then you could try building a kernel with MALLOCLOG defined
and see if there is anything that is consistently listed as a
neighbour if/when you get a report of data modified on the malloc free
list.

-- 
Brett Lymn
"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email
in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."