On Thu, Jul 15, 1999 at 10:01:18AM -0700, Matthew Dillon wrote:
> :> I realise that will stop the panic from looking at the source code, but
> :> surely it's just covering up the problem and waiting for it to happen
> :> later?
> :>
> :I'm pretty it's caused by the INVARIANTS option, similar incidents have been
> :reported many times before. The problem with INVARIANTS is that 1. it alters
> :data structures, 2. kernel modules don't know about this option, so you
> :have inconsistent kernel and modules. There're three solutions,
> :
> :1, make INVARIANTS less intrusive. So far only vm_zone code is causing
> :problems, I suggest we rename the option to INVARIANTS_ZONE in this part
> :of code (the code should be pretty much bug free by now).
> :
> :2, compile modules with the option. The easiest way is probably add
> :-DINVARIANTS in your /etc/make.conf, you have to remember to take it
> :out when you remove the option from your config file.
> :
> :3, do not use INVARIANTS if you don't need it. :)
>
> This sounds very similar to the DIAGNOSTIC story... I would much
> prefer to see INVARIANTS be entirely passive and not fall down
> the same well as DIAGNOSTIC did. People may remember how utterly
> useless DIAGNOSTIC became due to being overly intrusive.
>
> INVARIANTS should simply assert conditions that it expects to be
> true and panic if they aren't.
In this case, it appears to have done that. I just don't know enough to
work out what is causing the assertion to fail...
--
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator
In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
--
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**********************************************************************
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
