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 02:15:50PM +0100, Hubert Feyrer wrote:
> 
> My sources are from about 1 week ago (netbsd-5 branch).

Hmmm that should have the fix to net/rtsock.c then

> How do I look at that log when the option's enabled in the kernel?
> 

If the free list is detected as being corrupted then the malloc log is
printed out, if memory is getting corrupted then the thing being
stomped will change but the "neighbour" - the bit of memory in use
just before the stomped memory may be the same which may offer some
clues - there is a variable malloclog_fuzz in kern/kern_malloc.c that
can be tweaked to widen/narrow the neighbour matching.

By the way you need DIAGNOSTIC defined as well to enable the checks.

-- 
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."